Skip to main content

​
Overview

Secure Payment Pages let you generate a hosted payment URL from the API and redirect the payer to a dedicated payment experience. This feature is useful when you want to reduce frontend tampering risk and separate payment execution from your checkout UI.

​
Built-in contract safety check

Before signing, the secure page validates that the transaction targets official Request Network contracts. The payer-facing status copy is:
  • “This is a safe smart contract”
  • “The smart contract you are interacting with is an official Request Network smart contract, it is audited and valid.”
If validation fails, the secure page warns the payer and prevents continuing with unsafe contract interactions.

​
How the flow works

1

Create a secure payment link

Call POST /v2/secure-payments with one or more requests.The API creates Request records and returns:
  • requestIds
  • token
  • securePaymentUrl
2

Redirect the payer to the hosted page

Send the payer to securePaymentUrl.
3

Payer reviews payment details

The hosted page loads the payment details and prepares the required transaction flow.
4

Sign and submit payment transactions

The payer signs the returned transaction set from their wallet. Depending on token approvals, this can be one or more transactions.

​
Authentication

Both secure payment endpoints accept:
  • x-api-key, or
  • x-client-id with browser Origin
See Authentication for implementation options.

​
API Reference

POST /v2/secure-payments

Create a secure payment entry and return a hosted secure payment URL. View the complete endpoint documentation with request/response schemas and examples.

​
Status outcomes

  • 200: token is valid and payable
  • 403: token expired or status is not payable
  • 404: token not found
  • 409: payment already completed

​
Next pages

Secure Payments API Reference

Endpoint details, request and response schemas, and error codes.

Supported Networks and Currencies

Check supported chain and currency coverage before creating links.