TRUSTODI
Last updated: June 10, 2026
Certain rails and currencies require supporting documents for a payment to be processed. Providing proper documentation reduces the chance of a Request For Information (RFI), payment failure, or refund. Please follow the guidance below.
| Payment reason | Supporting document(s) |
|---|---|
| CONSULTING_FEES | Invoice, contract, or agreement between parties |
| DOWN_PAYMENTS_FOR_REAL_ESTATE | Purchase contract, mortgage contract |
| EMPLOYEE_SALARIES_OR_WAGES | Employment contract, pay-slip |
| EXPENSES_REIMBURSEMENT | Receipts, expense reports |
| PURCHASE_OF_GOODS | Invoice, contract, or agreement between parties |
| PURCHASE_OF_SERVICES | Invoice, contract, or agreement between parties |
| REMITTANCE | Bank statement, remittance confirmation letter |
| RENT | Rental agreement |
| ROYALTIES | Invoice, royalty contracts |
To ensure consistent and reliable deliverability of payments, follow these best practices when submitting invoices as supporting documents. Failure to follow them may lead to RFIs, payment failure, or refunds.
Certain payments may trigger a Request For Information (RFI), where our compliance team or a banking partner requires more information about a payment. An RFI can be raised while a payment is processing or even after it has completed. RFIs are sent to your team, and you can then share them with your customer as needed. Responding as quickly as possible is critical — failure to answer an RFI may lead to the beneficiary being blocked, the payment being refunded, or further compliance action.
Need help with documentation for a specific corridor? Contact support@trustodi.com.