For Neobanks · Payments · Lending · Wealth

Money alerts that don’t vanish in email

Fraud flags buried in promo. ACH failures nobody opens. KYC deadlines that slip. Blasts delivers consent-based Screen Blasts into a dedicated inbox users opted into — Partner API from your ledger / risk stack, beside push and SMS (not instead of regulatory channels).

Get Free Sandbox Key → See Fraud Alert Example ↓

The attention gap in FinTech comms

Promo

transactional email still competes with marketing noise in the same mailbox

SMS $

OTP + alerts at scale get expensive — and users mute keywords

API

your risk / payments bus already knows the event — Blasts is another opt-in surface

Built for high-stakes money moments

🛡

Fraud & unusual activity

Card-not-present spikes, new device, velocity rules — HTML alert with amount, merchant, and “secure my account” CTA.

💸

Payment / ACH status

Sent, settled, returned, NSF — merge tags for amount, last-4, return code. Batch end-of-day digests if you prefer.

✅

KYC / document reminders

ID upload deadlines before account freeze — with read webhooks so support knows who saw the ask.

📉

Balance & limit alerts

Low balance, credit-limit near, autopay failed — consent-first, not a marketing drip.

📄

Statements & tax docs

“Your 1099 / monthly statement is ready” with portal link + optional PDF attachment.

🔗

Enroll at onboarding

Hosted blasts.dev/enroll/… after KYC pass, or server-side confirm when the user is already authenticated.

Honest framing: this is opt-in Screen Blast delivery — not a claim that email will never hit promo, not a substitute for bank-regulated notices where the law requires a specific channel, and not a HIPAA / PHI product. Strong fit for product-owned alerts where the user already expects account notifications and you control the enrollment moment.

Rich HTML fraud alert example

What a risk Screen Blast can look like — plus the Partner send call

Live Preview — Screen Blast Inbox

API Call — Single Send with HTML

# Fraud flag — enrolled account holder
curl -X POST "https://api.blasts.app/api/v1/partner/messages/send" \
  -H "Authorization: Bearer $API_KEY" \
  -H "X-Blasts-Timestamp: $(date +%s000)" \
  -H "X-Blasts-Signature: sha256=..." \
  -H "Content-Type: application/json" \
  -d '{
  "to_email": "jordan@example.com",
  "body_html": "<div style=\"font-family:sans-serif\">
    <div style=\"background:#7c3aed;color:#fff;padding:20px;text-align:center\">
      <h1>Unusual card activity</h1>
      <p>Card ending {{last4}}</p>
    </div>
    <div style=\"padding:20px\">
      <p>Hi {{name}}, we blocked
      <strong>{{amount}}</strong> at
      <strong>{{merchant}}</strong>.</p>
      <p>Case {{case_id}}</p>
      <a href=\"{{approve_url}}\">Yes, it was me</a>
      ·
      <a href=\"{{freeze_url}}\">Freeze card</a>
    </div>
  </div>",
  "body_plain": "SECURITY: {{name}}, blocked {{amount}} at {{merchant}} on card {{last4}}. Case {{case_id}}. Approve: {{approve_url}} Freeze: {{freeze_url}}",
  "metadata": {
    "case_id": "FRD-20991",
    "event": "fraud_flag"
  }
}'

Why Blasts fits beside push & SMS

	Email	Push / SMS	Blasts
Seen when it matters	✗ Promo / clutter	✓ If permissions on	✓ Opt-in Screen Blast inbox
Rich HTML + docs	✓	✗ Short form	✓ HTML + PDFs
Cost at volume	Low visibility	✗ SMS fees / mute risk	✓ Prepaid credits
Read proof	✗ Soft	✗ Limited	✓ Webhooks
Consent model	Often bundled	OS / TCPA rules	✓ Explicit enroll
Ledger / risk hook-in	✓ ESP	✓ FCM / CPaaS	✓ Partner API + HMAC

Wire it in under a week

1. Sandbox key

Ask for pk_test_* (0 credit debit, 100 sends/UTC-day). Contact AL@SavingsSites.com.

2. Enroll users

Hosted enroll after onboarding, or server-side confirm when they’re logged into your app.

3. Hook risk / payments

On fraud / ACH / KYC events, POST send or batch to https://api.blasts.app/api/v1/partner/….

4. Webhooks

Listen for delivered / read. Keep regulated statutory notices on your existing compliant channels.

More FinTech examples

ACH returned — single send

# NSF / return code to enrolled user
curl -X POST "https://api.blasts.app/api/v1/partner/messages/send" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "to_email": "jordan@example.com",
  "body_html": "<div style=\"font-family:sans-serif;padding:20px\"><h2>ACH payment returned</h2><p>Payment of <strong>{{amount}}</strong> was returned (code {{return_code}}). Update funding source to avoid late fees.</p></div>",
  "body_plain": "ACH returned: {{amount}}, code {{return_code}}. Update funding in the app.",
  "metadata": { "event": "ach_return", "return_code": "R01" }
}'

KYC reminder — batch

# Document deadline for accounts pending verification
curl -X POST "https://api.blasts.app/api/v1/partner/messages/batch" \
  -d '{
  "batch_name": "kyc_deadline_0725",
  "body_html": "<div style=\"font-family:sans-serif;padding:20px\"><h2>Action needed: verify your identity</h2><p>Hi {{name}}, upload your ID by <strong>{{deadline}}</strong> to keep full account access.</p></div>",
  "body_plain": "KYC: {{name}}, upload ID by {{deadline}} to keep full access.",
  "recipients": [
    { "to_email": "user1@example.com", "merge": { "name": "Jordan", "deadline": "Jul 25" } }
  ]
}'

Add an inbox channel your risk stack already owns

Free sandbox key · Partner API · same contracts as production.

Request Sandbox Key → API Reference More Code Examples