Choose your country or region

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.

Payment systems

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

The app submits each international payment to the system that already builds your Swift messages. We never hold a Swift connection or a BIC of our own.

Whatever connectivity you run

Your own Swift interface, Swift's cloud service or a service bureau all stay as they are. We connect to the system in front of them, not to Swift.

Status back into the app

We read the status your core or hub reports and show the customer where the payment is, including a reason when it is returned.
Data

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.

Use cases

What your bank can do with it

Pay family abroad

Customers send money to an account in another country and see the quote before they confirm with a step-up check.

Pay overseas suppliers

A business prepares an international payment and a second person approves it, so no one approves their own.

Know where the money is

Customers follow the payment in the app instead of calling your branch to ask.

Receive from abroad

Incoming international payments show in the activity feed as your core books them.
Why it matters

What it changes for your bank

Fewer branch visits for transfers

The international payment customers once queued for is a few screens in your app.

Your Swift set-up, untouched

No new interface, certificate or service bureau contract. The app sits on what you run.

Fewer payments returned

The app asks for the details your core needs up front, so incomplete instructions don't leave the bank.
Rollout

From first call to live

  1. Step 1: Map your international paymentsWe learn which system builds your Swift messages, which currencies you send and what it reports back.
  2. Step 2: Build the connectorWe connect the app to that system with our connector kit and map its statuses to clear customer wording.
  3. Step 3: Test on your sandboxWe send test payments through your test environment, including returns and refusals.
  4. Step 4: LaunchInternational payments open in your web, iPhone and Android apps, with tracking and notifications.
Questions

SWIFT: what IT teams ask

Does Everbranch need its own Swift connection or BIC?
No. Your bank keeps its Swift connection and BIC. The app hands each payment to your core or payment hub, which sends it over Swift as it does today.
Does it matter whether our core sends MT or ISO 20022 messages?
No. Message formats stay inside your core or payment hub. We connect to that system's interface and read back the outcome it reports.
We reach Swift through a service bureau. Does that work?
Yes. The bureau stays between your bank and Swift. We only connect to your own systems, so your bureau arrangement doesn't change.
Can customers track an international payment after it leaves?
Yes, as far as your systems report it. The app shows each status your core or hub gives back, so the more your bank tracks, the more customers see.
Related

PAPSS

Your customers pay someone in another African country from your app, in their own currency. The payment runs through your bank's PAPSS participation.
PAPSS integration

Buna

Your customers pay across the Arab region from your app, in Arab or international currencies. Each payment runs through your bank's own place in Buna.
Buna integration

Temenos Transact

Keep Transact as your core and give customers an app they enjoy. We connect through the Transact APIs your bank licenses, or the files it already exchanges.
Temenos Transact integration
Pilot programme

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