ACH is in development. The API endpoints and webhooks on this page are provided for reference and are subject to change. Reach out to your relationship manager for beta access. See USD rails.
POST /v2/transfers requires the Transfer funds permission and an Ed25519 request signature.
Choose a destination type
As with a domestic wire transfer, an ACH credit can go to any destination or to a bank trusted destination. Each one needs its own permission group and API key, because a permission group can’t use both at the same time.Send to any destination
Use any destination to pay a US bank account that isn’t saved as a trusted destination. Setdestination.type to FIAT_INLINE and put the beneficiary and bank details in destination.details, with beneficiaryBank.code set to ABA and the routing number in beneficiaryBank.id. Don’t send destination.id or assetParametersFiatTrustedDestination.
Your API key’s permission group must have Any destination selected under Transfers outside Anchorage, with a daily amount limit. For the permission group setup, an example payload, and the field reference, see Any destination bank transfers.
Set up a trusted destination
To send to a trusted destination instead, create one withPOST /v2/trusted_destinations, setting type to fiat and fiat.beneficiaryBank.code to ABA. See Create a USD trusted destination via API.
Your API key’s permission group must have Any trusted destination selected under Transfers outside Anchorage. See Connect a trusted destination to an API key.
Send to a trusted destination
Setdestination.type to TRUSTED_DESTINATION and destination.id to the fiat trusted destination ID, and include assetParametersFiatTrustedDestination. To find the destination ID, call GET /v2/trusted_destinations and filter on type == "fiat".
USD_R asset type and production uses USD. The fields, purpose values, and response match a domestic wire transfer. See Domestic wire transfer.