For financial institutions

Keep customers engaged with rewards you don't fund

Embed Saldo's white-label widget, post transactions to one webhook, and deliver merchant-funded rewards your customers redeem in your app — whether they pay by card, PIX or wallet. No PII leaves your perimeter — only tokens cross the wire.

Request a demoRead the API docs

Integration

Three calls, no PII

The whole integration is widget + webhook + callback. Your customer data stays inside your perimeter.

Embed the widget

Drop our iframe or call the headless API. White-label by default — your colors, your branding, no Saldo references visible to cardholders.

Post transactions

Send transaction events to /api/v1/transactions as they happen. HMAC-signed, tokenized, idempotent. Match latency in seconds.

Credit the cardholder

Receive a redemption callback. Apply the cashback in your own systems on your own ledger. We never touch the customer balance.

Why institutions pick Saldo

Designed around your compliance posture

PII never crosses the boundary

We operate on the cardholder_token + card_token your institution generates. No names, emails, card numbers, or any other PII.

Curated offer catalog

Browse offers from real merchants in real categories. Approve what fits your program — reject anything that doesn't.

Tokenized end-to-end

HMAC-signed webhooks, hashed API keys, configurable rotation. Built around the assumption that we can be audited at any moment.

Configurable per program

Sort order, max offers displayed, eligibility windows, MCC restrictions — every knob is in your dashboard, not a support ticket.

Trust & security

Built for bank security from day one

The architecture keeps you outside PII and PCI scope — and gives your security team the controls they expect.

Tokenized architecture

We store only the cardholder_token + card_token you generate — never names, emails, PANs, or government IDs.

Minimal PCI & PII scope

Because Saldo never touches real card numbers, your PCI scope stays minimal and Saldo isn't a PII processor under GDPR, CCPA or LFPDPPP.

HMAC-signed webhooks

Every transaction event and API call is verified with HMAC signatures and timing-safe comparison.

Hashed, rotatable API keys

Per-institution keys are hashed at rest and scoped to your data — a key can never read another institution's.

Strict tenant isolation

Every record is scoped by institution_id; one institution's cardholder data is never exposed to another.

Full audit logging

Administrative actions are recorded — who changed what, and when — for compliance and review.

Pricing

Tiered network access

Plus the per-redemption payout you keep on every settled offer.

Community Banks

Small banks and credit unions getting started

$500–$2,000per month
  • ✓Full offer catalog access
  • ✓Real-time webhook matching
  • ✓Standard widget themes
  • ✓Email support
Talk to sales
Most popular

Regional Banks

Mid-size programs ready for advanced features

$2,000–$8,000per month
  • ✓Everything in Community Banks
  • ✓Advanced analytics dashboard
  • ✓Custom widget branding
  • ✓Priority support + Slack channel
Talk to sales

Enterprise Programs

Large institutions with bespoke needs

Customnegotiated terms
  • ✓Everything in Regional Banks
  • ✓Dedicated account team
  • ✓Custom take-rate negotiation
  • ✓SLA + uptime guarantees
Talk to sales

FAQ

Institution FAQ

How do financial institutions integrate with Saldo.tech?

+

Integration involves three components: (1) Embed the Saldo.tech offer widget in your banking app or online portal — it's white-label and fully customizable. (2) Post transaction events to our webhook API (POST /api/v1/transactions) for real-time matching. (3) Receive callbacks when offers are redeemed so you can credit cardholder accounts. The entire integration uses tokenized identifiers — no PII crosses the boundary.

What cardholder data does Saldo.tech require?

+

Saldo.tech requires only two tokenized identifiers that your institution generates: a cardholder_token (opaque identifier for the customer) and a card_token (tokenized PAN). We never receive or store names, emails, addresses, card numbers, or any personally identifiable information. The mapping between tokens and real identity stays in your systems.

How does the economic model work for institutions?

+

The merchant funds the reward. When a merchant funds a $15 reward, Saldo.tech retains its platform fee (10-15%) and passes the net (e.g., $13.20 on a 12% fee) to your institution, which you credit to the cardholder as cashback — so the reward itself costs you nothing. Your return is cardholder engagement and retention, not redemption revenue. Depending on tier, institutions pay a monthly network access fee for connecting to the network.

How long does implementation take?

+

Most institutions integrate in a few weeks. There are three pieces: embed the white-label widget in your app, post transaction events to one webhook, and handle the redemption callback to credit cardholders. All of it uses tokenized identifiers, so it stays outside your PII and PCI boundaries.

Do we control which offers our cardholders see?

+

Yes. You approve every offer before it goes live, set the rules it must satisfy (allowed categories, reward limits, durations), and can auto-approve trusted merchants or block specific ones. Nothing reaches your cardholders without your sign-off.

What are the institution pricing tiers?

+

Saldo.tech offers three tiers: Community Banks ($500-$2,000/month) for smaller institutions getting started, Regional Banks ($2,000-$8,000/month) for mid-size programs with advanced features, and Enterprise Programs (custom pricing) for large institutions with negotiated terms. All tiers include access to the full offer catalog and real-time matching.

Can we customize the cardholder experience?

+

Yes. The Saldo.tech widget is fully white-label — you control colors, branding, and placement. Cardholders see offers branded with your institution's identity, not Saldo's. You can also use the headless API to build a completely custom experience.

Ready to plug in?

We can have you live with a sandbox key and a working widget embed in under a week. Talk to our team.

Request a demoSign in to portal