International settlement rails research

Date: 2026-07-14
Status: Research brief (not an implementation plan)

Not legal advice — commercial counsel should review partner contracts and AML / money-transmission exposure before committing to a rail or partner model.

This brief consolidates Paybond’s international settlement-rails research for product and engineering. It sits alongside the production reference Settlement provider integration, which covers the rails already in scope.

Top 3 recommendations

Editorial product ranking for the next international rails (partner/API model — no Paybond PSP licenses for these paths):

1. TrueLayer (UK/EU bank A2A escrow) — best structural Harbor fit for fund → evidence → refund/release.
2. Wise Platform (cross-border multi-currency payouts) — best payee / FX unlock after evidence-approved release.
3. Paystack (Nigeria / NIP) — preferred next regional corridor given Nigeria demand; VA and Transfer maps cleanly to escrow without raw NIBSS membership.

Corridor alternative: Pix via licensed PSP remains the best LATAM pick if Brazil demand leads over Nigeria. Flutterwave is the Nigeria alternate to Paystack.

Licensing posture across all three: integrate as orchestrator via partner APIs; keep money movement and scheme licenses with the partner.

Why this matters

Paybond already covers:

International account-to-account (A2A), FX, and local instant rails matter for:

• Escrow-style fund → evidence → release / refund where the buyer pays from a bank account (not only cards).
• Multi-tenant settlement destinations outside the US (payee bank accounts, local wallets, FX payout corridors).
• Non-US buyers and payees who expect Faster Payments, SEPA Instant, Pix, NIP, and similar local rails.

Recommended approach: keep Paybond as the control-plane orchestrator (tenant destinations, webhook jobs, Harbor rail drivers, Configuration → Settlement). Partner with licensed PSPs / initiators for money movement rather than joining every national scheme as a direct participant.

Decisions (2026-07-14): Flutterwave next (multi-country Africa) — BYO tenant credentials like Adyen; Paystack becomes an alternate / deferred corridor pending demand. See the Flutterwave implementation design: Flutterwave settlement rail — implementation design. TrueLayer and Wise remain important but deferred pending demand. Reuse the existing settlement control plane at each step. Pix via licensed PSP is the LATAM corridor alternative when Brazil demand leads.

Implementation (TrueLayer selected): see TrueLayer settlement rail — implementation design.

Recommended international rails (detail)

Depth behind the Top 3. TrueLayer and Wise are ranked #1–#2; Nigeria (Paystack) is #3 with Pix as the LATAM corridor alternative.

1. TrueLayer — UK Faster Payments and EU SEPA Instant / Open Banking

#1 — Highest escrow fit.

Why Paybond

• Strong mapping to Harbor’s fund → evaluate → terminal settlement loop: pay-in settles into a merchant account (hold), then Refund API or payout drives release/refund.
• Webhook-first status model fits existing gateway webhook-job patterns.
• Multi-tenant destinations can store TrueLayer merchant-account / beneficiary config on paybond_tenant_settlement_config the same way Connect / Adyen destinations do today.

How to integrate

1. API aggregator — integrate TrueLayer Payments API v3 (not build direct bank Open Banking connections).
2. Merchant account — create TrueLayer merchant account(s); settle pay-ins into that account as the escrow float.
3. Pay-in — create payment; user authorizes in bank UI; monitor payment_* webhooks until settled.
4. Refunds — POST /v3/payments/{payment_id}/refunds for evidence-failed / cancelled intents (tied to original payment; cannot exceed pay-in).
5. Payouts (optional release path) — POST /v3/payouts for closed-loop (to original payment_source_id) or open-loop (SCAN/IBAN beneficiary).
6. Webhooks — subscribe to payment / refund / payout events; enqueue gateway jobs with tenant binding metadata (same preflight discipline as Stripe / Adyen).

Caveats

• Instant rails mean funds are settled into the merchant account, not “authorized soft”; escrow is operational (hold and policy), not scheme-level soft auth like card capture.
• Bank UX and coverage vary by ASPSP; some SEPA Instant corridors have bank-specific gaps.
• Partner KYB / due diligence is required before live merchant accounts.
• Refunds before settle can stay pending until the pay-in settles.

Licensing

2. Wise Platform — multi-currency cross-border payouts

#2 — Highest payee / FX fit.

Why Paybond

• Solves the hard part of international escrow: payee gets paid in the right currency after evidence, without Paybond building correspondent banking.
• Guaranteed delivery amount on quote aligns with escrow “locked release amount” UX.
• Enterprise / Embedded models keep licensing light vs becoming a money transmitter or licensed FI for every corridor.

How to integrate

Preferred flow for new integrations (MCA BALANCE funding):

1. Quote — create a quote for source → target amount/currency.
2. Recipient — create / select account recipient (bank details).
3. Transfer — create transfer from quote and recipient.
4. Fund — fund via MCA BALANCE (prefunded Wise balance), not legacy bulk settlement for new correspondents.

Avoid bulk settlement for new correspondent-style integrations — Wise documents it as no longer available for new correspondent partner integrations. Prefer Enterprise and/or Embedded models with balance funding.

Caveats

