Create a payment session | Redpin

A Payment Session is a temporary, secure, and hosted interaction between your platform and Redpin, designed to facilitate cross-border payments.

The OAuth 2.0 Authenticated Create Payment Session API allows you to create a new hosted payment session. You provide the payment details (amount, items, recipients, etc.) and session configuration (like allowed domains), and receive a unique session URL in response. This URL can be embedded in your app or website to launch the hosted payment flow in a secure, guided interface.

Payment sessions are time-bound and will automatically expire at the specified expires_at timestamp. Once expired, the session URL becomes inaccessible and can no longer be used to complete the payment. If the payment is not completed before the session expires, a new session must be created again to initiate the payment.

For real-time payment status updates, use the Webhook Subscription API to subscribe to the PAYMENT STATUS event.

A Payment Session is a temporary, secure, and hosted interaction between your platform and Redpin, designed to facilitate cross-border payments. The [OAuth 2.0 Authenticated](/api-guide/getting-started/authentication#oauth-20-authentication) Create Payment Session API allows you to create a new hosted payment session. You provide the payment details (amount, items, recipients, etc.) and session configuration (like allowed domains), and receive a unique session URL in response. This URL can be embedded in your app or website to launch the hosted payment flow in a secure, guided interface. Payment sessions are time-bound and will automatically expire at the specified `expires_at` timestamp. Once expired, the session URL becomes inaccessible and can no longer be used to complete the payment. If the payment is not completed before the session expires, a new session must be created again to initiate the payment. For real-time payment status updates, use the Webhook Subscription API to subscribe to the [PAYMENT STATUS](/api-reference/customers/api-integration/webhooks/create-webhook) event.

Authentication

AuthorizationBearer

OAuth 2.0 Bearer token authentication. This API uses OAuth 2.0 Client Credentials flow. Please refer to the Authentication section for detailed information on how to obtain and use your OAuth credentials.

Path parameters

customer_idstringRequired

A unique identifier for the customer initiating the session.

Request

This endpoint expects an object.

client_customer_refstringRequired

The API caller’s internal customer ID for the person initiating the payment. It must be the same reference used when invoking the Pre-eligibility check API.

client_reference_idstringRequiredformat: "^[A-Za-z0-9_-]+$"1-36 characters

A unique reference identifier for this payment session in your system. This reference is used to uniquely identify and track this specific payment.

Validation Rules:

Uniqueness is enforced for third-party payments only: must be unique per customer (per Redpin customer_id); duplicate references for the same customer will be rejected. Hosted sessions are third-party, so this applies.
Maximum length: 36 characters
Allowed characters: alphanumeric (A-Z, a-z, 0-9), hyphens (-), and underscores (_)

A unique reference identifier for this payment session in your system. This reference is used to uniquely identify and track this specific payment. **Validation Rules:** - Uniqueness is enforced for third-party payments only: must be unique per customer (per Redpin `customer_id`); duplicate references for the same customer will be rejected. Hosted sessions are third-party, so this applies. - Maximum length: 36 characters - Allowed characters: alphanumeric (A-Z, a-z, 0-9), hyphens (-), and underscores (_)

amountobjectRequired

due_datedateRequired

The date by which the amount must be credited to all recipient bank accounts. Must follow the ISO 8601 format (YYYY-MM-DD) and be at least 5 calendar days from the current date.

The date by which the amount must be credited to all recipient bank accounts. Must follow the [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format (YYYY-MM-DD) and be at least 5 calendar days from the current date.

purpose_of_transactionenumRequired

Purpose of the transaction. Must be one of the predefined values. Validation Rules:

Must be provided and cannot be null or empty
Must be one of the allowed enum values
Case sensitive - must match exactly

Purpose of the transaction. Must be one of the predefined values. **Validation Rules:** - Must be provided and cannot be null or empty - Must be one of the allowed enum values - Case sensitive - must match exactly

recipient_detailslist of objectsRequired

List of recipients who will receive payment funds. Independent of items, allowing flexible fund distribution.

Validation Rules:

At least one recipient is required
Sum of all recipient amounts must equal the session total amount
All recipient currencies must match the session amount currency

List of recipients who will receive payment funds. Independent of items, allowing flexible fund distribution. **Validation Rules:** - At least one recipient is required - Sum of all recipient amounts must equal the session total amount - All recipient currencies must match the session amount currency

itemslist of objectsOptional

List of payment items describing what is being paid for in this session. Each item represents a line item (property, invoice, booking, service fee, etc.).

Validation Rules:

At least one item is required
Sum of all item amounts must equal the session total amount
All item currencies must match the session amount currency

List of payment items describing what is being paid for in this session. Each item represents a line item (property, invoice, booking, service fee, etc.). **Validation Rules:** - At least one item is required - Sum of all item amounts must equal the session total amount - All item currencies must match the session amount currency

allowed_originslist of stringsOptional

Origins (or app identifiers) from which the hosted payment session is expected to be launched. Also used as a proxy to determine whether OTP based verification is required.

Each entry must be one of the following:

A valid HTTPS origin for web applications (e.g., https://example.com)
A valid Android package name (e.g., com.example.app) for native Android apps
A valid iOS bundle identifier (e.g., com.example.iosapp) for native iOS apps

OTP enforcement logic:

If this field is empty or omitted → OTP is required. The customer will be prompted to enter an OTP sent to the mobile number supplied during Third-Party Customer creation. The customer can choose to receive the OTP via SMS or voice call based on their preference.
If this field is set (contains one or more entries) → OTP is not required.

Notes:

Wildcards or regular expressions are not supported.
If this field is not provided, the session will be accessible from any origin and OTP will be enforced as described above.

Origins (or app identifiers) from which the hosted payment session is expected to be launched. Also used as a proxy to determine whether OTP based verification is required. Each entry must be one of the following: - A valid HTTPS origin for web applications (e.g., https://example.com) - A valid Android package name (e.g., com.example.app) for native Android apps - A valid iOS bundle identifier (e.g., com.example.iosapp) for native iOS apps OTP enforcement logic: - If this field is empty or omitted → OTP is required. The customer will be prompted to enter an OTP sent to the mobile number supplied during [Third-Party Customer](/api-reference/customers/api-integration/third-parties/create-third-party-customer) creation. The customer can choose to receive the OTP via SMS or voice call based on their preference. - If this field is set (contains one or more entries) → OTP is not required. Notes: - Wildcards or regular expressions are **not supported**. - If this field is **not provided**, the session will be accessible from **any origin** and OTP will be enforced as described above.

Response

Payment session created successfully

session_idstring

A unique identifier automatically generated for each payment session.

client_reference_idstring

The unique payment reference provided by the client in the request, returned for confirmation and tracking purposes.

expires_atdatetime

The exact date and time (in ISO 8601 format) when the session becomes invalid.

The session URL becomes inaccessible and can no longer be used to complete the payment. If the payment is not completed before the session expires, a new session must be created again to initiate the payment.

The exact date and time (in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format) when the session becomes invalid. - The session URL becomes inaccessible and can no longer be used to complete the payment. If the payment is not completed before the session expires, a new session must be created again to initiate the payment.

session_urlstring

A hosted payment page URL that displays Redpin’s secure payment flow. This URL can be integrated into your mobile app (via webview) or website (via redirect or iframe), allowing users to review payment details and complete the cross-border transaction.

Errors

A Payment Session is a temporary, secure, and hosted interaction between your platform and Redpin, designed to facilitate cross-border payments.

For real-time payment status updates, use the Webhook Subscription API to subscribe to the PAYMENT STATUS event.

1	curl -X POST https://api.redpincompany.com/v1/customers/customer_123/sessions \
2	-H "Authorization: Bearer <token>" \
3	-H "Content-Type: application/json" \
4	-d '{
5	"client_customer_ref": "CUST-1002-TXN",
6	"client_reference_id": "PAY-2025-08-20-002",
7	"amount": {
8	"currency": "AED",
9	"value": 87500
10	},
11	"due_date": "2025-08-20",
12	"purpose_of_transaction": "PROPERTY_PURCHASE",
13	"recipient_details": [
14	{
15	"amount": {
16	"currency": "AED",
17	"value": 80000
18	},
19	"payment_reference": "BLV-805-DEPOSIT-INS1",
20	"purpose_of_transaction": "PROPERTY_PURCHASE",
21	"recipient_id": "123456"
22	},
23	{
24	"amount": {
25	"currency": "AED",
26	"value": 5000
27	},
28	"payment_reference": "PLATFORM-FEE-AUG",
29	"purpose_of_transaction": "BILL_PAYMENTS",
30	"recipient_id": "654321"
31	},
32	{
33	"amount": {
34	"currency": "AED",
35	"value": 2500
36	},
37	"payment_reference": "AGENT-COMM-AUG",
38	"purpose_of_transaction": "PROPERTY_PURCHASE",
39	"recipient_id": "789012"
40	}
41	],
42	"items": [
43	{
44	"item_name": "Boulevard Residences - Unit 805 - Initial deposit",
45	"amount": {
46	"currency": "AED",
47	"value": 50000
48	},
49	"item_ref": "INV-2025-10450",
50	"item_type": "deposit"
51	},
52	{
53	"item_name": "Boulevard Residences - Unit 805 - Installment 1 of 10",
54	"amount": {
55	"currency": "AED",
56	"value": 30000
57	},
58	"item_ref": "INV-2025-10451",
59	"item_type": "installment"
60	},
61	{
62	"item_name": "Platform transaction fee",
63	"amount": {
64	"currency": "AED",
65	"value": 5000
66	},
67	"item_ref": "INV-2025-10452",
68	"item_type": "platform_fee"
69	},
70	{
71	"item_name": "Agent commission",
72	"amount": {
73	"currency": "AED",
74	"value": 2500
75	},
76	"item_ref": "INV-2025-10453",
77	"item_type": "commission"
78	}
79	],
80	"allowed_origins": [
81	"https://app.example.com"
82	]
83	}'

1	{
2	"session_id": "cbf9e10a-b876-491c-9c28-0d1be0581bf7",
3	"client_reference_id": "PAY-2025-001-TXN",
4	"expires_at": "2025-07-03T08:18:53.631073Z",
5	"session_url": "https://app.redpin.com/session/cbf9e10a-b876-491c-9c28-0d1be0581bf7"
6	}