Payment intents that survive uncertainty.
Create once with idempotency, confirm deliberately, and consume signed events. A browser return is a hint—not fulfilment authority.
Open the API documentation →One payment story.
Four clear surfaces.
PerionPayments joins a provider-neutral payment API, hosted checkout, merchant dashboard, and operator control plane around the same retained evidence.
Hosted checkout, payment links, and embedded payment UI.
Accessible payer journeys keep provider-specific mechanics behind one stable customer contract and one safe “do not pay again” recovery state.
From provider evidence to bank-confirmed settlement.
Immutable journals, three-way reconciliation, independently approved settlement batches, and retained bank evidence keep financial truth inspectable.
Dashboards that expose current API truth.
Merchant and operations workspaces connect payments, callbacks, webhooks, approvals, incidents, ledger controls, reports, and governed exports without log archaeology.
Early access path
Value first. Controls intact.
- Under 10 minutesTarget first sandbox payment after access.
- Under 20 minutesTarget form time for a prepared KYB-1 application.
- 1–2 business daysPublished KYB-1 review commitment.
- Same day as approvalTarget first live payment once every external gate is actually closed.
Test the contract before live-money approval.
The sandbox is self-serve when public admission is open. Live rails are not represented as active until provider certification and the acceptance ledger support the claim.
Create your sandbox →