Payment Gateways Tokenization Overview

Implemented

• CIM - requires payment profile ID (payment token) and customer profile ID (customer ID)
• Braintree - requires payment method token (payment token) and customer ID (customer ID)
• Chase - requires customer profile ID (payment token)
• First Data - requires transamor token (payment token)
• QBMS - requires wallet entry ID (payment token) and customer ID (auto-generated)
• Moneris - requires data key (payment token)
• NETbilling - requires transaction ID (payment token)

Not yet implemented

• beanstream - requires card ID (payment token) and profile ID (customer ID)
• securenet - requires payment method ID (payment token) and customer ID (provided or auto-generated)
• usa e-pay - requires card ref (payment token)
• elavon (converge ) - requires token (payment token)
• realex (direct) - requires card ref (payment token) and payer ref (customer ID)