Developers

Build against one payment API.

Start with Sale, 3DS server-to-server, recurring payments, refunds, voids, settlement, response codes and token migration flows.

View documentationDocumentation
Documentation map

Documentation built around payment flows.

A clear left navigation, flow-based guides and code examples for each payment lifecycle operation — organised the way an integration actually proceeds.

Payments reference9 sections

Accept payments

POST/payment

Create a sale and capture it on your schedule.

SaleVoid / Settle

Authenticate payments

POST/payment

Server-to-server 3DS attached to the same request.

3D Server-to-Server

Manage lifecycle

POST/settlePOST/refundPOST/void

Recurring billing, refunds, voids and settlement.

RecurringRefundSubscription Management

Understand responses

GET/transaction/{id}

Statuses and mapped response codes for every attempt.

Response codes

Migrate tokens

POST/payment

Move stored card credentials onto the platform.

Token Migration
API lifecycle

One sale, the whole lifecycle.

Request, decision, response — then every lifecycle operation against the same transaction. The flow your integration follows is the flow the documentation follows.

Integration sequence

Request

POST

POST /payment

{

"amount": "•••",

"currency": "•••",

"cardToken": "tok_••••",

"capture": true

}

Decision

Approved3DS requiredReview / Decline

Response

{

"status": "approved",

"code": "•••",

"transaction": "•••"

}

Then operate the lifecycle
POST/settlePOST/refundPOST/voidGET/transaction/{id}
Integration surface

A small, predictable API surface.

Five endpoints cover the integration — from the first sale to settlement, refunds and response handling. Token migration runs through the same payment request.

EndpointPurposeLifecycle stage
POST/paymentSale — including 3DS server-to-server and recurring via tokenCreate
POST/settleCapture an authorized paymentSettle
POST/voidCancel before settlementBefore settlement
POST/refundReturn a settled paymentAfter settlement
GET/transaction/{id}Status and mapped response codesAnytime

Endpoints as published in the API documentation. Full payloads, fields and response codes live in the reference.

View Documentation
Developer access

Ready to integrate Paysation?

Talk to our team about API access, documentation, test credentials and integration flows.

API accessTest credentialsIntegration support
Talk to salesView docs