The RAM Tool is full of helpful information and features for you to discover. Please follow the below to get started.
Video tutorial
Upon receiving login details from Trust Payments, you may access RAM Tool using the following link: https://www.omnipaygroup.com/ramtool
Enter your username and password.
Once logged in, we first request that you change your password for security reasons. You can do this by navigating to Customer Service > Change Password.
Our password policy specifies the following requirements to be met when setting a new password:
- Passwords must contain at least 1 numeric character.
- Passwords must contain at least 1 alphabetic character.
- Passwords must be at least 8 characters long.
- None of your last 6 passwords can be re-used as your new password.
Remember that passwords are case-sensitive!
Merchant identifiers
Every merchant can be identified in two ways:
- An internal Merchant Identificant Number (MID) - The MID is up to 8 digits long and is used by OmniPay to identify the merchant within their own systems.
- An external merchant number - The institution identifies the merchant by its external merchant number. This is typically the identifier that would be used within the institution’s own processing systems. The external merchant number can be up to 20 digits long.
If the RAM Tool prompts you to enter a merchant number, in most scenarios both the MID and the external merchant number are supported. If you enter an 8-digit number, the RAM Tool assumes that the number is a MID. Otherwise, the RAM Tool assumes that the number is an external merchant number.
Switching between merchant numbers
If you have multiple MIDs, such as MOTO and e-commerce MIDs or multiple shops, you can switch between them by following these steps:
- Click the drop-down MID menu found at the top of the page.
- Click the button.
- Select a merchant number.
Posting dates
Presentments, chargebacks, merchant notes and many other items shown in the RAM Tool are assigned a posting date. The posting date is the internal date showing when the relevant transaction was processed on our system.
Be aware that the posting date of a given transaction does not necessarily correspond with the calendar date it was first received. For example, all transactions processed overnight from the evening of 5th March to the morning of 6th March (OmniPay local time) will have a posting date of 6th March.
The posting date is used when performing date-based searches (e.g. a search for all processed batches within a given date range) and also to calculate summary totals, such as the total value of all presentments submitted for an institution.
Specifying date ranges in searches
Many types of searches you can perform require a start and end date to narrow your search. You can either type this in using the format DD/MM/YYYY or click the calendar icon to select the date from a calendar. Please ensure that the start date specified is before the end date.
To avoid overburdening the server, some pages restrict the number of days that can be spanned by a single query (i.e. the number of days between the start and end dates). If the range specified in your search is too large, the RAM Tool will automatically change the start date to bring it in line with system restrictions. When this happens, the changed date is highlighted on the form in red.
About account types
Transactions are credited and debited to various accounts within the OmniPay accounting system. Every account is maintained in a particular account currency (e.g. USD, GBP, EUR, etc.). Any transactions posted to an account that has a different account currency are converted using the appropriate foreign exchange rates, such as the card scheme rates or the OmniPay rates.
Various functions on the RAM Tool require you to select an account to perform an operation (e.g. selecting an account to search for transactions). There are two account types:
- PAR (Payment Account Retail) - The account where merchant batches are posted and payments are generated.
- Acquirer Dispute Account - The account that receives incoming chargebacks, debits chargebacks to other merchant accounts, or is used to otherwise write off or re-present chargebacks.
Capture methods
The OmniPay accounting system assigns a capture method to every presentment transaction. The capture method is an internal accounting system code that describes how the transaction data (specifically the card number) is captured. The capture method is essentially a code that combines the meaning of various card scheme fields such as:
| Capture Method | Description |
| Recurring | Recurring transaction |
| SET/3D-SET authenticated | For Visa, this capture method indicates a Verified by Visa electronic commerce transaction. The capture method corresponds to Visa ECI 05. For Mastercard, this capture method indicates a UCAF (Universal Card Authentication Field) electronic commerce transaction with the UCAF data populated. The capture method corresponds to a Mastercard UCAF Collection Indicator value of 2 (the UCAF Collection Indicator is in position 3 of the Electronic Commerce Security Level Indicator field in the Mastercard clearing message). |
| SET/3D-SET non-authenticated | For Visa, this capture method indicates an electronic commerce transaction with a merchant which supports Verified by Visa, where the merchant attempted to authenticate the cardholder using Verified by Visa. The capture method corresponds to Visa ECI 06. For Mastercard, this capture method indicates an electronic commerce transaction where the merchant supports UCAF, but the UCAF data was not provided by the cardholder/issuer. The capture method corresponds to a Mastercard UCAF Collection Indicator value of 1 (the UCAF Collection Indicator is in position 3 of the Electronic Commerce Security Level Indicator field in the Mastercard clearing message). |
| eCommerce, non-secure | An electronic commerce transaction where the card details are transported to the merchant in the clear. For Visa transactions, the capture method corresponds to Visa ECI 08 For Mastercard transactions, the capture method corresponds to a Mastercard Security Protocol value of 9 (the Security Protocol is in position 1 of the Electronic Commerce Security Level Indicator field in the Mastercard clearing message). |
| eCommerce, Channel Encrypt | An electronic commerce transaction where the card details are transported to the merchant in encrypted form. This is the capture method assigned to normal SSL-based electronic commerce transactions. For Visa transactions, the capture method corresponds to Visa ECI 07. For Mastercard transactions, the “eCommerce, Channel Encrypt” capture method corresponds to a Mastercard Security Protocol value of 2 (meaning “channel encryption”). The Mastercard Security Protocol field is position 1 of the 3 position Electronic Commerce Security Level Indicator field in the Mastercard clearing message. For Mastercard transactions, the “ecommerce, Channel Encrypt” capture method may then be followed by the value of the UCAF Collection Indicator as received in the incoming transaction. The UCAF Collection Indicator is position 3 of the 3 position Electronic Commerce Security Level Indicator field in the Mastercard clearing message and is shown in round brackets. In summary, the following Capture Method texts are shown for Mastercard electronic commerce transactions:
|
