Before processing real payments, you should thoroughly test your integration using Payzah’s sandbox environment. The sandbox mirrors production behavior exactly, allowing you to simulate successful transactions and error scenarios without moving real money. Use the test credentials and endpoints below to verify every part of your integration end-to-end.
All test credentials listed on this page are exclusively compatible with the test endpoints. Sending these card details to production endpoints will result in failed or rejected transactions. Refer to the endpoint table below to ensure you are pointing to the correct URLs.
Public Sandbox API Key
You do not need a merchant account to start testing. Use the shared sandbox key below to run requests against the test environment straight away.
This value is already Base64-encoded, so paste it into the Authorization header exactly as shown — no further encoding needed.
This key belongs to a shared demo account, so transactions created by other developers will also appear against it. Treat any data you see as public, and never send real customer details through it.
This key works only on the test environment. It cannot authenticate against production. Register through the Payzah app to receive your own private key before going live.
Test Card Credentials
K-Net (Debit)
Visa
MasterCard
Apple Pay
Use the following details when testing K-Net debit card payments in the sandbox: Use the following details when testing Visa credit card payments in the sandbox: Use the following details when testing MasterCard credit card payments in the sandbox: Use the following details when testing Apple pay, but you need to have a developer account with apple to add these cards and accept payments in the sandbox, else you can go live and you will see the apple pay enabled automatically:Card 1Card 2
Test vs. Production Endpoints
Payzah provides distinct URLs for each environment. Make sure your integration reads the base URL from a configuration variable so you can switch between environments without changing code.
Before switching your integration to the production endpoints, complete a full round of User Acceptance Testing (UAT). Cover every integration point — successful payments, declined cards, cancelled transactions, and status-check polling — so you can go live with confidence and minimize support issues.