User details for AML

Learn what details you must provide with your payments to help prevent crime.

TrueLayer provides payment initiation services (PIS) on your behalf if you do not have your own PISP license. This means you must provide certain user details with each payment you create with the Payments API, which is used as part of anti-money-laundering (AML) measures.

As part of these measures, TrueLayer screens all transactions to and from merchant accounts. This prevents transactions that could be related to money laundering or sanctioned individuals. If a transaction is flagged for such an issue, we will contact you to request more information.

The user details you need to provide, and the method you use to provide them, vary based on the type of payment. We provide an overview of the information required on this page. There's more detailed guidance in the documentation for each payment type.

📘

Repeated payments

Even if you receive regular payments from a user, you should still collect payment details for each payment they make.

This page explains the minimum required user details you must collect. However, you can collect more information than this.

Single payments

When you create a payment with the Payments API, you provide user details as part of the user object in the payment creation request. The available fields for the user object are a user id, name, email, phone, date_of_birth and address.

When you create a payment, you must include the user's name, and either their email address or phone number.

Learn more about providing user details as part of single payments.

Variable recurring payments

When you create a mandate with Payments v3, you provide user details as part of the user object in the payment creation request. The available fields for the user object are a user id, name, email, phone, date_of_birth and address.

When you create a mandate, you must include the user's name, and either their email address or phone number.

Learn more about providing user details as part of variable recurring payment mandates.

Closed-loop payout

A closed-loop payout is a payout made back to an account based on the payment_source of an initial single payment. As user details were already collected in the initial single payment, there's no requirement to collect user details for a closed-loop payout.

Open-loop payout

An open-loop payout is a payout made to an external_account and is not linked to an initial payment. The available fields related to user details for the external_account object are an account_holder_name, date_of_birth and address.

When you create an open-loop payout, you must include the account holder's name and date of birth.

Refunds

A refund is a payment, or payments, made back to an account based on the id of an initial single payment. As user details were already collected in the initial single payment, there's no requirement to collect user details for a refund.