Quick answer
A rewards program tracks eligible spending by connecting a verified customer with qualifying transactions and applying its published earning rules. The amount on a receipt and the amount that earns rewards can differ. Boomerangme's API can support card operations, while its webhooks notify other systems about account events. Your integration still needs a deliberate policy for exclusions, duplicates and refunds.
Define eligible spending before connecting software
Write the rule in a way both staff and customers can understand. Decide whether taxes, delivery fees, gift-card purchases, tips, discounted items and redeemed benefits qualify. Choose when a purchase becomes final: at payment, fulfillment or completed service. Those are program decisions; a connector should implement them rather than invent them.
Consider an illustrative purchase with $40 in eligible products and $5 in excluded charges. Under a one-point-per-eligible-dollar rule, the earning base is $40, not the $45 receipt total. If a qualifying $10 product is later returned, the retained eligible spend becomes $30. The exact reversal depends on your published policy and available operations; the example explains the calculation, not a preset Boomerangme behavior.
Understand API calls and webhook events
The official API overview directs developers to API v2 and distinguishes card-specific operations for amounts, points, stamps, visits and spend. Choose the operation for the card mechanics you actually use. A successful technical call does not prove the original purchase was eligible.
The webhook documentation describes notifications sent to a receiving system when selected events happen. Examples include card issuance, scans and balance changes. These outgoing signals can help monitoring and synchronization. A card scan alone is not evidence of paid spending, and a balance event is not a complete itemized receipt.
Choose the source of truth
Usually the till, commerce platform or booking system contains the purchase and refund record. Identify the system responsible for deciding whether an order is complete. Record the customer mapping and the qualifying amount before updating the loyalty card. If a staff member can also award progress manually, define when that is permitted so the same sale is not credited twice.
Use a reconciliation record with an order reference, customer reference, expected loyalty change and confirmed result. Keep it in a secured system with appropriate access. Do not embed secret API credentials in a public webpage or collect unnecessary customer information just because a connector can transmit it.
Plan for repeated delivery and corrections
Any integration can experience timeouts or uncertain results. Before retrying, determine whether the first operation succeeded. Design duplicate protection around the original purchase reference in your integration; do not assume a specific platform endpoint provides the safeguard unless its current documentation confirms it.
Refund handling needs its own test. Decide how a partial return affects earned progress and what happens if the reward has already been used. Escalate cases that cannot safely be corrected automatically. A written exception procedure is preferable to silently deleting a customer's card or changing unrelated historical purchases.
Test a small set of realistic purchases
Run an eligible purchase, an entirely excluded purchase, a mixed basket, a partial refund and a duplicate-delivery attempt. Include a transaction where the customer identifier is missing or incorrect. For each case, write the expected result first and compare it with the actual balance and your source transaction record.
Also simulate the receiver being unavailable. Check how the integration owner notices the failure and reconciles it. The objective is a recoverable workflow, not a diagram with arrows that always assume success. If a third-party connector is involved, inspect its actual transmitted fields and permissions before accepting it as equivalent to a custom integration.
Read dashboard values carefully
The API notes that reward-cost reporting can require an explicitly supplied value; it does not automatically retrieve the predefined reward price for the documented redemption method. Keep purchase revenue and benefit-delivery cost distinct in your own review. Ask the implementer which values populate each report before interpreting lifetime value as cash collected.
Use a weekly sample reconciliation even after launch. A program can look active while missed transactions or incorrect eligibility weaken customer trust. Our cost checklist and ROI guide help connect technical accuracy with a commercial decision.
Can a webhook calculate eligible spending for me?
A webhook transmits selected event data. Eligibility comes from your program rules and the underlying purchase record. Verify that your workflow receives the fields needed to calculate the right amount.
Does a scanned card prove a purchase happened?
No. A scan can identify or open a card without proving a completed eligible transaction. Award progress only after the required purchase or service condition is satisfied.
Where should an integration begin?
Start with your card mechanics and five test transactions, then check the current developer documentation. Explore Boomerang Me to confirm the integration route for your systems before investing in a full rollout.
Sources & further reading
- Boomerangme API documentationAPI v2, card-operation distinctions and explicit reward-cost value; no endpoint examples invented.
- Boomerangme webhooksOutgoing event purpose and card issuance, scan and balance examples; reliability checklist is original guidance.
Sources reviewed .
Numerical examples are illustrative unless a cited source states otherwise.
