Connect Airwallex

Airwallex by currency, every batch a draft

Each currency arrives as its own account with its statement, and an approved run lands in Airwallex as one draft batch.

Book a demo Start free

Orla creates the draft and never submits it. Rolling out space by space.

What lands in the book

Each currency of the wallet is an account of its own

Airwallex · GBP, Airwallex · EUR and so on, so a batch is single-currency and never needs a conversion decision.

Each currency arrives with its available balance; rename any of them and your name is kept. Balances refresh about once an hour.
The statement arrives by itself: about a month back when you connect, hourly after that, and only settled movements. One that settles days after it was started is still picked up.
A conversion between two of your own currencies is one transfer, not an expense and an income.
A payment Orla prepared is not booked twice: when the statement brings the bank's version of it, the payment you already have gains the bank's reference and date.
Receive shows the account number, IBAN, sort code or routing code, BIC and the account holder as Airwallex states them, one block per Global Account.

The key you give us

A scoped key, and an honest word about what it could do

Developer, then API keys, in your own Airwallex. The form lists the permissions one by one.

What to create: A scoped key with read on balances, financial transactions and Global Accounts, read and write on beneficiaries and batch transfers, and nothing on transfers. You paste the Client ID and the API key.
What keeps the money safe: Airwallex has no permission that separates preparing from sending. So the guard is double: Orla's code never submits a batch, and you are asked to switch on your own approval workflow in Airwallex for transfers started over the API.
Checked before it is saved: Tried against Airwallex first. Once accepted it is stored encrypted and never shown again, not to you and not to us.
If Airwallex stops accepting it: The row says so, and Update key takes a fresh one while keeping the accounts, their history and the ceiling.
The ceiling: A ceiling per payment is set when you connect, and a payment above it is not even prepared.
A demo option: Connects Airwallex's test environment instead of real money.

Who presses last

Orla drafts. A person in Airwallex submits and approves

Approve in Orla as usual, and nothing has moved yet.

What Orla does: Within a few minutes it creates a draft batch in your Airwallex, with every approved payment of the run as a line, and each payment says it is waiting there.
Who presses last: Someone on your team opens Airwallex, submits the batch and approves it. Orla has no call that submits.
When the expense is booked: Line by line, only when Airwallex reports a transfer as paid. A line refused or failed in Airwallex is refused in Orla, and nothing is booked for it.
The payee: Must already be a beneficiary in your Airwallex. When it is not, Add payee to Airwallex first shows exactly what will be written into your account and adds it only after you confirm. A beneficiary the payment cannot reach the chosen way, a local transfer to one set up for SWIFT only, counts as not found.
Two that look alike: If two beneficiaries could be the one meant, the payment stops and says so. Nobody is paid until the duplicates are tidied in Airwallex.
Once, never twice: Orla creates a batch for a run once. A batch untouched for two weeks, deleted, or with a line removed or changed, asks you to check in Airwallex what was really paid.
A payment Airwallex reverses: Caught within the hour, flagged, announced to the owner and the admins, and netted by a compensating entry.
Disconnecting: Not while payments from Orla wait as drafts inside Airwallex: submit or delete them there first.

Questions

The questions a finance lead asks before connecting the bank

Can Orla send money from our Airwallex account?

Orla creates a batch in its draft state and never submits it; someone on your team submits and approves it inside Airwallex. Airwallex has no permission that separates preparing from sending, so the guard is Orla's code, which has no submit call, plus the approval workflow you are asked to switch on in Airwallex.

How do several currencies in Airwallex show up in the books?

Each currency of the wallet is its own account, named Airwallex · GBP and so on, with its available balance and its statement. A conversion between two of your own currencies is one transfer, not an expense and an income, and a batch paid from one of them is single-currency.

What if a payee is not in our Airwallex yet?

The payment says so instead of being prepared. Add payee to Airwallex shows exactly what will be written into your account and writes it only after you confirm. If two beneficiaries could be the one meant, the payment stops and nobody is paid until the duplicates are tidied in Airwallex.

Pay from another bank

Connect Airwallex, and keep the send button in Airwallex

Your own account, reached with a key you made yourself; the money never passes through Orla. This rail is being switched on space by space.

Mercury →: Orla requests a payment with a token that has no Send Money permission; an admin approves it in Mercury.
Slash →: No drafts there, so a transfer is created only when your colleague presses Send via Slash after the approvals.
Safe →: Read from the chain with its owners and threshold; Orla proposes as a delegate, never signs and never executes.

See it on your own books

Thirty minutes: we connect an account, drop a real bill in, and close a month together.

Book a demo or start free and connect one account