Prepare device accounts, packages and test environments
Keep merchant Test Mode, device key type and SDK environment aligned before trying a payment.
Enable the product on the correct account
Tap to Pay must be enabled in the Partner and Merchant portals. Physical encrypted readers require the Encrypted Devices service. Create an API-source key for the merchant and configure the application identifier for SDK paths that use it. An account key does not itself enable a hardware service.
Distinguish three independent settings
Merchant Test Mode prevents processor submission. SDK Test/Live selection chooses the SDK platform. A device’s injected test or production keys determine which environment it can use. Do not assume changing one setting changes the others. Setting Verify before testing Merchant Test Mode Enabled in the Merchant Portal for a non-processing test. SDK environment Matches the account and intended test setup. Hardware/card type Test cards with test devices; production hardware/card pairing follows the documented Test Mode workflow.
Obtain the matching SDK package
Use the platform download source and release-bundle documentation. Android packages include Java/Kotlin examples and binaries; iOS includes its sample client and dependencies. Full and Lite have different features and OS minimums. Do not copy dependency versions between unrelated release bundles.
Keep testing distinct from a launch
Gateway Test Mode can approve valid inputs without sending them to the processor. It is useful for hardware integration but cannot verify real settlement. Record the environment with each test result and verify the intended mode before an approved production rollout. No account mode was changed by this documentation work.