Add prepaid value to a loyalty platform partnership
A member claims a reward in the loyalty app, but the prepaid partner issues it. Let the app decide who qualifies from their points or activity. Give both teams a shared reference so support can find the recharge or voucher when a member asks what happened.
| Decision | Starting owner |
|---|---|
| Points, eligibility and campaign rules | Loyalty platform |
| Product and fulfilment status | Prepaid partner |
| Member communication | Loyalty platform with agreed status wording |
| Match reward records and supplier charges | Finance on both sides |
| Correct unresolved claims | Named case owner with access to original references |
By Freepaid · Published
Draw the status flow before sharing access
Start with an eligible member action. Record the loyalty reference and proposed reward. Check that the member can receive the chosen product, then release the order through the agreed interface. Attach the fulfilment reference and latest status to the original loyalty record. Decide when points or budget move from reserved to spent. Document what happens if the status is delayed.
If a member taps Claim twice or reopens a support ticket, look up the approval already on file. Keep an order with an unknown result attached to its original reference. Agree who can cancel or replace an approval and what evidence they need first.
Compare commitments with supplier charges
Suppose a programme approves 180 R20 rewards in a trial, a face value of R3,600. At close, 170 are confirmed, six are rejected before fulfilment and four have unresolved outcomes. The confirmed face value is R3,400. Hold R80 of planned face value against the four open cases for investigation. The treatment of rejected orders and any charged fees depends on the supplier's actual records and the programme rules.
Give finance an export with the loyalty reference, fulfilment reference, approved value, supplier charge and date. Exclude full PINs and unnecessary recipient detail. Use a test case where a recorded approval has no matching supplier charge and another where the supplier shows a debit with an unknown outcome.
Test the member and support experience
Run one successful redemption, one rejected or held claim and one member request for a status update. Check that the member receives an accurate explanation and that support can find the same evidence. Decide what happens when a voucher was issued but redemption is still pending, if the partner can report that distinction.
Before opening the programme to more members, name the people who can change product values or funding limits. Agree how either team can suspend fulfilment and which records an incoming support lead will need to pick up open cases. AllNetAirtime API documentation · SIMcloud
Build a cross-reference test into acceptance
Give the loyalty support agent a member reference and the partner a supplier reference. Ask them to find the same reward and latest status independently. If either person has to search by amount or mobile number alone, fix the link between the records before you expand the pilot.