International payments are subject to anti-money laundering (AML) regulations and local reporting requirements that vary by destination country and payment rail. To satisfy these requirements, some corridors require structured compliance data as part of the Create Payment request. This data is used for transaction screening and regulatory reporting. It is not transmitted to the beneficiary.
Ripple Payments Direct 2.0 exposes three compliance fields on the Create Payment request:
purposeCode— the economic purpose of the paymentsourceOfCash— the origin of the funds being sentreceiverRelationship— the sender's relationship to the payment beneficiary
Whether a field is required or optional depends on the destination corridor. If you omit a required compliance field, the payment will fail validation.
purposeCode describes the reason for sending the payment. It is the most widely required compliance field and is collected by the majority of corridors.
Valid values are defined by each corridor's payment partner and local rail. Common categories include commercial payments (goods, services, invoices), personal transfers (family support, salary, education), and financial transactions (investment, savings). The specific codes accepted (and their labels) vary by destination.
sourceOfCash indicates where the funds being sent originate. It is used by some corridors for enhanced AML screening, particularly in markets where source-of-funds declarations are a local regulatory requirement.
Valid values represent categories such as business income, salary or wages, savings, investment returns, and loan proceeds. As with purposeCode, accepted values vary by corridor.
receiverRelationship describes the sender's relationship to the payment beneficiary. It is used in certain corridors to support transaction risk assessment, particularly for consumer remittance use cases.
Valid values represent relationship types such as employee, supplier, family member, spouse, or self (for transfers between the sender's own accounts). Accepted values vary by corridor.
Valid values for all three fields are documented in the Integration resources section, organized by destination region, country, and currency. If a corridor is not listed there, no compliance fields are required for that corridor.
Not all three fields are required in every corridor. Check the relevant corridor page in Transaction resources to confirm which fields are required, which are optional, and which valid values apply.