INTERNATIONAL PAYMENTS
SWIFT & SEPA payments under your brand
Classical international payments, run from your platform: SWIFT for cross-border transfers anywhere in the world, SEPA for euro payments across the Single Euro Payments Area, created and signed in your web and mobile apps, screened before they leave, and booked into the same double-entry ledger as everything else.
SWIFT worldwide, SEPA across the euro area
Two payment types cover the classical international ground. SWIFT carries cross-border transfers to and from practically any banked destination, the default rail for global business payments. SEPA credit transfers handle euro payments across the Single Euro Payments Area as the fast, low-friction option for European business.
Both run as first-class payment types in the client apps: created, signed under multi-signatory mandates, tracked to completion, and confirmed with downloadable payment confirmations. For the domestic side of your corridors, instant schemes, Interac, ACH/EFT, see Local & Instant Payments.
Frequent beneficiaries live as saved counterparties, so a repeat SWIFT or SEPA payment opens prefilled; the signature itself is the client’s payment PIN.
The settlement chain behind your payments
External settlement runs today through integrated payment providers. Own correspondent accounts and direct SWIFT connectivity are in development, an initiative that shortens the settlement chain, reduces per-transaction cost and removes dependency on any single intermediary. Because providers are configuration, routing per corridor stays a commercial decision rather than an engineering project.
Whatever the route, the accounting is identical: every leg books into the double-entry ledger, and correspondent positions are reconcilable against their counterpart records with dedicated reporting.
Screened before it leaves: compliance and four-eyes on outbound flows
No payment departs unexamined. Every outbound transfer is compliance-screened with hold, rejection and action-required outcomes; per-client limits respond to risk rating, PEP and US-person status; country-level availability is enforced centrally. Client-side signatory mandates and, where policy requires, back-office approval put four eyes on the money, and flagged payments can be reviewed, amended, investigated or intervened on in flight.
International payments, priced per client
Cross-border payments are one of the platform’s cleanest revenue lines: fees differentiated by payment type and by direction (incoming versus outgoing), combining flat and percentage components with minimums and maximums, varying by currency, country and transaction size. Servicing charges, payment cancellations, SWIFT confirmations, reference letters, are priceable too. Every charge maps to its own income position, so international-payments revenue reports itself by line.
SWIFT & SEPA payments FAQ
When does a payment go SWIFT vs SEPA?
SEPA covers euro payments within the Single Euro Payments Area; SWIFT covers cross-border transfers globally and non-SEPA cases. In the client apps both are simply payment types, the right rail for the destination and currency.
What does the client see during and after a payment?
Creation and signing in the web or mobile app, status through the lifecycle, and downloadable payment confirmations afterwards, with SWIFT confirmations available as a serviced document where needed.
What happens if a payment gets flagged?
It holds rather than leaves: compliance screening routes it to the back office with a hold, rejection or action-required outcome, where it is reviewed, approved, amended or investigated, with intervention possible on payments in flight.
Can we charge differently for incoming and outgoing transfers?
Yes, fees are differentiated by payment type and direction, per client, down to an individual account, and changed from the back office without a release.
Which currencies and corridors are supported?
That is a configuration-plus-provider question rather than a fixed list: corridors are mapped to your markets and routing during scoping, and new ones are onboarded as integrations and configuration.
Can signatories approve international payments from a phone?
Yes, payment authorisation works in the native iOS and Android apps, so approval is not tied to a desk.
Send a test payment in the demo
Creation, signing, screening, the provider hand-off and the ledger entries behind it, watch a cross-border payment cross the platform end to end.