Cashback offers (automatic)
A Cashback Offer needs no action from the Consumer. Once they are enrolled in Perks, every eligible transaction the bank shares with Paylead is matched against the Consumer’s active Offers, and a match creates a Cashback Reward automatically.The Consumer is enrolled in Perks
Onboarding and consent put the Consumer into the Perks service. From that point their transactions are eligible for matching.
The bank shares the transaction
The bank pushes the transaction to Paylead through the Share transactions flow. This is a platform-level task, independent of any single Offer.
Paylead matches it against active Offers
Paylead checks the transaction against the Consumer’s active Offers (Brand, amount, channel, validity, targeting).
There is nothing to render for the act of earning itself: the Consumer does not tap or confirm anything. Your job is to surface the resulting Reward. See Reward lifecycle for the status tracks and the list and detail endpoints.
Voucher offers (bought up front)
A Voucher Offer lets the Consumer buy a prepaid value redeemable at a participating Brand. Unlike a Cashback Offer, the Consumer actively places an order and pays for it. The whole flow runs through the Paylead API: Voucher order payment no longer depends on a WebApp.The purchase flow
Browse Voucher Offers
Voucher Offers are the
VOUCHER entries in the catalog. Surface them like any other Offer (see The Offer catalog).Create a Voucher Order
Place an order on the chosen Offer with
POST /offers/{offer_id}/vouchers/orders. The body carries one or more amount_selections, each an amount and a quantity. The order starts in CREATED.Pay the order
Two payment models are available. Pick the one that matches your integration.
- Paylead-hosted payment
- Delegated payment
Paylead processes the payment page.
- Call
POST /vouchers/orders/{order_id}/payments/webviewto get aredirect_url. - Redirect the Consumer to that payment webview.
- When the Consumer returns, call
POST /vouchers/orders/{order_id}/payments/confirm.
The order completes
Once payment is confirmed, the order moves to
READY and the Vouchers are issued. A failed or abandoned payment leaves the order in PAYMENT_FAILED or CANCELLED.Code examples coming soon. The Paylead API (v2) is still under construction. Request and response examples for this section will be published once the contract is finalized. In the meantime, contact your Paylead account manager for early-access details.
Order states
| Status | What it means |
|---|---|
CREATED | Order placed, payment not yet completed. |
CONFIRMED | Payment confirmed, Vouchers being issued. |
READY | Vouchers issued and ready to use. |
PAYMENT_FAILED | Payment did not go through. No Voucher is issued. |
CANCELLED | Order cancelled before completion. |
What a Voucher carries
| Field | Description |
|---|---|
id | Unique identifier of the Voucher. |
order_id | The order the Voucher was issued from. |
status | The order status the Voucher reflects. |
brand | The Brand the Voucher is redeemable at (identity, logo, color). |
amount | Face value of the Voucher. |
valid_until | Expiry date. |
pin_code_1, pin_code_2 | PIN codes, when the Brand uses them. |
card_number | Voucher or gift card number. |
card_url | Link to the Brand’s redemption page, when provided. |
pdf_id | Identifier of the downloadable Voucher file. |
archived_at, refunded_at | When the Voucher was archived or refunded, if applicable. |
What’s next
Reward lifecycle
Track and display the Rewards a Cashback Offer generates.
Pool & payout
How a validated Reward reaches the Consumer’s pool and gets paid out.
Webhooks reference
React to Reward and Voucher events in real time.