Skip to main content
Browser tokens are in early access and subject to change. To request Browser tokens access, contact hi@natural.com.
Some checkouts encrypt the card inside the browser instead of posting it to the processor in the clear. The proxy still swaps the real card in for the processors and merchants on Supported checkouts. Two things to get right.

1. Put the right hosts in allowedHosts

Everything in allowedHosts, including the card-field iframes, goes through the proxy. Allowing one live Adyen host covers Adyen’s regional hosts too, such as checkoutshopper-live-us.adyen.com.

2. Load the payment page after the claim

The proxy learns the checkout’s encryption key from the page’s own requests (for Adyen, from the card fields loading), so open or reload the payment page with the proxy configured before you enter the stand-in card. If the proxy never saw the page load, it refuses the card request rather than sending a card that would be declined.

If the proxy refuses

A refused request gets a 502 whose JSON body carries an error code and a hint saying what to change, for example:
Do what the hint says and submit again; don’t send the request directly. If the checkout still can’t be paid, report it with POST /merchant-reports so Natural can add support. Never include card numbers or codes in a report.