Create Fiat Beneficiary

For each receiver, you need to create a beneficiary on the platform. We will return a beneficiary_id, which can be used to make transfers.

Once added, the platform will automatically perform AML and Sanctions checks on the beneficiary.

---

Endpoint

POST https://api.zamp.finance/api/client/:clientid/customer/:customerid/fiat/beneficiary

This API creates a fiat beneficiary.

---

Request Body for AED Beneficiary

Key	Type	Description	Required
first_name	String	First Name of the beneficiary in String format (beneficiary_account_type is Individual)	Yes
last_name	String	Last Name of the beneficiary in String format (beneficiary_account_type is Individual)	Yes
email	String	Email of the beneficiary.	No
telephone_number	String	Telephone number of the beneficiary in E.164 format.	No
date_of_birth	String	Date of birth in RFC3339 format (YYYY-MM-DD).	No
address	Address	Address details of the beneficiary.	Yes
relationship_to_customer	String	Relationship of the customer to the beneficiary. Possible values: "SPOUSE", "EX_SPOUSE", "CHILDREN", "PARENT", "SIBLING", "RELATIVE", "SELF", "FRIEND", "BUSINESS_PARTNER", "CUSTOMER", "EMPLOYEE", "BRANCH_OFFICE", "SUBSIDIARY_COMPANY", "HOLDING_COMPANY", "SUPPLIER", "CREDITOR", "DEBTOR", "FRANCHISEE".	No
account_type	String	Type of the beneficiary. Example: "Individual".	Yes
destination_currency	String	Destination currency of the beneficiary (e.g., USD, USDC).	Yes
transfer_type	String	Type of transfer. Possible values: SWIFT, ACH, LOCAL.	No
beneficiary_bank_country_code	String	Country code of the beneficiary’s bank (ISO 3166 Alpha-2, e.g., US).	No
routing_code_type_1	String	Routing code type based on transfer type. Possible values: ACH, FEDWIRE, or SWIFT.	No
routing_code_value_1	String	Routing number corresponding to the routing code type.	No
account_number	String	Beneficiary IBAN or account number for payout.	Yes
account_ownership_document	String	Base64-encoded document proving ownership of the account.	No
intermediary_information	Intermediary	Optional intermediary bank details (correspondent institution).	No

---

Intermediary

Key	Type	Description	Required
institution_name	String	Name of the intermediary institution (e.g., “Bank of America”).	Yes
institution_address	Address	Address of the intermediary institution.	No

---

Address

Key	Type	Description	Required
address_line	String	Address line of the beneficiary.	No
city	String	City.	No
state	String	State / Province (2-digit subdivision per ISO 3166-2).	Yes
postal_code	String	Postal / ZIP code.	No
country_code	String	Country code in ISO 3166-1 Alpha-2 format.	Yes

---

Sample Request JSON (USD Beneficiary)

{
  "first_name": "John",
  "last_name": "Doe",
  "email": "johnDoe12@test.com",
  "telephone_number": "+12125551234",
  "date_of_birth": "1970-01-01",
  "address": {
    "address_line": "1600 Pennsylvania Avenue NW",
    "city": "Washington",
    "state": "DC",
    "postal_code": "20500",
    "country_code": "US"
  },
  "relationship_to_customer": "SUBSIDIARY_COMPANY",
  "routing_code_type": "SWIFT",
  "routing_code_value": "BOFAUS3NXXX",
  "account_type": "Individual",
  "account_number": "8508697970656",
  "transfer_type": "LOCAL",
  "destination_currency": "AED",
  "beneficiary_bank_country_code": "AE",
  "beneficiary_alias": "Test",
  "beneficiary_bank_name": "",
  "account_ownership_document": "base64_of_the_document",
  "intermediary_information": {
    "institution_name": "Bank of America",
    "institution_address": {
      "address_line": "1608 Pennsylvania Avenue Bank NW",
      "city": "Washington",
      "state": "DC",
      "postal_code": "20500",
      "country_code": "US"
    }
  }
}

---

Response Body

Key	Example Value	Description
beneficiary_id	merchant_jXHm4aJH4vUmgcT6bmYGwD_11_30	Unique identifier assigned by Zamp systems for the created beneficiary.

---

Sample Response JSON

{
  "data": {
    "beneficiary_id": "merchant_jXHm4aJH4vUmgcT6bmYGwD_11_30"
  }
}

---

✅ Notes:

• Ensure that all ISO codes (country/state) follow official ISO 3166 standards.
• Base64-encoded documents must not exceed the platform’s maximum payload limit.
• beneficiary_id must be stored securely for future transfers.