- All active merchants on your platform
- One row = one legal entity, not per PSP account
- Send via email or SFTP
Identity
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)The type of registration ID based on the country where the merchant is registered.Example:
"UEN" (SG) or "SOS" (US)The country where the merchant is legally registered, as a two-letter code per ISO 3166 alpha-2.Example:
"SG"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
A comma-separated list of Merchant Category Codes (MCC).Example:
"5251, 5714"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"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"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"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:
8000000Risk & exposure
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: 135000The 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: 14Optional 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.The number of transactions this merchant processed in the last 12 months.Example:
10000The total value of collateral held for risk prevention purposes. Whole number, no decimals.Example:
8000000Your desired insurance limit, if you have one — leave blank and we’ll propose one. Whole number, no decimals.Example:
8000000The merchant’s website URL. The protocol (
http:// or https://) can be omitted.Example: "www.timstiles.com"The official registration date of the merchant’s company, formatted as ISO 8601.Example:
"2024-01-30"The first line of the merchant’s legally registered address.Example:
"100 High Street"The second line of the merchant’s legally registered address.Example:
"Suite 300"The city in which the merchant is legally registered.Example:
"London"The postal code or ZIP code of the merchant’s legally registered address.Example:
"238884"