TestReturn guide

How to use ready-made return URLs to test redirects, payments, checkouts and OAuth callbacks.

What TestReturn is

TestReturn gives you four public pages to use as return URLs while you test. Each page shows which route was reached, the full URL, and every query parameter it received. There is nothing to set up and no account to create.

How to test a success URL

Set https://testreturn.link/success as the success, return or completion URL in your test integration. Finish the flow and the browser lands on a green success page that lists what the provider sent back, for example:

https://testreturn.link/success?payment_id=123456&status=paid

Copy success URL

How to test a failure URL

Set https://testreturn.link/failure as the failure or error URL. Use a test card or account your provider declines, then check the reason or error code on the page:

https://testreturn.link/failure?reason=declined&code=card_declined

Copy failure URL

How to test a cancellation URL

Set https://testreturn.link/cancel as the cancel URL. Start the flow, then press cancel or back on the provider's page:

https://testreturn.link/cancel?checkout_id=abc123

Copy cancel URL

How to inspect callback and query parameters

Use https://testreturn.link/callback when you only need to see what came back, for example as an OAuth redirect URI:

https://testreturn.link/callback?code=abc123&state=xyz789

Every parameter is shown as a name and a decoded value. Repeated names are listed once per value, in the order received. Each value has its own copy button.

Copy callback URL

Your provider must allow the URL first. Most OAuth providers make you register the exact redirect URI in their developer console.

Typical integration setup

Success URL:
https://testreturn.link/success

Failure URL:
https://testreturn.link/failure

Cancel URL:
https://testreturn.link/cancel

Privacy

• Query parameters are read and shown by JavaScript in your own browser. They are never sent to a TestReturn server or stored.
• Each visitor only sees the parameters in their own address bar.
• Values are shown as plain text. HTML or scripts in a parameter are never run.
• The pages load no third-party scripts and send no referrer when you follow a link away.

Do not send production secrets, passwords, long-lived access tokens, personal data, or sensitive customer information to public TestReturn URLs. TestReturn is for development and test data. Anything in a URL can end up in browser history and in the logs of the provider that redirected you.

Known limitations

• Only query-string parameters are listed. Values after # appear in the full URL but are not split into a table.
• Every page returns HTTP 200. Custom status codes, delays and webhooks are not supported yet.
• Server-side callbacks and webhooks (requests made by a server, not a browser) are not captured. TestReturn only sees what your browser opens.
• Nothing is kept. Reloading or closing the page is the only history.