TEST ENVIRONMENT

Test Cards, UPI IDs and Wallets

Plan and validate complete payment journeys in FiatPe Test mode before enabling Live transactions.

Important: Test cards only for Test environment. These test cards, UPI, and Wallet credentials must only be used in the UAT environment. Using these test cards in production environment may cause validation error.

OVERVIEW

Testing Overview

The FiatPe UAT environment allows you to test payment flows, request and response handling, webhook callbacks, and failure scenarios without processing real transactions.

UAT Environment

Use UAT credentials and test values to simulate payments safely before going live.

https://api.fiatpe.com

End-to-End Validation

Validate order creation, payment link flows, UPI payments, webhook handling, and final payment status updates.

create → pay → verify → webhook

Test outcomes, not only success

Cover declines, authentication, pending states, cancellation, expiry, retries, and duplicate callbacks before release.

success · failed · pending · cancelled

Verify on your server

Treat the browser result as provisional. Verify the returned signature and authoritative payment status before fulfilment.

checkout → signature → status → fulfil

Keep Test and Live isolated

Use Test keys, synthetic customer data, and separate webhook endpoints. Never enter real card or banking details.

Test every payment method

Exercise cards, UPI, wallets, and net banking because redirects, authentication, and failure behavior differ.

Reconcile asynchronous results

Test delayed and repeated webhooks, then confirm your status API and idempotent handlers reach one final result.

Complete a go-live rehearsal

Validate order creation, checkout, return URL, signature verification, webhook receipt, and fulfilment as one journey.

FiatPe testing recommendation

Test multiple payment outcomes, verify signatures on your server, reconcile the final payment status, and confirm that repeated or delayed webhooks are handled safely. The FiatPe credentials and behavior documented on these pages are authoritative for your integration.

Before moving to production, make sure your integration handles success, failed, pending, cancelled, and expired payment scenarios correctly.