Testing Payments
How to test payments in games under development.
Testing payments in Pley Payments is easy and cost-free using sandbox mode and test cards in the Game Manager. This allows you to test purchases without real payment methods or filling out banking/tax forms until you're ready to publish.
Game Manager OnlyPayments can only be tested in the Game Manager by playing builds directly, or by using the run local feature in the Unity SDK.
For builds published on a release track, or released on a distribution channel (such as Discord), only real payments can be done.
Testing Payments
1) Launch a build (not release track) in the Pley Game Manager under builds.
2) Trigger a payment in-game.
3) Enter a sandbox test card (listed below). Look for Sandbox payment
in the checkout modal. Alternatively, use a testing payment card with Google Pay.
4) Complete the payment.



Sandbox Testing Cards
Card Type | Card number | Exp. date | CVV/CVC |
---|---|---|---|
Consumer Visa, Netherlands | 4111 1111 1111 1111 | 3/30 | 737 |
Consumer Mastercard, Great Britain | 5555 4444 3333 1111 | 3/30 | 737 |
ExpressPay Credit, China | 8171 9999 2766 0000 | 10/30 | 737 |
Discover, US | 6011 6011 6011 6611 | 3/30 | 737 |
Name & country can be anything; they donโt impact the test.
Testing on Production/ReleaseTesting payments on release tracks (e.g., Production) requires real payment methods, not test cards.
Powered by Adyen. See more test cards in the Adyen testing documentation.
Response
Sandbox purchases mark entitlements with "in_sandbox": true
in the JSON response for easy backend tracking. This can be used if you want different behavior for sandbox purchases.
{
"entitlement_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"product_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"in_sandbox": true
},
...
Keeping track of paymentsSandboxed transactions from in the Game Manager isn't tracked and they will not be part of the Sales reports.
Making test-payments will not affect any data or reporting.
Updated 6 days ago