Two REST endpoints that plug real-time card reward rates and portfolio gap analysis directly into your banking platform — server-to-server, sub-100ms, no shopper PII required.
Both endpoints are authenticated with your sp_bank_… key. Server-to-server only — no browser-side keys required.
Pass an amount, MCC, and merchant name. Get back the top 3 cards from your catalog ranked by reward rate for that purchase — with estimated reward in cents.
{
"amount": 87.45,
"mcc": "5411",
"merchant_name": "Whole Foods"
}
Pass your card IDs and a spending profile. Get per-category winners within your lineup and a ranked list of uncaptured reward gaps — where your customers are leaving money on the table.
{
"card_ids": ["amex_gold", ...],
"spending_profile": [
{ "category": "groceries",
"monthly_spend_usd": 800 }
]
}
The API works entirely on catalog data and MCC codes. You never send a cardholder name, account number, or transaction ID to SuperPay.
Recommendations are served from a cached catalog with no AI call in the critical path — safe to call inline at checkout or in your mobile banking app.
The /v1/bank/portfolio endpoint tells you which spend categories your lineup doesn't cover well — and which market-leading cards are capturing that spend instead.
Bank partner keys (sp_bank_…) are separate from merchant keys. Different rate limits, separate usage logs, and scoped admin controls in the portal.
Register the exact domains your banking app runs on. Browser-side requests from any other origin are rejected — no API key exposure risk.
Apply for recommend-only access or both endpoints. Access level is baked into your key and enforced server-side — nothing to configure in your integration.
Start free with the sandbox key, upgrade when you go live. No per-call fees — flat monthly rate.
Integrate and test with no commitment. Sandbox key included with every approved application.
Up to 50,000 calls/month — both endpoints included. Full production access.
sp_bank_… keyUnlimited calls, dedicated SLA, priority support, and custom contract terms for large institutions.
Use the sandbox key below to call /v1/bank/recommend directly from your terminal — no signup required.
Copy this key and paste it into the curl command below. The sandbox key hits the same recommendation engine as live keys.
curl -X POST https://superpayrewards.com/v1/bank/recommend \
-H "Authorization: Bearer sp_bank_18efc2c6_de60bb1bb2d3521152d28c37e97e84a969b6eb0530970b56" \
-H "Content-Type: application/json" \
-d '{"amount": 87.45, "mcc": "5411", "merchant_name": "Whole Foods Market"}'
For /v1/bank/portfolio, email hello@superpayrewards.com for a portfolio-enabled sandbox key.
Card name, issuer, network, reward rate, reward type (cashback vs points), estimated reward in cents, and a human-readable reason string. No shopper-specific or account-level data — everything comes from the public card catalog.
The Bank Partner API sends no shopper PII to SuperPay and returns no PII. You send an amount, MCC, and an optional merchant name. SuperPay returns catalog data. Review the Bank Partner Terms and Privacy Policy with your legal team.
Same recommendation engine, different key namespace and purpose. Merchant keys (sp_live_…) are for checkout widgets. Bank partner keys (sp_bank_…) are for FI-to-server calls and include the portfolio analysis endpoint that isn't exposed to merchants.
300 requests per minute per key. Headers X-RateLimit-Limit, X-RateLimit-Remaining, and Retry-After are set on every response. Need more? Contact us to discuss a custom arrangement.
Typically within 1 business day. We review the registered origins, use case, and access level request before issuing a live sp_bank_… key.
We'll verify your email and review your application — you'll receive your sp_bank_… key once approved, typically within 1 business day.
By submitting you agree to the Bank Partner Terms and Privacy Policy.