Direct Payments

What is this?
A direct (host-to-host) card charge where the Merchant collects card data in its own UI, encrypts it with a key from PlexyPay, and creates a payment via POST /v1/payments/direct. 3-D Secure may be required by the Bank/ACS.

Actors

User — payer in the merchant’s UI

Merchant — frontend + backend that collects and encrypts card data

PlexyPay — payment API/orchestrator (routes, 3-DS handling, webhooks)

Bank / ACS — issuer/acquirer side (authorization & 3-D Secure)

When to use

You need a fully API-only flow (no hosted checkout UI).

You control the entire user experience and PCI scope.

You can handle 3-D Secure redirects/challenges.

Security & Prerequisites

Encryption key: obtain via GET /v1/keys; encrypt card data client-side.

Idempotency: send an Idempotency-Key header for every charge attempt.

Webhooks: expose an HTTPS endpoint to receive asynchronous status updates.

Direct Payment Integration Flow

Direct Payments

Actors#

When to use#

Security & Prerequisites#

Actors

When to use

Security & Prerequisites