Integration

Zembula + Amazon Pay

Amazon Pay keeps the checkout details of a one-time Charge Permission readable for 30 days, and Zembula can show them in your email. Zembula can read each record by its ID through the Amazon Pay API.

It's our business to grow yours

Book a demo

What Zembula can read from Amazon Pay

Amazon Pay lets people pay at checkout with their Amazon account and stored payment details. Zembula can read three kinds of data from Amazon Pay and render them in an email at the moment a person opens it. A Checkout Session is one engagement at checkout, and Zembula can find it by its checkout session ID. A Charge Permission records consent to charge, either once or on a recurring basis.

It holds checkout details such as the name, the email address and the shipping address, and Zembula can find it by its charge permission ID. A Charge is one payment transaction, authorized and captured, and Zembula can find it by its charge ID. Each request to Amazon Pay is signed with a key pair. Your team creates and uploads that key pair in Seller Central.

Amazon Pay also supports Instant Payment Notifications, so Zembula can use webhooks as a second route. A receipt-style follow-up, a thank-you to a recurring payer and a retry prompt can all draw on these records.

DataDetailLooked up by
Checkout SessionOne engagement at checkout, with the checkout details.checkout session id
Charge PermissionConsent to charge, once or recurring, with checkout details.charge permission id
ChargeOne payment transaction, authorized and captured.charge id

How the data arrives

  • API: Each request is signed with your Amazon Pay key pair, and Zembula can read the record by its ID.
  • Webhook: Amazon Pay supports Instant Payment Notifications, and Zembula can receive them as webhooks.

What you need

  • An API key or a data export from Amazon Pay. Zembula sets up the connection for you.
  • A key pair that your team creates and uploads in Seller Central, in Integration Central.
  • A record ID, such as a charge ID, sent as a merge tag in the image URL.

Limits to plan for

LimitWhat it means
Checkout details of a one-time Charge Permission can be read for 30 days after creation.Plan emails that show these details inside that window.

Ideas for email

  • Send a receipt-style follow-up when a Charge completes, using the Charge record.
  • Thank a repeat payer when a recurring Charge Permission is active.
  • Prompt a retry when a Charge Permission cannot be charged.

Last checked: 19 November 2026.

Performance marketing dials, inside email. For the first time.

See how we do it by booking a demo.