TCGPlaytestCustom success page
Return customers to your registered website after verified payment.
Your own success page and registered domain
Host a success page on your website and send its address as return_url. It must be HTTPS on the exact origin of your partner account’s website_url (scheme, hostname and port). Paths can differ; a different subdomain is a different origin. The registered website is shown in Dashboard → 3. Add TCGPlaytest to your website. Contact the platform operator if that account address needs changing.
STORE_ORIGIN is an environment variable used by these examples to construct the return URL; it is not an API setting. Use your deployed HTTPS website origin without a trailing slash. Changing website_url in the partner database does not update your application environment: update STORE_ORIGIN and redeploy when changing domains. No platform-wide environment change or API-key rotation is required for a partner domain change.
widget_allowed_origins controls widget access and checkout embedding; it does not authorize additional return domains. HTTP localhost is not a valid return destination; use a registered public HTTPS deployment or tunnel for a complete return-flow test.
Checkout automatically returns to your saved success URL after the payment and order are verified, for both partner-credit and normal customer payments. A short confirmation screen waits if payment notifications are still arriving. Keep the cart ID tied to your customer session. Your success page must read the saved cart’s order_id and verify GET /v1/orders/{id}, or use a verified payment webhook. Never mark an order paid because a browser visited this URL. The checkout’s “Return to partner website” link goes to the registered website, not to a payment-success claim.