Skip to main content

Download CSV template

Merchant list template with column headers and descriptions.

Download Excel template

Combined template with both Merchant List and Loss History sheets.
  • All active merchants on your platform
  • One row = one legal entity, not per PSP account
  • Send via email or SFTP

Identity

merchant_registration_id
string
required
The legal registration ID of the merchant. This ID is assigned by the relevant government authority in the merchant’s registered country.Example: "201912345H" (SG) or "5457657" (US)
merchant_registration_id_type
string
required
The type of registration ID based on the country where the merchant is registered.Example: "UEN" (SG) or "SOS" (US)
merchant_registered_country
string
required
The country where the merchant is legally registered, as a two-letter code per ISO 3166 alpha-2.Example: "SG"
merchant_registered_state
string
The state where the merchant headquarters are legally registered, per ISO 3166-2:US. Mandatory for US merchants, can be left blank for non-US merchants.Example: "US-NY"
The merchant’s legal name as registered with the relevant government authority.Example: "ABC Trading Ltd."

Business activity

mccs
string
required
A comma-separated list of Merchant Category Codes (MCC).Example: "5251, 5714"
currency
string
required
The currency in which figures are reported, as a three-letter code per ISO 4217. If there are multiple currencies, either convert all figures to a primary currency or provide one row per currency.Example: "SGD"
onboarding_date
date
required
The onboarding date of the merchant in your PSP system, formatted as ISO 8601. Either onboarding_date or months_onboarded is required.Example: "2024-01-30"
months_onboarded
string
required
The number of months since the merchant was onboarded. Use ">12" if onboarded more than 12 months ago. Leave blank if not yet onboarded. Either onboarding_date or months_onboarded is required.Example: ">12" or "6"
last_12_months_tpv
integer
required
The last 12 months Total Payment Volume (TPV) processed by this merchant. If the merchant has not yet been onboarded, provide the expected annual TPV. Whole number, no decimals, no thousand delimiters.Example: 8000000

Risk & exposure

value_at_risk
integer
required
The maximum loss the PSP could suffer if the merchant defaults, assuming no collateral. Whole number, no decimals. Either value_at_risk or delivery_days is required.Example: 135000
delivery_days
integer
required
The average number of calendar days between when the merchant receives payment and delivers goods/services. Use 0 for immediate delivery. Either value_at_risk or delivery_days is required.Example: 14

Optional fields

We understand that collating information across multiple systems can be tedious. However, if the following fields are easily accessible, we highly recommend supplying them so we can provide a better-tailored output for you.
last_12_mths_transaction_count
integer
The number of transactions this merchant processed in the last 12 months.Example: 10000
collateral_held
integer
The total value of collateral held for risk prevention purposes. Whole number, no decimals.Example: 8000000
desired_insurance_limit
integer
Your desired insurance limit, if you have one — leave blank and we’ll propose one. Whole number, no decimals.Example: 8000000
website_url
string
The merchant’s website URL. The protocol (http:// or https://) can be omitted.Example: "www.timstiles.com"
company_registration_date
date
The official registration date of the merchant’s company, formatted as ISO 8601.Example: "2024-01-30"
registered_address_line_1
string
The first line of the merchant’s legally registered address.Example: "100 High Street"
registered_address_line_2
string
The second line of the merchant’s legally registered address.Example: "Suite 300"
registered_city
string
The city in which the merchant is legally registered.Example: "London"
registered_postal_code
string
The postal code or ZIP code of the merchant’s legally registered address.Example: "238884"