PlexySDK DOCS

Test vs Live Payments

Run simulated transactions with a test API key, then switch to live keys for production

Test vs Live Payments

Plexy uses a single API endpoint (api.plexypay.com) for both test and live traffic. The API key you send determines the mode — test keys produce simulated transactions, live keys move real money.

Test payments

Use a test API key (prefix pr_) to run transactions against the live environment without charging real cards. No money is moved, and results are deterministic based on the card you submit.

Find your test API key in the dashboard under Settings → API keys. Test keys are shown alongside live keys — copy the one labeled Test.

Use this card for successful test authorizations:

Card numberExpiryCVCCardholder nameResult
4111 1111 1111 1111Any future dateAny 3 digitsAny value or omit itAuthorised
curl -X POST https://api.plexypay.com/v2/payments \
  -H "x-api-key: pr_..." \
  -H "Content-Type: application/json" \
  -d '{
    "amount": { "value": 10000, "currency": "KZT" },
    "paymentMethod": {
      "type": "scheme",
      "number": "4111111111111111",
      "expiryMonth": "03",
      "expiryYear": "2030",
      "cvc": "737"
    },
    "reference": "test_order_1",
    "returnUrl": "https://your-site.com/checkout/complete"
  }'

Live payments

Switch to a live API key (prefix pr_) once your integration is verified and your account is approved for production. Live keys process real cards and move real money — test cards like 4111 1111 1111 1111 are rejected in live mode.

Never commit API keys to source control. Store them as environment variables or in a secrets manager, and use separate keys per environment.

On this page