Product

Tools that keep every payment in view.

A clear foundation for payments, customers, billing, payouts, and the operational details around them.

Application first

These capabilities are prepared for test mode. Payment tools and keys appear in your dashboard only after the merchant application is approved. Live availability depends on a separate provider and acquirer review.

Core capabilities

The pieces of a complete payment operation.

Payments

Create a payment, retrieve it, capture a manual authorization, and refund all or part of it. Amounts are minor units.

Read payments docs

Customers

Store a customer email and name in test mode and attach later payments to that id.

Read customers docs

Payouts

The dashboard shows the test balance after fees and refunds. Payouts stay in manual review until an operator marks one paid.

Read payout review docs

Billing

Subscriptions and invoices are test-mode records. They do not pull a card on a schedule.

Read billing docs

Webhooks

LaxoPay posts a signed event to the merchant URL. Retries run at 1 minute, 5 minutes, and 30 minutes.

Read webhook docs

Dashboard

See application status, test payments, customers, API key prefixes, and webhook endpoints.

Read dashboard docs

Designed for confidence

The controls are part of the workflow.

Passwords are hashed. Sessions stay in HttpOnly cookies. API keys are stored as hashes. Webhooks are signed. The operator role is separate from merchant accounts.

Test mode isolationCard numbers choose an outcome; they are not stored or sent to a network.

Settlement directionChoose a settlement currency on the application. Availability follows approval.

Reviewable workspaceApplication status, keys, test balance, and endpoints stay together.

Build with LaxoPay

Your next chapter starts here.

Apply for a merchant account. Prepare your integration.
Build your first payment flow in an approved test workspace.

Get Started Explore the docs