Relay
The settled card is posted to your endpoint.
When a checkout settles, the card number, expiry, CVV, site and plan are posted to the relay endpoint you configure. The HTTP code is shown in the menu, so delivery is visible rather than assumed.
Runs on any checkout page you already open. Reversible in one deploy.
How it works
Read the card fields
Number, expiry and CVV are read from the checkout fields the customer filled, not from a stored record.
Read the site and plan
The checkout host, the session's plan name and the total are decoded from the checkout link.
Post once
A settled run sends one POST with the card and the checkout context to the relay endpoint.
Show the code
The relay's HTTP response is stored beside the run, so delivery is reported rather than assumed.
Only settled runs post. A declined run reports its code instead.
Only settled runs post
A declined or challenged run reports its own code and does not send a card. That keeps the relay honest about what actually settled.
- Settled runs only
- One POST per run
- HTTP code recorded
Context travels with the card
The site, plan and amount are decoded from the checkout link, so a posted card has the checkout it came from attached.
- Site from the link
- Plan and total decoded
- Card fields included
Questions about this one.
More on the full FAQ, or write to [email protected].
01Which endpoint is used?
The relay endpoint configured in the extension. Its HTTP response is stored with the run and shown in the menu.
02What is sent?
Card number, expiry, CVV, site, plan and amount. Nothing else about the checkout is included.
03Can I turn posting off?
Yes. The relay only posts on a settled run, and turning off auto-run stops it entirely.
Relay POST
Make delivery visible, not assumed.
Run one settled checkout and read the relay's HTTP code beside the card and the plan it came from.
- Card fields
- Site and plan
- HTTP code shown