• Primarily a payout / FX rail, not authorize-capture on the buyer bank side.
• Once a transfer is processing, cancellation is difficult or unavailable — policy should finalize release decision before funding.
• Corridor, KYC, and recipient validation failures need Harbor-friendly error mapping and retry policy.
• Partner model choice (Enterprise vs Embedded vs Correspondent) drives KYC ownership and who holds the Wise relationship to end customers.

Licensing

3. Pix (Brazil) via licensed PSP — LATAM corridor alternative

LATAM instant A2A (prefer when Brazil demand leads over Nigeria; otherwise see Nigeria follow-up / Paystack as Top 3 #3).

Why Paybond

• Dominant local rail for Brazilian ecommerce / A2A; cards alone under-serve this corridor.
• PSP OpenAPI shape (cobrança and webhook and devolução) maps cleanly to Harbor funding and terminal settlement jobs.
• Keeps Paybond out of direct Bacen Pix participation.

How to integrate

Integrate a Brazilian licensed PSP (or Stripe Pix where product eligibility applies), not Bacen directly:

1. Cobrança — create Pix charge (QR / EMV / copia-e-cola) for the intent amount.
2. Webhook — confirm paid / expired / failed; bind to tenant and intent like other rails.
3. Devolução — refund (full/partial) on evidence failure or cancel, within scheme/PSP refund windows.
4. Release — on evidence success, either credit tenant destination (PSP payout) or treat PSP merchant balance as the hold then payout to payee.

Bacen’s public pix-api OpenAPI is the scheme spec; production traffic goes through a participant’s / PSP’s implementation of that API surface.

Caveats

• Pix settles instantly to the receiver — escrow cannot be soft-auth at the scheme; implement as wallet / merchant hold and devolução.
• Refund windows and rules are PSP- / scheme-constrained; design Harbor refund SLA accordingly.
• Brazil-only corridor (IOF, KYC, and tax disclosures may apply depending on PSP and charge type — see Stripe Pix docs if using Stripe).
• Pix Automático is a separate product path (mandates); don’t block v1 escrow on it.

Licensing

Suggested sequencing

1. TrueLayer   — buyer bank funding and refund (escrow core)
2. Wise        — multi-currency payee release (FX / local payout)
3. Flutterwave — Nigeria and multi-country Africa (VA and Transfer) — Paystack deferred/alternate
4. Pix (PSP)   — Brazil funding corridor when LATAM demand leads
1. TrueLayer   — buyer bank funding and refund (escrow core)
2. Wise        — multi-currency payee release (FX / local payout)
3. Flutterwave — Nigeria and multi-country Africa (VA and Transfer) — Paystack deferred/alternate
4. Pix (PSP)   — Brazil funding corridor when LATAM demand leads

Reuse the existing control plane at each step:

Do not invent a parallel settlement config system per country.

Near-misses (deprioritized)

Nigeria follow-up

Top 3 #3. Prefer Flutterwave (primary) for multi-country Africa corridors; Paystack remains a strong alternate for Nigeria-specific flows. Both follow the BYO partner/API licensing model (no raw NIBSS membership).

Underlying rail

• Primary instant rail today: NIBSS Instant Payments (NIP).
• Successor platform: NIBSS National Payment Stack (NPS) — ISO 20022 messaging, modernized initiation / reconciliation / dispute tooling. NIP remains relevant in parallel during migration; integrate via a licensed PSP that will migrate messaging as NPS adoption lands.

Recommended partners

Not first picks

• Moniepoint / OPay / PalmPay — strong consumer / agent networks; weaker fit as a neutral B2B escrow orchestration rail for Paybond.
• Remita / Interswitch — capable but heavier enterprise / switching posture for our first cut.
• Raw NIBSS membership — unnecessary when Paystack / Flutterwave already provide NIP connectivity under their licenses.

CBN licensing posture

Confirm commercial KYB, settlement timing, and refund / dispute SLAs with the chosen PSP before Harbor driver work.

Licensing summary

Across all four: tenant isolation stays Paybond’s job (authenticated settlement destinations, webhook binding, Harbor snapshots). Licensing for money transmission stays with the partner unless counsel redesigns the commercial model.

Sources

TrueLayer

• Payout and refund basics
• Refund a payment
• Create payout
• What difference does it make if I use my own PISP license?

Wise Platform

• Wise Platform API guides
• Fund transfers (incl. bulk settlement deprecation for new correspondent integrations)
• Bulk Settlement API reference
• Onboarding & KYC

Pix / Brazil

• Stripe Pix payments
• Stripe Pix Automático
• bacen/pix-api (OpenAPI scheme spec)
• Pix API docs site

Nigeria / CBN / NIBSS

• CBN Payment Service Providers
• Paystack Dedicated Virtual Accounts
• Flutterwave Virtual Accounts (confirm current path in Flutterwave developer portal)
• TechCabal — CBN licences in Nigeria
• TechCabal — NIBSS National Payment Stack (NPS)
• TechPoint — CBN fintech regulations / licensing context
• TechPoint — How Nigeria’s National Payment Stack enables faster payments
• ClearingPost — Nigeria National Payment Stack / NIP successor
• NIBSS — National Payment Stack

Related Paybond docs

• Settlement provider integration — production architecture for Stripe, Adyen, Shopify, ACH, USDC
• Settlement with payment providers — public operator guide