successful production payments recorded
Add equestrian workflows without rebuilding payment infrastructure for each one.
Perno Equestrian creates contextual payment requests while Perno Orchestration selects compatible merchant accounts, hosts checkout and receives status updates.
One consistent payment layer beneath every center journey.
Built on payment infrastructure already working in production.
A conservative snapshot of Perno's production footprint—not a forecast or an invented customer claim.
payment providers represented in live transactions
specialist industry payment products
processed payment value in the leading production currency
Live database snapshot for 30 October 2026. Values are rounded down and sandbox transactions are excluded. Different currencies are not combined.
Payment-provider plumbing should not shape the rider experience.
Each payment provider has different APIs and statuses.
Return URLs and webhooks are easy to misconfigure.
New payment surfaces repeat the same integration work.
A shared foundation with vertical context on top.
Orchestrated routing
Use compatible merchant accounts and payment methods.
Hosted checkout
Keep provider logic away from the center dashboard.
Status updates
Receive provider results into Perno records.
Return journeys
Use consistent success and cancellation destinations.
Reusable surfaces
Power center pages, links and QR from one source.
Room to expand
Add providers without redesigning every equestrian workflow.
One consistent payment layer beneath every center journey.
Perno Equestrian creates context
The booking, entry or offer defines the payment.
Orchestration routes
Perno chooses the compatible production setup.
The result returns
The payment and operational record stay connected.
One core supports every equestrian payment surface.
Payment orchestration
Must staff choose a provider for every payment?add
No. Perno can use orchestration routing from the configured center setup.
Can provider-specific accounts still be managed?add
Yes. Merchant accounts remain part of Perno Orchestration configuration.