Plan
The site and plan are decoded from the link.
The checkout link carries the session. The extension decodes it to read the site host, the plan name and the total, so a posted card arrives with the checkout it came from attached.
Runs on any checkout page you already open. Reversible in one deploy.
How it works
Read the link
The checkout URL carries the session reference that names the payment page.
Fetch the init payload
The payment page's init payload carries the display name, the line item name and the total summary.
Decode the plan
The line item name and total become the plan and amount attached to the card.
Attach it to the POST
Site, plan and amount travel with the card fields to the relay endpoint.
Decoded from the checkout's own init payload, not from a guess.
Decoded, not guessed
The site and plan come from the checkout's own payload. A posted card therefore names the checkout it settled, rather than a label the extension invented.
- Site host read
- Line item name read
- Total summary read
Works for any checkout
The same decode applies to a hosted page, a payment link or a custom checkout, as long as the page exposes its init payload.
- Hosted checkout
- Payment links
- Custom checkouts
Questions about this one.
More on the full FAQ, or write to [email protected].
01Where does the plan name come from?
From the checkout's init payload: the first line item's name is the plan, and the total summary is the amount.
02What if the checkout hides its payload?
Then the site is read from the host and the plan falls back to the line item visible in the page.
03Does it change the price?
No. The total is read as presented, and nothing about the checkout's amount is rewritten.
Checkout context
Send the card with the site and plan it settled.
Decode the checkout link and the posted card arrives with the checkout it came from attached.
- Site decoded
- Plan decoded
- Total decoded