Rewards & incentives
The recipient may be redeeming an earned benefit rather than making a purchase. Explain eligibility, available choice and the distinction between receiving a voucher and successfully redeeming it.
Gift card API
Make the reward useful at the moment of redemption.
Plan gift card or voucher distribution for a rewards program, loyalty product or B2B storefront. APISMA reviews private API access around your business use and intended scope.
Before the recipient chooses
A familiar logo is not enough information.
Two vouchers from the same brand can still differ in how and where they can be used. Build the selection around the restrictions that affect the recipient.
| Decision | Explain to the recipient | Validate for the intended scope |
|---|---|---|
| Where can it be used? | The relevant brand or issuer and the redemption channel. | Whether use is online, in-store or limited to an approved channel; do not infer this from branding. |
| Will it fit the recipient? | The applicable market, currency and value. | Region restrictions, available denominations and any account requirements that affect redemption. |
| When and how is it redeemed? | Where to find instructions and any applicable expiry conditions. | The actual redemption steps, validity rules and whether restrictions need prominent disclosure. |
| What if it does not work? | A clear support route and the safe information to provide. | Who investigates redemption issues and how sensitive code details are protected. |
Distribution models
The same voucher can serve different business jobs.
The qualification review needs your distribution model, not only a requested brand list. It affects who chooses the item and who is responsible for the recipient experience.
Loyalty programs
Points and voucher value are separate concepts. Show the exchange clearly in your product and decide how the recipient can recover the redemption instructions later.
Marketplace or B2B resale
The buyer may not be the final recipient. Define the intended audience, approved distribution relationship and support responsibilities before planning how codes appear in the storefront.
Product design decisions
Protect the code. Explain the next step.
A redeemable code is sensitive value. Plan visibility and support carefully without treating an interface choice as a promise about APISMA delivery behavior.
- Before selection
Put relevant restrictions next to the choice. Do not hide a region limitation behind a generic FAQ or assume the user has read issuer terms elsewhere.
- After receipt
Provide the correct redemption instructions and a way to find them again. Distinguish the value received from any subsequent action on the issuer’s service.
- During support
Avoid exposing full codes in public messages or routine logs. Agree a controlled investigation route and explain what the customer should not share.
Illustrative planning example
A voucher chosen for a different market
The product should help the recipient check the market before selection. If a problem is reported later, support needs the applicable restrictions and safe reference context, not a public screenshot containing the code.
Confirm the actual correction and refund policy in the commercial agreement; do not promise that every issued voucher can be exchanged.
Common questions
Questions about gift card integration.
Is a gift card API the same as a game top-up API?
No. This category concerns redeemable value. A direct game top-up concerns value applied to a player account. A gaming brand can appear in either context, so confirm the actual product type.
Can I browse brands and denominations here?
This public guide does not provide a live catalog or confirm supply. Include the brands or markets you want to evaluate in the private conversation and confirm the available scope before presenting it to customers.
What should a rewards team bring to the review?
Explain why the recipient receives a reward, who selects it, how the distribution model works and the expected monthly range. Identify the person responsible for recipient support.
Does an access request return a voucher?
No. The form begins manual business qualification. It does not create a transaction, return a code or issue credentials.
Describe your voucher distribution model.
Select gift cards and vouchers in the form, with your company, work contact and expected monthly volume. Prepare the recipient journey and distribution responsibilities for the follow-up conversation.
Submitting a request does not create an account or guarantee approval.