Base URL
All API requests use the following base URL:Create a payment link
Send aPOST request to /payment-links to create a new payment link.
| Field | Type | Required | Description |
|---|---|---|---|
amount | string | Yes | The payment amount as a decimal string (e.g., "75.00") |
currency | string | Yes | The digital asset code (e.g., "USDT", "BTC", "ETH") |
description | string | No | An optional label or reference for this payment link |
url field contains the shareable link to send to your customer.
List payment links
Send aGET request to /payment-links to retrieve all your payment links.
| Parameter | Type | Description |
|---|---|---|
status | string | Filter by status: active, paid, expired, deactivated |
limit | integer | Maximum number of results to return (default: 20, max: 100) |
offset | integer | Number of results to skip for pagination |
Retrieve a payment link
Send aGET request to /payment-links/{id} to retrieve a single payment link by its ID.
Payment link statuses
| Status | Meaning |
|---|---|
active | The link is live and accepting payments |
paid | A successful payment has been received |
expired | The link has passed its expiration time |
deactivated | The link has been manually disabled |
Integration pattern
A typical integration flow looks like this:Backend creates a payment link
Your server sends a
POST /payment-links request to PIK with the order amount and currency.Redirect the customer
Extract the
url from the PIK response and redirect your customer to it. PIK handles the checkout UI.See Webhooks to learn how to receive real-time payment confirmation events in your application.
