Skip to main content
Use this page to test your integration without making assumptions about unsupported environments.

​
Current environment model

Do not send test traffic to an arbitrary staging URL unless Kyren has issued credentials for that environment.

​
Test API Keys

Use an API key issued for the target environment:

​
Test Card Numbers

Use these card numbers only when Kyren has issued a staging or test-capable environment, or when Kyren has enabled a test-capable payment gateway for your merchant. Do not assume these card numbers produce deterministic outcomes on production checkout sessions. For all test cards:
  • Use any future expiration date (e.g., 12/28)
  • Use any 3-digit CVV (e.g., 123)
  • Use any cardholder name
  • Use any billing address

​
Test WeChat Pay / Alipay

QR payment behavior depends on the gateway configuration attached to your merchant. Use Kyren-provided credentials for the target environment or coordinate a callback simulation when validating asynchronous status updates.

​
Testing Webhooks

When testing webhooks locally, you can use a tunneling tool like ngrok to expose your local server:
Then configure the ngrok URL as your webhook endpoint in the Dashboard:
Remember to update your webhook URL to your production endpoint before going live.

​
Going Live Checklist

Before switching to production, make sure you have:
1

Replace API keys

Use the production key issued for api.kyrenpay.com
2

Update base URL

If Kyren issued a staging base URL, change from that URL to api.kyrenpay.com
3

Update webhook URL

Set your production webhook endpoint in the Dashboard
4

Verify webhook signatures

Ensure your server correctly verifies X-Kyren-Signature headers
5

Handle errors gracefully

Test error scenarios and ensure your app handles them properly