The Terminal ID Field that is submitted in a Transport Create Transaction API request is used to fulfill the MasterCard Register Number requirement. Although this is a MasterCard requirement, each processor has a different format or standard for how they require this field to be sent in. We are adding the handling of this field into our available processors and products.
The implementation of the Terminal ID field within the POS should be flexible. There are a few requirements that it should meet in order to enable the use of any processor.
Notice: Most platforms will not accept a value of 0 within the Terminal ID field. To ensure compatibility with all platforms it is recommended to prevent any value less than 1 if your software allows configuration of this field.
The addition of the Terminal ID field is fairly simple, but it is important to handle the values submitted with care. Ensuring that the field is configurable will prevent restrictions related to which platform a customer can be configured for.
For additional questions on how to handle the use of the Terminal ID field for the MasterCard Register Number requirements please contact Certification Engineering at developer@cayan.com
| Processor/Platform | Value Required | Example |
|---|---|---|
| Vantiv IBM | 2 digits exactly | 01 |
| Elavon | 8 digits exactly | 01234567 |
| Rapid Connect | 8 digits | 01234567 |
| WorldPay | 2 digits exactly | 01 |