CP

CloudPayments emulator

admin — changes apply immediately, defaults come from config

Terminals (Public ID / API Secret)

Basic-auth allow-list. A wrong pair gets the documented 401 with an EMPTY body and WWW-Authenticate: Basic realm="CloudPayments". The API Secret also signs webhooks (Content-HMAC / X-Content-HMAC).

Webhook endpoints

Per-kind notification URLs (merchant-cabinet model). Empty = disabled (env default applies when set). Check is delivered synchronously and vetoes payments with codes 10/11/12/13/20 — or on any delivery failure.

Transactions

Actions transition state immediately and fire the matching webhook. "re-notify" re-fires for the CURRENT state (duplicate-delivery testing).

Card tokens

Subscriptions

No real timers: "charge now" runs one billing tick with the documented semantics (24h retry ⇒ PastDue after 1–2 failures, 3 strikes ⇒ Rejected, MaxPeriods ⇒ Expired).

Orders (payment links)

Test cards

NumberBrand3-DSPaymentToken payment
4242424242424242Visayessuccesssuccess
5555555555554444Mastercardyessuccesssuccess
2200000000000004МИРyessuccesssuccess
4012888888881881VisayesInsufficientFunds (5051)
5105105105105100MastercardyesInsufficientFunds (5051)
2202202202202200МИРyesInsufficientFunds (5051)
4000000000003055Visanosuccesssuccess
5205000000003055Mastercardnosuccesssuccess
2202000000003055МИРnosuccesssuccess
4111111111111111VisanosuccessInsufficientFunds (5051)
5200828282828210MastercardnosuccessInsufficientFunds (5051)
2200000022222222МИРnosuccessInsufficientFunds (5051)
4000056655665556VisanoInsufficientFunds (5051)
5404000000000043MastercardnoInsufficientFunds (5051)
2203000000000043МИРnoInsufficientFunds (5051)

Cryptogram convention: base64(JSON.stringify({number, exp, name})). Hosted card form: /widget.

Webhook deliveries

Requests from the backend

Danger zone

wipes payments, logs and every runtime override — back to configured defaults