Test payments before going live

Use Sandbox to test your checkout, test cards and payment flow before taking real payments

The basics
Sandbox is Paypercut’s practice environment. You can go through checkout, simulate a successful or failed payment and check whether your store reacts correctly, without charging a real card.

What Sandbox is and when to use it

Sandbox is Paypercut’s practice environment. You can test payment links, plugin checkout, wallet and 3D Secure scenarios and order updates without moving real money. Your Sandbox and Live accounts are separate.

Enable Sandbox before your account goes live

Enable Sandbox during account setup if you want to test Paypercut. To access it, open the account selector in the top-right corner of your dashboard and choose your Sandbox account.

Switch to Sandbox

  1. Sign in to dashboard.paypercut.io.
  2. Open the account selector in the top-right corner.
  3. Select your Sandbox account. If you have not created one, follow the option shown in the selector to create a sandbox account.
  4. Check that you are viewing the Sandbox environment before testing.

Connect your store or payment form to Sandbox

  1. If you use an e-commerce plugin, open its Paypercut settings.
  2. Select Test or Sandbox mode and provide your Sandbox API Secret if required.
  3. Use Test connection when available. Check the webhook configuration for your store.
  4. Keep Production keys out of the test setup.

Make the first test payment

  1. Create a test order or payment link.
  2. Open the checkout and use one of the official test card numbers listed below, with a future expiry date and any CVV.
  3. Repeat with both a successful 3D Secure card and a failed-authentication card.
  4. Go to Dashboard → Payments and check the outcome.
  5. Check the corresponding order status in your shop.

Official test cards: successful authentication and challenges

Card number Brand Tests
5204 2477 5000 1471 Mastercard Successful frictionless 3DS authentication (no extra customer step)
4005 5622 3121 2123 Visa Successful 3DS challenge, method not required
4761 3699 8032 0253 Visa Successful mandated challenge
4000 0000 0000 0341 Visa Successful out-of-band challenge

Official test cards: failed and unavailable authentication

Card number Brand Tests
4264 2815 1111 2228 Visa 3DS authentication fails
5405 0011 1111 1165 Mastercard 3DS authentication unavailable
4055 0111 1111 1111 Visa 3DS challenge fails
4264 2815 0000 3339 Visa 3DS directory server error
4264 2815 0000 1119 Visa Internal 3DS server error

Official test cards: additional scenarios

Card number Brand Tests
4000 0000 2222 2220 Visa / Cartes Bancaires Co-branded card recognition
4571 0099 0000 0003 Visa / Dankort Co-branded card recognition
5555 5500 9999 9999 Mastercard / Cartes Bancaires Co-branded card recognition
5550 0099 0000 0005 Mastercard / Bancontact Co-branded card recognition
4111 1111 1111 1111 Visa Authentication attempted
4005 5717 0111 1111 Visa Attempted challenge authentication

What to check after testing

  1. Did the shopper see the intended challenge or failure?
  2. Did the Paypercut payment show the correct final status?
  3. Did your online shop mark only successful payments as paid?
  4. For declined tests, did your shop leave the order unpaid and offer a sensible next step?

Go live only after verification

  1. Complete Paypercut account verification and obtain your Production API key.
  2. Change the store integration to Production, save the live key and confirm webhook configuration.
  3. Place one small real payment and check both dashboard and shop order status.
  4. Do not send goods until the payment is confirmed as succeeded.

Official Paypercut documentation

For advanced configuration and technical details, see the official Paypercut documentation.

Open documentation


Need more help?

Find the right support contact for your question.

Contact support