Overview

ParuPay is the payment service. Your shop stays your own system: it saves the order, charges with a payment link or server-to-server, and updates that order when a webhook arrives.

Save the order on your server

Create the order as pending. The amount on the payment link is the amount the customer pays. $10.00 is sent as 1000.

Ask ParuPay for a payment link

Your backend calls POST /v1/payment_links with the secret key. The response includes checkout_url.

Send the customer to hosted checkout

The customer pays on the ParuPay page. Your site does not collect the card number or CVC.

Update the order from the webhook

payment_intent.succeeded means paid. payment_intent.payment_failed means failed. charge.refunded means refunded. payment_intent.cancel means canceled.

Confirm it in the merchant portal

The same payment appears as success, pending, failed, or cancelled.

Sandbox uses sk_test_. Production uses sk_live_. Follow Getting started, or send a request from Try the API.

Accept online payments

Pre-built

The card form is hosted by ParuPay. You only redirect the customer.

Capability	Description
Pay by link	Create the link from your server and share `checkout_url`, or use it as the pay button on your own checkout.

API

Integration	Description
Secret key	Server calls send `Authorization: Bearer sk_test_` or `sk_live_`. The publishable key is only for hosted checkout.
Payment link API	`POST /v1/payment_links` creates the link. `GET /v1/payments` and `GET /v1/charges` read the result.
Server-to-server	One `POST /v1/s2s/payments`. ParuPay chooses 2D (capture now) or 3D (ACS) from the card.
API reference	Every endpoint: payment links, payment intents, charges and refunds, with pagination and errors.
Webhooks	ParuPay POSTs the payment result to your server, including when the customer never returns to your site.

Features

Feature	Description
Hosted checkout	Card entry happens on the ParuPay payment page.
Server-to-server	Charge from your server. One POST; 2D vs 3D is decided from the card.
3D Secure	Some cards email a one-time password. Others pay without OTP.
Payment statuses	Success, pending, failed, and cancelled. See Payment statuses for the API values.
Webhooks	Success, failure, and refund are sent server to server.
Your order id	Put `order_id` in metadata. Webhooks send `order_id` back so you can match the order.
Sandbox	Every merchant tests on the ParuPay sandbox with `sk_test_` and the standard testing cards.
Live	`sk_live_` charges real cards once your account is approved. Live server-to-server is enabled per account.

Start

Accept payments

Developers

Accept online payments

Pre-built

API

Features