MERCHANT INTEGRATIONS

Access with purpose,
not for display

Technical access, sandbox, and documentation are issued after company and project review. The public site explains the architecture and onboarding path only.

Talk to our team Dashboard

Integration-ready architecture

MERIDIANMERCHANT INTEGRATIONS

Project keys

Sandbox

Signed events

Live operating layer

Built around the actual flow

01Project keysLIVE

02SandboxLIVE

03Signed eventsLIVE

What your business gets

Merchant integrations

Isolated projects

Every key, webhook, and limit belongs to one project.

Secure issuance

Secrets are shown once, stored as hashes, and support rotation.

Validated launch

Negative paths and webhook replay are tested before production.

How it works

not for display

Apply

The company describes its business and payment flow.

Review

An administrator approves the company and creates a project.

Access

The team receives sandbox, keys, and private documentation.

Production

Methods, limits, and live callbacks are enabled after acceptance.

Operational picture

Everything that matters, in one operating layer

Status, project rules, and events stay connected. Teams can see what is happening now and which configuration was applied to every operation.

Isolated projects
Secure issuance
Validated launch

LiveMERCHANT INTEGRATIONS

Current projectMerchant integrationsMERIDIAN / 01

01Project keysCaptured

02SandboxCaptured

03Signed eventsCaptured

Event trailLIVE

01Apply

02Review

03Access

04Production

MERIDIAN PAYMENTS

Apply for access scoped to a real project.

Talk to our team

Access with purpose,not for display