Payment Gateways Tokenization Overview
Max Rice edited this page Oct 12, 2015
·
1 revision
- 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)
- 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)
- Home
- General Usage
- Payment Gateways
- WooCommerce Blocks
- Updating
- Testing
- Workflow