Swish payment service provider A PSP layer for invoices, subscriptions and card operations
A modern PSP for billing, not another billing module inside your app

Swish is a payment service provider for your SaaS billing layer

Separate billing from product code. Swish manages invoices, subscriptions, retries, card tokenization, and signed webhook events while your app stays focused on users and pricing.

Sign in See how it works
1
Integrate once
Your app sends billing intents and receives signed billing events.
2
Portal included
Customers manage invoices, subscriptions, and payment methods.
3
PSP-grade flow
Tokenization, retries, and webhooks handled in the billing service.

Swish PSP

Billing gateway and customer portal

Live

Your app

Creates billing intents

Products, users, and pricing stay in your platform.

Signed events

Swish PSP

Normalizes billing

Invoices, retries, subscriptions, tokens, and portal UX.

Dedicated billing layer

Payment provider

Captures and authenticates

Tokenization and authorization are handled by the gateway.

Why teams use Swish

  • Reduce billing surface area in your application code
  • Reuse a single PSP layer across multiple products and domains
  • Portal UX that matches your brand, without rebuilding billing pages

How it works

Treat billing as infrastructure. Your platform sends billing requests, Swish executes billing operations, and then sends signed events back to your app.

01
Create intent

Your platform calls the Swish API with customer and pricing details.

02
Tokenize and charge

Swish orchestrates tokenization, authentication, payment attempts, and retries.

03
Emit billing events

Swish signs webhook payloads and sends events back to your platform for product updates.

Features

A PSP-style billing layer you can operate independently from your product.

01

Customer portal

Invoices, subscriptions, and payment methods with branding per platform.

02

Signed webhooks

Deliver billing events back to your product with verifiable signatures.

03

Tokens, not raw cards

Card data stays at the gateway. Swish stores tokens, last digits, and expiry only.

04

Retries and dunning

Manage failed payments and reminders without implementing it in every product.

05

Multi-platform ready

Separate branding, credentials, and domains per platform with strict tenancy.

06

Audit-friendly invoices

Persist PDFs only for final invoices. Generate drafts on-demand so status is always correct.

FAQ

Answers for teams adopting Swish as a PSP layer.

Your application links to the portal (or includes portal URLs in billing emails). Users sign in and see billing data tied to their assigned customers.
Yes. Each platform can have its own custom domain, branding, and PSP configuration. Swish enforces separation by platform.
No. Card details are captured and tokenized by the payment gateway. Swish stores only tokens and non-sensitive metadata (brand, last four, expiry).
Webhook payloads are signed server-side using a platform secret. Your app verifies the signature before trusting the event.

Go straight to the portal

If your account already has access, sign in to view invoices, manage subscriptions, and update payment methods.

Portal login

Need access? Ask your admin or support team to add you as a billing contact.