Skip to content
All questionsOperations and disputes

How do I test payments before launch?

Testing a successful payment is not enough: declines, refunds and repeat notifications are what usually break in production. Walk each scenario end to end — from creating the payment to what your own system finally shows.

Scenarios to walk through

  • Successful payment. The order becomes paid and the receipt reaches the buyer.
  • Decline. The buyer sees a clear message and the order is not marked paid.
  • Refund. Full and partial — check the amounts match and each gets a receipt.
  • Repeat notification. A second message about the same payment must not change the order twice.
  • Unreachable handler. Make sure an order can still be closed by fetching the status manually.

How it works in MulenPay

The integration is built on the REST API: the store creates a payment, the buyer pays on the MulenPay page, and the store learns about a status change from a webhook sent to the address in the settings. The status of any payment can be fetched by its id, and a webhook resend is triggered from the dashboard or by request. The dashboard shows webhook statistics: which response codes your server returned. Methods, formats and the signature are described at docs.mulenpay.com. For platforms with a ready-made module — WordPress, 1C-Bitrix, OpenCart, PrestaShop and others — you test settings rather than code: keys, the notification address and order status mapping.

Before live traffic

  • The keys in settings belong to the live store, not a test one.
  • The notification address points at production over HTTPS, not a developer tunnel.
  • Logging of incoming notifications is on.
  • The test order amount fits the limit per operation: 10 to 300,000 roubles.

Step by step

  1. Create a payment for the minimum amount and pay it yourself.
  2. Check that the order became paid, the webhook is logged and the receipt reached your email.
  3. Issue a partial refund from the dashboard and confirm the order reflects it.
  4. Resend the webhook from the dashboard and check the order did not change.
  5. Stop the handler, create a payment, then start it and close the order by fetching the status.
  6. Repeat the first step through SBP and a Pay service.

How the integration works is on the payment API page. What a webhook is and how to handle it is covered separately.

Payment APISee how this works at MulenPay

More questions on this topic

Still have questions?

Write to us — we will answer and help you start accepting payments.

Let’s talk about your project

Setup, pricing or support — choose the way you prefer to get in touch.

Write to the team

Your name and one contact are enough. Add details if you wish.

How should we contact you?

By clicking the button you agree to the processing of personal data.

TelegramTelegram