Skip to main content
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.

Test Card Credentials

Use the following details when testing K-Net debit card payments in the sandbox:
FieldValue
BankKnet Test Card
Card Number888888-0000000001
Expiry09/2030
PIN1234

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.
OperationEnvironmentURL
Payment InitializationTesthttps://development.payzah.net/ws/paymentgateway/index
Payment InitializationProductionhttps://payzah.net/production770/ws/paymentgateway/index
Payment Status CheckTesthttps://development.payzah.net/ws/paymentgateway/get-payment-details
Payment Status CheckProductionhttps://payzah.net/production770/ws/paymentgateway/get-payment-details
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.