Sender Information
Sender object
When making a payout on behalf of an underlying customer, you must include a sender object in your request. This is required for compliance and screening obligations and applies across both API endpoints Create Payment Request & Create FX Request for downstream use cases (i.e where financial instituation is sending funds on behald of it's own customers) from it's master wallets with Verto.
This is often referred to as On Behalf Of, or Ultimate Sender Information. All information submitted is screened automatically by Verto for sanctions.
Where funds are sent directly from a sub-account - i.e., not from the master wallet of the financial services company, but the sub-account created for it's end customer, sender information is automatically populated from the sub-account information, and as such the such object is not required.
The sender object supports two types: company (business) and individual.
ReminderThe
senderobject is mandatory for all downstream payment flows, including the return of funds back to the original sender. Omitting it will cause the transaction to be flagged. If you are unsure whether this applies to your integration, contact your account manager before going live.
Company sender
Use this structure when the underlying sender is a business.
"sender": {
"country": "NG",
"type": "company",
"name": "Suit Country",
"customerIdentificationNumber": "45jtjy",
"accountNumber": "1234567890",
"address_line_1": "house street",
"address_line_2": "house street",
"address_city": "London",
"origination_country": "US",
"zip_code": "83888",
"registration_country": "NG",
"companyRegistrationNumber": "7575788",
"sub_category": "Baby products"
}| Field | Description | Mandatory |
|---|---|---|
country | Country of origin of funds | Yes |
type | Sender type — must be company | Yes |
name | Legal registered name of the business | Yes |
customerIdentificationNumber | Customer ID on your system | Either this or accountNumber |
accountNumber | Customer account number on your system | Either this or customerIdentificationNumber |
address_line_1 | Street, house number, building, apartment | Yes |
address_line_2 | Additional address line | Yes |
address_city | Sender's city | Yes |
origination_country | Country where the transfer is being initiated | Yes |
zip_code | Business address ZIP code | Yes |
registration_country | Country of business registration | Yes |
companyRegistrationNumber | Business registration number | Conditional — confirm with your account manager |
sub_category | Sender industry category | Conditional — confirm with your account manager |
Individual sender
Use this structure when the underlying sender is a private individual — for example, in remittance or last-mile delivery use cases.
"sender": {
"country": "NG",
"type": "individual",
"name": "John Suit",
"dob": "1990-03-15",
"customerIdentificationNumber": "45jtjy",
"accountNumber": "1234567890",
"address_line_1": "house street",
"address_line_2": "house street",
"nationality": "NG",
"address_city": "London",
"origination_country": "US",
"zipCode": "83888"
}| Field | Description | Mandatory |
|---|---|---|
country | Registered country of the sender's address | Yes |
type | Sender type — must be individual | Yes |
name | Full legal name of the sender | Yes |
dob | Date of birth (YYYY-MM-DD) | Yes |
customerIdentificationNumber | Customer ID on your system | Either this or accountNumber |
accountNumber | Customer account number on your system | Either this or customerIdentificationNumber |
address_line_1 | Street, house number, building, apartment | Yes |
address_line_2 | Additional address line | Yes |
address_city | Sender's city | Yes |
origination_country | Country where the transfer is being initiated | Yes |
zipCode | Sender's address ZIP code | Yes |
nationality | Sender's nationality | Yes |
