Country requirements
Bank lookup means you must fetch the receiving institution fromGET /v2/institutions and pass the selected bank_id. See Bank lookups below.
Recipient extras are in addition to the fields every registration requires: name (or business_name), email, and address.
Business recipients marked No means the country accepts individual recipients only; submitting recipient.business fails.
* Required for
FIRST_PARTY recipients too. Every other country’s recipient extras apply to THIRD_PARTY recipients only.
Jordan additionally requires recipient.individual.middle_name — it’s optional on every other corridor. Registration rejects a JOD payout missing it, naming recipient.individual.middle_name.
† beneficiary_type must be FIRST_PARTY for US payouts, and the destination must be a bank account the customer owns. Every other country accepts both FIRST_PARTY and THIRD_PARTY.
SEPA countries
All SEPA corridors pay out in EUR and share the same requirements, except that Sweden also requirestax_id for THIRD_PARTY business recipients:
Austria, Belgium, Bulgaria, Croatia, Cyprus, Czechia, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland.
Bank lookups
Countries marked Yes above require the customer to select their receiving institution, and registration fails without abank_id. Fetch the list before you render the bank field:
- Japan is marked Yes, but the lookup only gets you part of the way: it returns
bank_id, but not the Zenginbank_code, which the institutions endpoint doesn’t carry. Collectbank_codedirectly from the customer in addition to doing the lookup.
Building the request
You register payout destinations throughPOST /v2/identities/{identity_id}/payment-instructions. The country determines three things: the payment_method, the details object nested inside bank_account_details, and which recipient fields you need — see your corridor’s row in Country requirements above. Beyond those fields, conversion submission, webhook handling, and status progression are identical across every corridor.
Canada, which uses one of the more detailed objects:
recipient.individual or recipient.business. Nest tax_id and phone inside whichever one you set.
Bastion derives the account holder’s name and address from the recipient object before forwarding to the payment provider. Do not put them inside bank_account_details.
Format requirements
Bastion validates these formats when you register payment instructions. A value that doesn’t match returnsINVALID_INPUT with the offending field, instead of failing later at the payment provider. The rules below apply to every corridor; where a country or rail needs something more specific, it’s in Field formats by country.
Recipient names. THIRD_PARTY individuals must send recipient.individual with both first_name and last_name — a top-level recipient.name without recipient.individual is rejected for them. business_name is 3 to 100 characters, and at most 50 on SEPA.
Emails. email must be a bare ASCII address with a domain that contains a dot, e.g. avery.tremblay@example.com. Bastion rejects display-name forms such as Avery <avery@example.com>, anything in angle brackets, dotless domains such as avery@localhost, and non-ASCII characters such as tëst@example.com.
Labels and bank names. account_name and bank_account_details.name are each at most 255 characters.
Tax IDs. Bastion strips spaces, dashes, periods, and slashes from tax_id before validating it. The result must be 3 to 20 characters — for example, 30-51731290-4 is accepted and validated as 30517312904. Several countries also enforce a specific format on top of this.
Postal codes. Bastion checks postal_code against the postal format of the address country. Matching is case-insensitive — use the country’s standard local format, e.g. 10115 for Germany or SW1A 1AA for the United Kingdom. Some countries have additional rules.
Region codes. region_code is the subdivision (state, province, or region) code, up to 50 characters. It accepts one-character subdivision codes for non-US addresses, e.g. C for Buenos Aires City, Argentina, or 9 for Vienna, Austria. For US addresses, use an ISO 3166-2 code without the country prefix, e.g. CA, not US-CA. UM (U.S. Minor Outlying Islands) is not a valid US region.
country is a two-letter ISO 3166-1 alpha-2 code in upper case, e.g. AR.
Street addresses. street_line_1 and street_line_2 allow at most 35 characters each on payment instructions — stricter than the 100 characters accepted during identity onboarding. street_line_2 is optional, but when set it must be at least 3 characters. street_line_1 can’t be a P.O. Box.
Phone numbers. E.164 with country code, e.g. +541143000000.