Skip to main content

Payment Issues

This page covers common problems with each payment method and how to resolve them.

QR Code Not Generating​

Symptoms: Clicking UPI/QR payment shows an error or a blank screen instead of a QR code.

Solutions:

  1. Check Razorpay configuration -- ensure your Razorpay API keys are correctly configured in the store settings
  2. Verify Razorpay account -- log into your Razorpay dashboard and check that QR code generation is enabled and your account is active
  3. Network connectivity -- QR generation requires an API call. Check your internet connection
  4. Amount limits -- Razorpay may have minimum or maximum amount limits for QR payments

Card Payment Failed​

Symptoms: The Razorpay payment form shows an error, or the payment is declined.

Solutions:

  1. Card declined -- the customer's bank declined the transaction. Ask the customer to try a different card or payment method
  2. Razorpay SDK error -- refresh the page and try again. Check the browser console for specific error messages
  3. 3D Secure timeout -- if the customer's bank requires 3D Secure and the authentication times out, retry the payment
  4. Check Razorpay dashboard -- log into Razorpay to see the payment status and any error details

Terminal Not Connecting​

Symptoms: Ezetap terminal payment is initiated but no response is received, or the terminal shows an error.

Solutions:

  1. Check terminal power and connectivity -- ensure the Ezetap device is on and connected to the network
  2. Verify Ezetap configuration -- confirm the terminal ID and API credentials in store settings
  3. Restart the terminal -- power cycle the Ezetap device
  4. Cancel and retry -- use the Cancel button in the POS to abort the current attempt, then try again

Split Payment Stuck​

Symptoms: A split payment is partially completed but cannot proceed to the next split.

Solutions:

  1. Check individual payment status -- each split is an independent payment. If one fails, retry that specific split
  2. Network timeout -- if the POS lost connectivity during a split, refresh and check order status
  3. All splits must complete -- the order is only finalized when every split is paid

Duplicate Order Concerns​

Symptoms: Worried about duplicate charges after a network timeout during payment.

Resolution: Swift POS uses idempotency keys for all payment operations. If a network timeout occurs:

  • Retrying the same payment operation is safe
  • The backend detects the duplicate request and returns the original result
  • No duplicate orders or charges are created
info

If you are unsure whether a payment went through, check the order list. If the order appears, payment was successful. If not, it is safe to retry.