Cashier Intent Sim

Demo Cashier
Merchants & Keys
Master Endpoints
Payment Methods
PAM Profiles
Orders
Request Log
API / Help

Demo Cashier

Everything you need is on this one page: pick where to test, enter your details, and click Open Cashier.

PAM server — a separate local service standing in for your real player-account system checking...

Merchants & Keys

This tab is only for the local simulator's own test merchants. To test against the real PayNetEasy sandbox or production with your real credentials, use the Demo Cashier tab instead — everything (consumer key, private key, Master Endpoint id) is entered there in one place.

Generate demo merchant (for testing against this local simulator)

Register your own merchant (public key only, for testing your code against this simulator)

Merchants

Master Endpoints

A Master Endpoint is what you call /intent on, e.g. /paynet/api/v4/intent/{id}. Each belongs to one merchant.

New Master Endpoint

Payment Methods (Auxiliary Endpoints)

These are what /intent returns, and what /sale and /payout are called on by their end-point-id.

New Method

PAM Profiles (mock player accounts)

Keyed by pam_user_id. Controls what the simulated PAM reports back during /intent and whether payments settle approved or declined.

New / update profile

Orders

Created by /sale and /payout. They settle automatically after 2-5s (simulating the async PAM reservation + acquirer flow), or you can force it now.

Request Log

API / Help

Endpoints this simulator implements

POST /paynet/api/v4/intent/{MASTERENDPOINTID}
POST /paynet/api/v4/sale/{end-point-id}      (deposit)
POST /paynet/api/v4/payout/{end-point-id}    (payout)
POST /paynet/api/v2/status                   (order_id)

All calls must be application/x-www-form-urlencoded, signed with OAuth 1.0a / RSA-SHA256 in the Authorization header, exactly like the real Payneteasy v4 API. Send Accept: application/vnd.pay+json to get JSON error bodies with proper HTTP status codes instead of the default form-encoded/200 error format.

How to point your own client at this simulator

  1. Register a merchant here with your code's public key (Merchants & Keys tab). Keep the matching private key in your code, exactly as you would for the real sandbox.
  2. Create a Master Endpoint and some Methods under that merchant.
  3. Point your client's base URL at instead of the real sandbox host.
  4. Create a PAM Profile for each test player scenario you need (balance, KYC, refusal reason, forced payment outcome).

Refusal / error codes this simulator reproduces

Top-level refusals: PLAYER_REFUSED_BY_PAM, PAM_UNAVAILABLE, PLAYER_CURRENCY_UNKNOWN,
                     NO_METHODS_CONFIGURED, NO_METHOD_FOR_PLAYER_COUNTRY,
                     NO_METHOD_IN_PLAYER_CURRENCY, NO_METHOD_FOR_OPERATION
Method refusals:     METHOD_UNDER_MAINTENANCE, AMOUNT_BELOW_MINIMUM, AMOUNT_ABOVE_MAXIMUM,
                     KYC_STATUS_NOT_ACCEPTED, PLAYER_CATEGORY_NOT_ACCEPTED
Error codes:         1 (bad/missing param), 11 (unknown endpoint id), 20 (PAM disabled),
                     102 (empty pam_user_id/session), 2005 (PAM settings incomplete)