Plan Direct Connect and EMV validation
Distinguish direct terminal certification from a pre-integrated SDK or Cloud API implementation.
Choose Direct Connect for terminal integration
Direct Connect is an API-led option for device manufacturers implementing EMV contact/contactless, magstripe and keyed processing. Java and .NET packages supplement the protocol. Access to the integration guide and packages is supplied through the program contact; this public guide cannot substitute for that restricted package.
Plan the production gates
The source requires EMV Level3 certification for each supported processor, solution verification and secure device key injection. Passing a sandbox request does not establish certification. Agree device models, processor scope and verification cases before building a deployment schedule.
Select an EMV sandbox case
Place the exact case name in Request/TransactionDetails/Reference. The sandbox checks the request against that case and returns validation details. Although this overview has a Coming Soon setup subsection, the separate public Getting Started page supplies the test endpoint and access procedure; follow the EMV sandbox workflow guide.
Interpret validation feedback
Read Response/Result/PaymentProviderError. Multiple ICC-tag issues are separated with |, and multiple issues for one tag with semicolons. Compare required tags, length, format, terminal capability bits, country/currency and cryptogram inputs with the chosen test case. An expected decline test can succeed by returning its specified decline.
Use the NFC simulator only on test terminals
The Android Card Simulator uses NFC Host Card Emulation and pre-recorded test scenarios. It requires Android 5/API21 or later plus NFC, and supports selected brand and CVM outcomes. Set it as the default contactless app when prompted, choose the scenario and tap a test terminal. It neither creates real payments nor proves production certification.