A Guide to RMS Pay Terminology
Overview
This data dictionary explains the key fields and event types used in RMS Pay transaction and settlement reports. It’s designed to help you understand what each data point means and how it relates to the payment lifecycle, from authorisation through to settlement and payout.
Information
The information below will help you:
Reconcile transactions and payouts more easily
Identify where a payment is in its lifecycle
Understand how different events (such as refunds, chargebacks, and settlements) are recorded
Each entry includes the field name or event code and a plain-language description of its purpose within RMS Pay reporting.
| TYPE/EVENT CODE | DESCRIPTION |
|---|---|
| PSP Reference | RMS Pay unique identifier for the transaction |
| Merchant Reference | RMS's merchant reference for this transaction |
| ModifiedPSPReference | When a payment undergoes a modification, a new PSP reference specific to that modification is generated. This means that the original payment and each of its modifications (e.g., a refund or capture) have distinct PSP references. |
| CardSummary | Last four digits of the credit card |
| ShopperStatement | Text that appears on a shopper's bank or card statement after making a purchase. |
| AccDate | Date which transaction occurred in RMS. EventDate is the Adyen Event Date this can be different to the Accounting Date. The first record is an example of this. The Customer rolled to the new Accounting Date 16-May-2025, however the transaction was done after 10:30pm on 15-May-2025 |
| EventDate | Timestamp indicating when the event was captured by the payment gateway |
| Settled Date | Date when funds processed are transferred to the property bank account |
| Authorisation | Indicating that the payment request has reached the issuing bank, and a decision (see : Type ) has been returned. |
| Cancellation | This is specific to cancelling a pre-auth |
| Capture | Occurs when when a PreAuth is Completed/Used |
| Chargeback | The payment was reversed by the customer, and the issuer has started a dispute process. RMS Pay withdraws the disputed funds from your account. You can accept the chargeback or supply defense documents. If you accept the chargeback, this is the final status. |
| ChargebackReversed | You defended the chargeback successfully, or the customer re-paid the funds. RMS Pay has transferred the funds back to your account. If the defense is successful, this is the final status. |
| SecondChargeback | You were not successful in your defense of the first chargeback. This is the end of the dispute process and a final status. |
| Refund | The financial institution has refunded the customer and the funds have been deducted from your account. |
| RefundedReversed | The refund was returned. This means that the funds have been returned to RMS Pay and are back in your account. This can happen if, for example, the customer's bank account details have changed. We recommend that you contact the customer to check their bank account details before retrying the refund. |
| Token | Token details have been received |
| Pre-Auth | Temporary hold placed on a credit or debit card to reserve funds for a transaction before the actual charge is captured. |
| PreAuthCancellation | This action lifts the hold on the customer's funds, returning them to the card once the issuer completes the cancellation process. |
| Cancel | Payment that has been cancelled. |
| Payment | A request initiated by the property and processed via RMS Pay to transfer funds from a credit/debit card or digital wallet to the property's account. |
| Cancel_or_refund | The financial institution has refunded the customer and the funds have been deducted from your account. |
| Settled | Transaction data has been received, RMS Pay settlement process has occurred and fees have been applied (there may only be 2 hours difference between settled and paid out as this process occurs at T+2) |
| Paid Out | RMS pay settlement process has occurred and payout to bank account has been triggered |
Comments
0 comments
Please sign in to leave a comment.