curl --request PATCH \
--url https://api-sandbox.finogates.com/v1/platform/payees/bank-accounts/{payee_id}/{bank_account_id} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"nickname": "Acme — Primary payout account"
}
'{
"status_code": 200,
"data": {
"id": "f1e2d3c4-b5a6-7890-1234-567890abcdef",
"payee_id": "d4e5f6a7-b8c9-0123-4567-890abcdef012",
"nickname": "Acme — Primary payout account",
"account_holder_name": "Acme Supplier LLC",
"bank_name": "Example Bank",
"bank_country": "US",
"currency": "USD",
"rail_code": "ach",
"account_type": "checking",
"account_last4": "6789",
"routing_last4": "0021",
"status": "active",
"created_at": "2025-06-10T18:12:00.000Z",
"updated_at": "2025-06-12T11:02:17.000Z"
},
"query_generated_time": 1712847600000
}{
"detail": [
{
"loc": [
"<string>"
],
"msg": "<string>",
"type": "<string>"
}
]
}Update a Payee's Bank Account
Change details of a saved bank account. Send only the fields you want to update — anything you leave out is kept as-is. The usual case is filling in a field that’s required for a corridor but was missed at creation, such as the IFSC code for an India destination (ifsc).
If you send a new bank_account_number it must be digits only; it is re-encrypted and only the last four digits are ever returned.
curl --request PATCH \
--url https://api-sandbox.finogates.com/v1/platform/payees/bank-accounts/{payee_id}/{bank_account_id} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"nickname": "Acme — Primary payout account"
}
'{
"status_code": 200,
"data": {
"id": "f1e2d3c4-b5a6-7890-1234-567890abcdef",
"payee_id": "d4e5f6a7-b8c9-0123-4567-890abcdef012",
"nickname": "Acme — Primary payout account",
"account_holder_name": "Acme Supplier LLC",
"bank_name": "Example Bank",
"bank_country": "US",
"currency": "USD",
"rail_code": "ach",
"account_type": "checking",
"account_last4": "6789",
"routing_last4": "0021",
"status": "active",
"created_at": "2025-06-10T18:12:00.000Z",
"updated_at": "2025-06-12T11:02:17.000Z"
},
"query_generated_time": 1712847600000
}{
"detail": [
{
"loc": [
"<string>"
],
"msg": "<string>",
"type": "<string>"
}
]
}Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Query Parameters
Optional. The unique ID of the user who owns this payee. Omit to look the payee up by its ID within your tenant.
"b3a9b622-cc63-4d3c-aad6-2d8e29e6f9d4"
Body
Partial update for a saved payee bank account (PATCH semantics).
Only the fields included in the request body are changed; everything else is
left untouched. The common use is filling in a corridor-required field that
was missed at creation — e.g. the IFSC code for an India destination
(bank_branch / ifsc). The account number, when supplied, is
re-encrypted and re-masked exactly as on create.
120120120Account type — "checking"/"savings" for US ACH, or the UniTeller code (AHO/CTE/NON).
30New bank account number (digits only). Re-encrypted on update.
4 - 34UniTeller branch / routing code (IFSC, SWIFT/BIC, or CLABE).
50100Response
The updated bank account (sensitive numbers masked).