Create a standing order that takes in a user ID, a source account ID and a destination IBAN or blockchain address container. This will send an OTP to the user after all checks pass, to be entered into the "Confirm Standing Order" API, after which, any funds deposited into the users' source account are automatically converted into the currency of the destination container and sent. If a single EUR account is denominated as the source for a standing order, any EUR deposits arriving into that account ID will be converted into the currency denominated in the whitelisted address and paid out with the then prevailing network fees. If a single BTC account is denominated as the source for instance, using the "Lightning Network" APIs, you can even specify a "proposedRate" and a FOK (Fill or Kill) boolean to honor a specific rate for your flow of off-ramps from BTC to EUR.
SCA-enabled applications: accepts a verificationMethod field (sms, totp, or passkey). All three factors are accepted for standing-order setup. Under SCA-enabled apps, the destination must already be a Trusted Beneficiary when the debit side is regulated: USDC-destined orders require a trusted address (64009); CRYPTO_TO_FIAT orders require a trusted IBAN (64011). When using passkey, run PASSKEY_APPROVAL_START before calling /standing-orders/confirm.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
