NEWPockyt × Circle: native USDC settlement now live →
VisionNews
Checkouts · B2B
Wires, RTP, ACH —
received as natively
as consumer checkouts.
For B2B businesses receiving payment by wire transfer, local real-time payment rails, or ACH-style transfers: a globally-addressable bank account in your merchant name, directly into the Pockyt ledger, governed by the same controls as any other balance.
Supported B2B rails
SWIFT wire
Global · same-day settlement most corridors
Live
Local RTP rails
FedNow, SEPA Instant, FPS, NPP, PromptPay, more
Live
ACH (US)
Standard ACH plus same-day ACH
Live
Direct debit (SEPA, BACS)
Pull-based collection for recurring B2B
Beta
Why this matters
B2B money doesn't move like B2C money.
Consumer checkout assumes a buyer at a cart, choosing from a method list, completing within seconds. B2B is the opposite: a counterparty's accounts-payable team initiates the transfer from their bank, asynchronously, often days after invoicing. The infrastructure has to match.

Standard B2B today

The merchant gives the counterparty a generic bank account number. Funds land in an operational bank account, separate from any payment processor. Reconciliation is manual — matching incoming wires to outstanding invoices in a spreadsheet. Cross-border wires add 1-3 days, FX margin from the receiving bank, and no programmability on top.

Bank-ral Collection on Pockyt

Funds land in your Pockyt virtual account on the same rail. Pockyt assigns each invoice a unique reference, auto-matches incoming transfers to invoices, and exposes the same API surface for balances, conversion, and routing as any other Pockyt primitive. One ledger across both your B2C and B2B inbound.

How it works
Tow Patterns, one ledger.

1. Per-invoice virtual sub-accounts

For high-volume B2B platforms, issue a unique virtual sub-account per invoice or per customer. Any incoming transfer auto-matches by destination. No reference parsing, no manual reconciliation — the sub-account is the reference.

2. Single VA with reference-based matching

For lower-volume use cases or where issuing per-invoice accounts isn't operationally desirable, use a single virtual account and let Pockyt match incoming transfers to invoices via the reference field. Auto-match confidence is exposed in the API so your team can review the edge cases.

# Internal transfer between two accounts
curl https://mapi.pockyt.io/v3/transfer/internal 
  -H "Accept: application/json" 
  -H "Content-Type: application/json" 
  -d '{
    "amount":                    "10000",
    "currency":                  "USD",
    "sourceAccountNumber":       "244275893769",
    "destinationAccountNumber":  "244182028636",
    "invoiceId":                 "129153721363341316",
    "ipnUrl":                    "https://example.com/webhooks",
    "note":                      "Bonus",
    "merchantNo":               "203113",
    "storeNo":                  "301854",
    "merGroupNo":               "100009",
    "timestamp":                "2026-03-23T17:00:00Z",
    "verifySign":               "cb74eb92eebadc97445d559bc5501012"
  }'
POST /v3/transfer/internal
Capabilities
What B2B collection actually needs.

01

Globally-addressable accounts

SWIFT-routable in all 11 domiciled markets. Local-rail addressable (FedNow, SEPA Instant, FPS, etc.) per market.

02

Per-invoice virtual sub-accounts

Issue a virtual sub-account per invoice. Auto-match by destination. Close after settlement.

03

Reference-based matching

For single-account use cases, intelligent reference parsing auto-matches incoming wires to invoices.

04

Webhooks on receipt

Signed webhook fires the moment funds clear. Includes sender details, reference, and matched invoice if applicable.

05

Multi-currency at receipt

Accept in any of 27 fiat currencies. Convert to USDC or another fiat on receipt, or hold in the original currency.

06

One ledger, all inbound

B2B wires reconcile in the same Pockyt ledger as consumer checkouts. No separate accounting layer.

When to use
Three patterns where Bank-rail Collection fits naturally.

1. B2B SaaS billing globally

Enterprise SaaS contracts settle by wire or ACH, not by card. Pockyt gives you a domiciled receiving account in every market your customers pay from, with auto-matching to your invoice system.

2. Marketplaces with B2B buyer flows

Marketplaces where buyers are businesses (wholesale, B2B services, equipment) benefit from offering local bank rails as a payment method. Per-invoice sub-accounts make reconciliation tractable at scale.

3. Treasury operations receiving payouts from partners

Companies that receive recurring payments from partners, distributors, or affiliates can collect via Pockyt instead of operational bank accounts — keeping all inbound funds in the same ledger as the rest of treasury operations.

Bank rails. One ledger.

Talk to our team about consolidating B2B inbound into the same operating layer as the rest of your money movement.