account_name) is never supplied by the caller — it is resolved server-side by looking up account_number and bank_code against the issuing bank via Flutterwave's account resolution service, so the request will fail if the account cannot be verified.account_number and the resolved instrument type must be unique per entity: you cannot save the same bank account twice for the same entity, even under different counterparties.curl --location '/counterparty-instruments' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"counterparty_id": "01HZ9KPQR3VTXMN84JWYB65CD0",
"account_number": "0690000031",
"bank_code": "044"
}'{
"message": "Counterparty instrument added successfully",
"status": "success",
"data": {
"id": "01J5RZ8N3F7Q2VYTHB6WCXK4M9",
"entity_id": "01HZ9ABCD1234EFGH5678IJKL90",
"counterparty_id": "01HZ9KPQR3VTXMN84JWYB65CD0",
"account_number": "0690000031",
"account_name": "JOHN ADEBAYO DOE",
"bank_code": "044",
"bank_name": "Access Bank",
"display_name": "Primary Salary Account",
"status": "active",
"country": "NG",
"created": 1722870000000,
"updated": 1722870000000
}
}