CardConnect specification
|
🛈 Important This topic applies only to CardConnect |
|
Item |
Support |
Notes |
|
Region(s) |
North America |
|
|
Gateway or Processor |
Gateway |
|
|
Processor / Acquirer supported |
Fiserv / First Data |
|
|
Provider website |
Yes |
|
|
Omni channel tokenization between in-store and on-line |
Yes |
|
|
Gift card program via provider |
Yes |
|
|
System status |
|
|
|
Channel support |
|
|
|
D365 Finance (SOP) |
Yes |
|
|
Commerce – Call center |
Yes |
|
|
Commerce – Online Storefront |
Yes |
|
|
Commerce – Retail POS |
Yes |
|
|
External e-Commerce |
Yes |
|
|
Retail POS |
|
|
|
Retail Modern POS supported |
Yes |
|
|
Cloud POS supported |
Yes |
|
|
Android Hybrid App POS supported |
Yes |
|
|
Android POS all-in-one devices available |
No |
|
|
Payment terminal devices |
|
|
|
Supported devices |
Ingenico IPP320 Ingenico ISC250 Ingenico ISMP4 Clover Mini (with built in printer) Clover Flex (with built in receipt printer) |
|
|
Device connectivity |
Wifi, LTE, RJ45 cable, Bluetooth* |
*Connectivity is device specific. Refer to specific device specification. |
|
Device encryption / security |
P2PE 2.0 Validated and PCI level 1 data center |
|
|
Local/cloud connectivity |
Cloud (standard) |
|
|
Offline processing on the payment terminal |
Yes3 |
|
|
Payment methods accepted |
Cards brands: VISA Mastercard AMEX Discover Interac (Canada) |
|
|
US Pin Debit |
Yes1 |
|
|
Wallet support |
ApplePay GooglePay |
|
|
Entry methods |
Swipe Dip/enter (Chip) Contactless Manually keyed into the payment terminal |
|
|
Third party application required |
No |
|
|
Line display support |
Yes |
|
|
Signature capture support |
Yes |
|
|
Bypass pin debit |
Yes |
|
|
Microsoft Dynamics 365 payment compatibility |
|
|
|
Omni channel payments supported |
Yes |
|
|
Omni-channel commerce order payments supported |
Yes |
|
|
Reconciliation available via MAX Pay Controller |
Yes |
|
|
Provider specific details |
|
|
|
Customer token profiles (Vaulted token) |
Yes |
|
|
Payment provider payments portal |
Yes |
Cardpointe |
|
Test account available |
Yes |
Via Retail Realm |
|
MPG additional non-standard value-added functionality |
|
|
|
Tokenization (card on file) at the Point of Sale |
Yes |
|
|
Customer Token list and card management at the Point of sale |
Yes |
|
|
One-time tokens for Call center payments |
Yes |
The ability not to store (hide) Customer tokens for certain sales orders. |
|
Credit card token and payment line import from a 3rd party system (e.g., external e-Commerce platform) |
Yes |
|
|
Payment terminal devices at Call center |
Yes |
Use “Call center as a POS” to process a full EMV retail payment transaction or use to acquire a token |
|
Call center multiple MIDs per Legal entity |
Yes |
|
|
Call center pre-pay default management |
Yes |
|
|
Capture electronic signature from the payment terminal for on-account transactions at the Point of sale |
Yes |
|
|
Consolidated unique Customer token from POS generated sales orders |
Yes |
|
|
Provider value-added services |
|
|
|
Token import from another provider |
Yes |
Subject to survey / analysis |
|
MAX Pay Global Roadmap items |
|
|
|
ACH |
|
ACH Check processing |
Notes
- Pin debit is device specific and is not currently supported on the Clover range of devices.
- Purchase tokenization (sale using a stored card instrument) is device specific and is not currently supported on the Clover range of devices.
- Standard range of Bolt devices provide stand-alone fallback payment processing capability in the event of internet failure.
.
Disclaimer
This page details the general specification for CardConnect. Specifications are subject to change without notice and all information has been verified correct at the time of compilation. E&OE