Introduction
This FAQ is designed to support Ezypay integration partners in understanding and troubleshooting the Ezypay Tap to Pay feature. As a mobile-based payment solution, Tap to Pay enables merchants to accept Visa and Mastercard payments—via physical cards or digital wallets like Apple Pay and Google Pay—directly through their mobile devices using NFC technology.
The following questions address common technical, operational, and compliance-related topics, including device compatibility, connectivity requirements, API integration, error handling, and transaction limits. Whether you're onboarding new merchants, testing in sandbox mode, or managing live transactions, this guide provides essential information to ensure a smooth and secure payment experience.
1. Why is Ezypay Tap to Pay not connecting for payments?
If a merchant experiences connectivity issues, please verify the following:
- The device has a stable internet connection.
- NFC (Near Field Communication) is enabled. If disabled, it must be manually activated.
If the issue persists, please get in touch with our support team at help@ezypay.com
2. Can Tap-To-Pay process payments when offline?
No. Ezypay Tap to Pay requires an active internet connection. Transactions are initiated from the Integrator’s platform, which sends a signal to the mobile device to activate. Only then can the card be tapped to complete the payment. Without internet connectivity, the device cannot receive the activation signal.
3. Does Ezypay Tap to Pay support all card types?
Card acceptance depends on configurations set by both the iIntegrator and Ezypay. In the initial rollout, only Visa and Mastercard will be supported.
To enable additional payment methods, merchants must submit a completed Change of Details form.
4. Will Apple Pay or Google Pay services be supported?
Ezypay Tap to Pay supports Visa and Mastercard cards stored in Apple Pay and Google Pay, provided they are used via NFC.
5. Are there any system monitoring or alerts on Ezypay’s side for offline status?
Ezypay does not currently have monitoring flags for offline status. We are only notified of a transaction once it has been successfully processed and an invoice is generated.
6. How does the partner platform trigger a Tap-To-Pay session?
Ezypay Tap to Pay sessions are activated via Ezypay’s API. The partner platform must send a payment initiation request (with amount, merchant ID, and transaction details) to Ezypay. Ezypay then signals the merchant’s mobile device to prompt for a card tap.
7. Is there a sandbox or test environment available?
Yes. Ezypay provides a sandbox environment where partners can simulate payment flows, including successful taps, declines, and error handling, without requiring the Ezypay Tap to Pay app. Merchants onboarded in sandbox mode cannot process live transactions until moved into production.
8. What are the typical Failed Payment Response Codes?
Ezypay returns standardised response codes that partners can map in their systems:
9. What are the minimum device and OS requirements?
Android: Version X and above, with NFC enabled.
iOS: To add details
Device must have Google Play Services & iOS enabled for updates and security patches.
10. Is Tap-To-Pay PCI DSS compliant?
Yes. Ezypay is PCI mPOC certified. Cardholder data is tokenised and never stored on the merchant’s device or the partner’s system. No additional PCI certification is required for partners, unless they choose to store card data themselves.
11. Can Tap-To-Pay be used for recurring payments?
No, Ezypay Tap to Pay is designed for one-off transactions only.
12. Can merchants use Tap-To-Pay on multiple devices?
Each device code can only be used on one device. If you wish to enable Ezypay Tap to Pay on an additional device, please download the Ezypay Tap to Pay app on the new device and request a new unique code from your integrator.
13. Are refunds and reversals supported?
Yes. Partners can trigger full or partial refunds via Ezypay’s Refund API. Refunds are always linked back to the original transaction reference to ensure traceability.
14. What should partners do if Ezypay Tap to Pay is failing across multiple merchants?
If a widespread issue is suspected, partners should escalate directly to the Ezypay Partner Support line instead of merchant support. Please include:
- Affected merchant IDs
- Device IDs (if applicable)
- Error codes observed
15. What is the flow of app registration?
Merchants will need to install the tap-to-pay apps in compatible devices, and a device ID will appear on the device screen. It will then need to be input into the partner platform to obtain a PIN via Ezypay’s API. Merchants are required to enter the PIN back into the app to complete the registration.
16. What is the transaction limit for tap-to-pay?
The maximum transaction limit per payment is $1,500 AUD.
17. What happens when a customer does not tap their card and the app times out?
If the customer does not tap their card within 2 minutes, the transaction will time out. The invoice status will read as “VOIDED”, once a webhook is sent (unless the webhook delivery fails). Integrators can also retrieve the status via the get terminal invoice API.
0 Comments