International payments over Swift, from your own app.
Your customers send money abroad from an app in your brand. Your core sends the payment over the Swift connection your bank already runs. Everbranch builds small and medium banks their own web and mobile banking app on the core they already run, and links it to SWIFT through the bank’s own connection.
We build the SWIFT connector during your implementation programme, with the same connector kit as our existing connectors.
How we connect to SWIFT
Swift is a cooperative company under Belgian law, owned and controlled by its member financial institutions and overseen by the G-10 central banks. It runs the secure messaging network banks use to send payment instructions to each other; it doesn't move money itself. Banks connect through their own interfaces, Swift's cloud services or a service bureau, and Swift is moving cross-border payments to the ISO 20022 standard.
Through your core or payment hub
Whatever connectivity you run
Status back into the app
What moves between SWIFT and your app
- International payment instructions from your app to your core or payment hub
- Beneficiary details your core needs, such as the BIC, account or IBAN, name and address
- Payment status from submitted to completed, returned or refused
- The charges and exchange rate your core quotes, shown before the customer confirms
- Notifications to the customer and, for businesses, to approvers
Your Swift connection, your BIC, your correspondent accounts and every message stay with your bank. We keep no ledger and send no Swift messages ourselves.
What your bank can do with it
Pay family abroad
Pay overseas suppliers
Know where the money is
Receive from abroad
What it changes for your bank
Fewer branch visits for transfers
Your Swift set-up, untouched
Fewer payments returned
From first call to live
- Step 1: Map your international paymentsWe learn which system builds your Swift messages, which currencies you send and what it reports back.
- Step 2: Build the connectorWe connect the app to that system with our connector kit and map its statuses to clear customer wording.
- Step 3: Test on your sandboxWe send test payments through your test environment, including returns and refusals.
- Step 4: LaunchInternational payments open in your web, iPhone and Android apps, with tracking and notifications.
SWIFT: what IT teams ask
Does Everbranch need its own Swift connection or BIC?
Does it matter whether our core sends MT or ISO 20022 messages?
We reach Swift through a service bureau. Does that work?
Can customers track an international payment after it leaves?
Other systems banks connect
PAPSS
Buna
Temenos Transact
Running SWIFT? Let's map it.
Tell us your version and how your teams use it. We'll show where it plugs in and what your customers get.
- Your name and colours in the demo
- Straight answers for risk, compliance and IT
- No commitment