What to do in Airwallex, and what to send back to Custodia.
To start issuing cards with Custodia, complete the two steps below in your production Airwallex account and send us the three values at the end. We cannot finish the connection until your Airwallex account manager has enabled both Issuing and Remote Authorization.
Before you start
Ask your Airwallex account manager to enable Issuing and Remote Authorization on the account Custodia will issue cards on. Both have to be on before we can connect. You do not configure remote authorization yourself. We do that after we have the API key.
What you will send us
Airwallex shows the API key and the webhook secret only once. Copy each as soon as it appears. The webhook id is not the secret. Do not send the webhook id in its place.
| What Airwallex shows | Send to Custodia |
|---|---|
| Client ID | Client ID |
| Scoped API key (shown once) | API key |
| Webhook secret (shown once) | Webhook secret |
1. Create a scoped API key
In the Airwallex web app, go to Settings → Developer → API keys → New scoped API key.
- Name it
custodia connection(or similar). - Under account-level permissions, select the account Custodia should issue cards on. One account only.
- Enable every Issuing resource, with Read and Write where both exist. We create cardholders and cards, read transactions, update issuing configuration, and subscribe to dispute events. A scoped key can only subscribe to the webhook events its scopes allow, and that event list cannot be changed after the webhook is created.
- Allow the source IPs below. They are Custodia’s production egress addresses. Only these addresses can call Airwallex with this key.
- Create the key.
- Copy the client ID and the API key immediately. Airwallex does not show the API key again.
Source IPs to allow
3.68.45.224/3218.159.95.44/32
2. Create the issuing webhook
Go to Developer → Webhooks → New webhook. Use the same account as the API key.
| Field | Value |
|---|---|
| Name | custodia issuing |
| Notification URL | https://airwallex.production.custodia-tech.com/ledger/api/airwallex/transactions/feed |
| Account | The same account as the API key |
Events to subscribe to
Transactions
issuing.transaction.succeededissuing.transaction.failed
Disputes
issuing.transaction_dispute.createdissuing.transaction_dispute.expiredissuing.transaction_dispute.submittedissuing.transaction_dispute.rejectedissuing.transaction_dispute.cancelledissuing.transaction_dispute.acceptedissuing.transaction_dispute.wonissuing.transaction_dispute.lostissuing.transaction_dispute.modified
You can also include issuing.card_transaction events (authorized, verified, cleared, reversed, expired, declined, modified). We accept those events and do not post them. Card authorizations are decided by Custodia on a separate URL, which we set up after you send the API key. You do not create that URL or a shared secret.
Submit the webhook. Copy the secret for that notification URL. The webhook id only identifies the subscription. If the secret is not on screen after you submit, open the webhook under Developer → Webhooks and copy the secret stored for that URL. Each URL has its own secret.
You do not need to allowlist Airwallex’s webhook source IPs. Custodia already accepts those requests.
Send these three values to Custodia
- Client ID from the scoped key
- API key from the scoped key
- Webhook secret for the notification URL above
Send all three together. Do not send a Login As value, an account name, or the webhook id in their place.
These steps are for your production Airwallex account. If you are connecting a demo account first, tell us before you create the webhook and we will send the sandbox notification URL.
Once we have these three values, we will finish the connection on our side and confirm when issuing is ready.