Visual rule builder
No-code interface. Pick a trigger from a dropdown, add point-and-click conditions with AND/OR logic, and chain actions in a visual canvas.
The rules engine
Build it once. Run it forever.
A visual rules engine for software platforms — conditional logic, boarding automation, payout webhooks, and triggered notifications across every event in your payment stack.
Rule editor · High-risk routing
ActiveWhen·
New application is submitted
Trigger: application.created
If·
risk_score≥75- And
mccin5812, 5813, 7995
Then·
- Assign to Senior Underwriting
- Notify
#risk-escalationson Slack - Hold application until manual review
Recently fired · today
High-risk → Senior underwriter
12×2m ago
Settlement posted → payout webhook
87×4m ago
KYC document expiring · 30 days
6×11m ago
Approval → Documenso e-sign request
23×14m ago
1,284 rule fires today
47 active rules
<80ms avg eval time
Why automate
More merchants should not mean more manual work.
Growth creates operational tax — boarding handoffs, payout notifications, risk escalations, and KYC follow-ups that pile up as your platform scales. Pulse's rules engine lets your platform define workflows once and run them on every event — from merchant onboarding to risk monitoring without a single repetitive click.
What's inside
A complete rule-driven backbone.
Conditional branching
If/then logic for sophisticated workflows: branch by risk score, MCC, processor, or boarding status — fire different action sequences per merchant type in one rule.
Boarding automation
Trigger processor submissions, e-sign requests, and activation webhooks the moment an application clears underwriting — zero manual handoff.
Payout event hooks
Fire webhooks into your own product on every settlement, hold, or reversal. Keep your platform state in sync with Pulse without polling.
Triggered actions
Send notifications, update statuses, fire webhooks, or call external APIs. Eliminate the repetitive operations work that slows payment teams down.
Smart alerts
Alert your team on velocity breaches, pending KYC, failed settlements, or expiring documents — all rule-driven, delivered to Slack or email.
In the wild
Eight rules platforms run on day one.
Board to Fiserv the moment underwriting approves
Send high-risk apps to senior underwriters
Fire payout webhook on every settled batch
Email merchant when KYC document is expiring
Alert Slack on velocity breach above threshold
Notify on daily volume spikes
Hold boarding when risk score exceeds 75
Fire webhook on every merchant status change
How it works
Trigger, condition, action — in five steps.
- Step 1
Trigger
Application submitted, merchant boarded, settlement posted, document uploaded — pick any payment lifecycle event.
- Step 2
Conditions
Stack AND/OR conditions on any field — MCC, risk score, processor, payout amount, boarding status.
- Step 3
Actions
Notify, hold, board, fire a webhook into your product, or call an external API. Mix-and-match in any order.
- Step 4
Test
Preview against historical records. Validate before going live — no surprises in your payment production environment.
- Step 5
Monitor
Activity log shows every fire and outcome. Iterate based on what actually happens across your merchant base.
No-code, no developer needed.
Triggers from a dropdown, conditions in plain English, actions chosen from a built-in library. Versioning lets you roll back. Plain-language summaries let anyone audit the rule.
Cross-platform by default.
One rule can span onboarding, underwriting, risk monitoring, and your own product via webhooks. When a high-risk application fires, simultaneously notify underwriting, hold boarding, and push an event to your platform — without juggling three tools.
Outcomes
Less manual work. More throughput. Same team.
Eliminate manual work
Boarding, notifications, and webhooks run themselves. Your team focuses on building product, not shuffling payment data.
Consistent operations
Every merchant follows the same path every time — no more tribal-knowledge payment ops or missed handoffs.
Real-time platform sync
Webhook actions keep your product state in sync with every settlement, hold, and status change without polling.
Scale without hiring
10× the merchant volume on the same ops team. Automation handles the operational tax that comes with payments growth.
Who it's for
Built for platforms where payments operations can't fall behind growth.
- Software platforms embedding payments who need boarding and payout events reflected in their own product instantly
- Vertical SaaS teams that want risk and compliance rules to run automatically — not manually reviewed each cycle
- Operations teams handling repetitive status updates, notifications, and processor handoffs at scale
- Platforms managing multiple processors that need consistent routing logic without duplicating ops effort
- Growing ISVs that need 10× merchant volume capacity without proportional headcount growth
Related
Where this connects.
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