Integration

Zembula + Kard

Kard matches card purchases to offers and tells you when an earned reward is approved or settled, and Zembula can use those notices. Zembula can look up a cardholder by Kard user ID.

It's our business to grow yours

Book a demo

What Zembula can read from Kard

Kard is a card-linked offers and rewards platform. It enrolls cardholders, matches their card purchases to offers and serves live offers that a card program shows in its own app. Zembula can use three kinds of Kard data. The first is the enrolled cardholder, with rewards enrollment, postal codes and phone numbers.

Each cardholder holds up to 10 postal codes and up to 10 phone numbers. The second is the card transaction, with its amount, direction, status, currency, merchant category and merchant. The third is the live card-linked offer. Kard also sends a webhook notice when an earned reward is approved and another when it is settled.

Kard identifies a cardholder by user ID, and it can also use a SHA-256 hashed email. It identifies a transaction by transaction ID. Kard builds a reconciliation file once a day, at 08:30 UTC. 0 credentials from Kard, and a pre-production credentials call comes before launch.

Kard also needs the historical transactions of a cardholder sent first. A cardholder record shows whether that step is done.

DataDetailLooked up byHow fresh
Enrolled cardholderA person in the rewards program, with enrollment, postal codes and phone numbers.user ID, or hashed emailset at setup
Card transactionA card purchase that Kard matches to offers, with amount, status and merchant.transaction IDdaily
OfferA live card-linked offer that a card program shows in its own app.set at setupset at setup
Earned reward noticeA webhook notice when a reward is approved or settled.set at setupset at setup

How the data arrives

  • API: Your team gets OAuth 2.0 credentials from Kard. Zembula connects to Kard with them.
  • Webhook: Kard sends a notice when an earned reward is approved and another when it is settled.

What you need

  • OAuth 2.0 credentials from Kard, and a pre-production credentials call before launch.
  • An API key or a data export from Kard. Zembula sets up the connection for you.
  • The Kard user ID of each cardholder, sent as a merge tag in the image URL.

Limits to plan for

LimitWhat it means
Kard generates the reconciliation file once a day, at 08:30 UTC.Transaction data from that file updates once a day.

Ideas for email

  • Tell a cardholder about a matched reward, using the earned reward notice from Kard.
  • Show live Kard offers inside a rewards email.
  • Show a different image to a cardholder whose historical transactions are not yet sent.

Last checked: 19 November 2026.

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

See how we do it by booking a demo.