Introduction
What Starship Rewards is, who the API is for, and what scope of integration it supports
Introduction
Starship Rewards is a B2B rewards and disbursement platform. The API gives your backend two primary capabilities: buy digital vouchers (gift cards, mobile top-ups, prepaid credits) for your end-users, and send payouts (bank transfers, mobile money, digital wallets) as cash disbursements. Both are funded from a prepaid wallet you hold with Starship.
Who this API is for
| You are... | Typical use case |
|---|---|
| A loyalty platform | Redeem user points for gift cards on demand |
| An employee-rewards provider | Send spot bonuses as Amazon / Flipkart / Starbucks vouchers |
| A neobank or fintech | Cash-back rewards, refer-a-friend incentives, promotional giveaways |
| A disbursement platform | Gig-worker payouts, insurance claims, refund processing |
| A marketplace | Seller payouts in their local currency via Starship's global payout rail |
If your integration is "I have an event in my system and I want to hand a digital voucher or cash to an end-user", this API fits. If your integration is "I want to accept payments from end-users", you want a payment processor, not Starship.
What the API provides
Catalog access
Browse ~2,000+ products across 40+ currencies and 80+ countries. Products are gift-card brands (Amazon, Starbucks, Netflix, etc.), with denomination ranges and live inventory availability.
Pre-order quotes
The Charges API returns the exact amount you'll be billed — face value, FX converted to your wallet currency, minus your negotiated discount, plus any fees. Display this to end-users with confidence; it's what you'll be charged.
Order placement & fulfillment
Submit an order and receive voucher codes. Depending on inventory state, this is either synchronous (vouchers in the response) or asynchronous (vouchers via webhook + GET /orders/:id).
Wallet & ledger
Prepaid wallets in each currency you transact in. Every debit is ledgered; a GET /wallets/:id/transactions endpoint gives you the full settlement trail for reconciliation.
Payouts
Send money directly to bank accounts, mobile-money wallets, or digital wallets via a unified POST /payouts endpoint. Beneficiary management and cancellation are first-class operations.
Webhooks
Real-time order.* and payout.* events delivered to your HTTPS endpoint with HMAC-signed payloads and automatic retry on failure.
What the API explicitly does NOT do
Setting expectations early saves back-and-forth with support:
- No automatic vendor fallback. If an order can't be fulfilled from Starship's inventory cache, it parks in
PENDINGstatus. Starship does not call the vendor API on your behalf unless an admin approves the fallback. See Fulfillment Model. - No end-user identity. Starship doesn't authenticate or store your end-users. You tell us who ordered; we deliver a voucher; their identity stays on your side.
- No payment capture. Your wallet is prepaid. Starship does not capture card/UPI/ACH payments from end-users. Fund your wallet out-of-band.
- No real-time FX quoting. FX rates refresh daily from an internal
fx_ratestable. If you need tick-by-tick rates, layer your own provider above Starship. - No "self-serve" webhook testing for arbitrary events. Test deliveries are supported for webhooks you've configured; there's no public sandbox for event spoofing.
How integrations typically scale
Most integrations go live in under two weeks: read-only catalog first, then quotes, then a small flight of sandbox orders, then a canary rollout in prod with 1–5 % of real volume, then full switch-over. The Integration Journey page walks through each stage.
Next
→ Integration Journey — the visual roadmap