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.

⚠️

Reminder

The sender object 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"
}
FieldDescriptionMandatory
countryCountry of origin of fundsYes
typeSender type — must be companyYes
nameLegal registered name of the businessYes
customerIdentificationNumberCustomer ID on your systemEither this or accountNumber
accountNumberCustomer account number on your systemEither this or customerIdentificationNumber
address_line_1Street, house number, building, apartmentYes
address_line_2Additional address lineYes
address_citySender's cityYes
origination_countryCountry where the transfer is being initiatedYes
zip_codeBusiness address ZIP codeYes
registration_countryCountry of business registrationYes
companyRegistrationNumberBusiness registration numberConditional — confirm with your account manager
sub_categorySender industry categoryConditional — 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"
}
FieldDescriptionMandatory
countryRegistered country of the sender's addressYes
typeSender type — must be individualYes
nameFull legal name of the senderYes
dobDate of birth (YYYY-MM-DD)Yes
customerIdentificationNumberCustomer ID on your systemEither this or accountNumber
accountNumberCustomer account number on your systemEither this or customerIdentificationNumber
address_line_1Street, house number, building, apartmentYes
address_line_2Additional address lineYes
address_citySender's cityYes
origination_countryCountry where the transfer is being initiatedYes
zipCodeSender's address ZIP codeYes
nationalitySender's nationalityYes