One embed, every processor
NMI, Fiserv, TSYS, First Data, Stripe, Maverick — Pulse builds and maintains every processor connection. You integrate with Pulse once and inherit them all, instantly.
Gateway
Embed once. Connect to every processor.
Your platform integrates with Pulse once. Pulse maintains direct connections to NMI, Fiserv, TSYS, First Data, Stripe, and Maverick — routing every transaction, streaming every event, and keeping your PCI scope small.
Gateway router · 5 processors
Routing liveNMI
0msHealthy
Fiserv
0msHealthy
TSYS
0msHealthy
Stripe
0msHealthy
Maverick
0msDegraded
Time
Merchant
Amount
Routed to
Webhook
14:02:18$124.50NMI
Acme Coffee Co.
MID 482910
41ms
14:02:11$1,842.00Fiserv
Harbor Marine Supply
MID 671203
55ms
14:01:55$312.75TSYS
Northwind Bakery
MID 593411
60ms
14:00:42$412.00NMI
Capitol Diner
MID 410552 · failover from Maverick
47ms
13:59:33$64.00Maverick
Bayside Auto Wash
MID 722890
Retrying
0 events routed today
0ms avg route
0.00% delivery
One integration, every rail
The gateway your platform never has to maintain.
Building to one processor is a project. Building to six is a team. Pulse gives you a single gateway that routes across every processor, streams events back in real time, and powers payment processing and integrations without a single processor contract on your side.
What's inside
Everything between your platform and the processors.
Live transaction stream
Every authorization, settlement, refund, and chargeback flows into your platform in real time as it happens. No polling, no next-day batch files — just a clean event stream your product can act on.
Webhook router
Route any processor event — to Slack, email, or your own endpoints — without writing custom handler code per processor. Filter by MID, amount, status, or any payload field.
Settlement reconciliation
Pulse automatically matches processor settlement files against transaction records. Discrepancies surface in a review queue with full diff context — no manual spreadsheet wrangling.
Retry & resilience
Failed webhook deliveries retry with exponential backoff, and routing fails over to a healthy processor automatically. Full logs surface every event, attempt, and response code.
PCI-aware tokenization
Card data is tokenized at the gateway boundary before it ever touches your platform. Pulse never stores PANs, which means your PCI scope stays minimal by design.
Capabilities
The full gateway toolkit, ready to embed.
Smart processor routing
Automatic failover
MID-level routing rules
Real-time auth stream
Webhook fan-out
Idempotent retries
Settlement matching
Refund + void passthrough
Delivery logs + replay
Latency monitoring
Tokenized PANs
Reduced PCI scope
How it works
One embed to a resilient, multi-processor gateway.
- Step 1
Integrate once
Connect your platform to the Pulse gateway via API or SDK. One integration inherits every processor Pulse supports.
- Step 2
Route intelligently
Pulse routes each transaction to the best-fit processor by merchant type, cost, and health — with automatic failover.
- Step 3
Stream events
Auths, captures, refunds, and chargebacks flow back as a clean real-time event stream and webhook deliveries.
- Step 4
Reconcile + monitor
Settlement files match to transactions automatically. Latency, delivery, and variance surface before anyone has to ask.
One API, every processor.
Pulse routes transactions across Fiserv, NMI, TSYS, First Data, Stripe, and Maverick behind a single API. Switch processors or add redundancy without rewriting your integration.
Resilient by design.
A degraded processor fails over automatically. Failed webhook deliveries retry with exponential backoff and full replay, so no event is ever silently lost.
Built for developers
One call in. A webhook back.
POST /v1/charges
$ curl
Outcomes
Less integration code. More resilience.
Pulse maintains the processor layer, not you
Processor APIs evolve, certifications lapse, and endpoints change. Pulse owns that maintenance burden — your platform inherits the updates without shipping a single line of integration code.
Real-time data your product can use
Surface live transaction status, velocity signals, and settlement data inside your own UI the moment events happen — not the next morning.
Minimal PCI scope by design
Because Pulse tokenizes at the boundary and never passes raw PANs to your application, your platform avoids the heaviest PCI-DSS compliance obligations from the start.
Add processors without adding projects
When your merchants need a new processor or your roadmap expands to a new market, you enable a connection in Pulse — not a multi-sprint integration project.
Who it's for
Built for platforms that don't want to be in the processor business.
- Vertical SaaS platforms that want one integration instead of a processor relationship per vendor
- ISV engineering teams that need a real-time event stream rather than next-day batch files
- Product teams routing processor events to Slack, email, or their own endpoints without per-processor code
- Finance and ops teams reconciling settlement across Fiserv, NMI, TSYS, and Maverick in one place
- Platforms scaling volume that need processor redundancy and failover without code changes
Related
The full PayFac-as-a-Service stack.
Now onboarding software partners
Turn your software into a payments business.
We sell it, board it, underwrite it, and run it. You add a revenue line to your platform without adding headcount.
Built for vertical SaaS platforms ready to monetize payments.
PCI DSS compliantSOC 2 Type II99.9% uptimeMulti-processor