arrow_backPerno Equestrian
The payment foundation

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.

account_tree
What you get

One consistent payment layer beneath every center journey.

petsPerno Equestrian
account_treePerno Orchestration
account_treePayment orchestration
Verified platform activity

Built on payment infrastructure already working in production.

A conservative snapshot of Perno's production footprint—not a forecast or an invented customer claim.

price_check
55k+

successful production payments recorded

account_balance
3

payment providers represented in live transactions

domain
5

specialist industry payment products

account_tree
976k+ PLN

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.

Inspect the product evidence: See what we ship View supported PSPs Explore the API
Why change

Payment-provider plumbing should not shape the rider experience.

check_circle

Each payment provider has different APIs and statuses.

check_circle

Return URLs and webhooks are easy to misconfigure.

check_circle

New payment surfaces repeat the same integration work.

What you get

A shared foundation with vertical context on top.

hub

Orchestrated routing

Use compatible merchant accounts and payment methods.

shield

Hosted checkout

Keep provider logic away from the center dashboard.

webhook

Status updates

Receive provider results into Perno records.

keyboard_return

Return journeys

Use consistent success and cancellation destinations.

qr_code_2

Reusable surfaces

Power center pages, links and QR from one source.

extension

Room to expand

Add providers without redesigning every equestrian workflow.

How it works

One consistent payment layer beneath every center journey.

Step 01

Perno Equestrian creates context

The booking, entry or offer defines the payment.

Step 02

Orchestration routes

Perno chooses the compatible production setup.

Step 03

The result returns

The payment and operational record stay connected.

Common uses

One core supports every equestrian payment surface.

check_circleLesson checkout
check_circleCompetition entry
check_circleCenter membership
check_circleOne-time deposit
check_circleDirect payment link
check_circleQR payment
Questions

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.

Build the equestrian journey on one payment core.