Create Payment

post

https://api.sandbox.layer1.com/api/v1/pay/summary

Creates a Payment Link — direction IN (request a deposit) or OUT (send crypto). The response carries the payment uuid plus a redirectUrl you can share with the counterparty for the Hosted Payments Page. From 1 July 2026, complianceDetails is required on every create request — see Travel Rule — Post 1 July 2026.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

The request data required to create a payment in or a payment out

merchantId

string

required

length between 6 and 50

Defaults to 5C8D8D78-366A-4AFB-B658-A64CE543C5DB

UUID of the wallet that will settle the payment. Identical to the wallet's ID — get it from the Wallets screen in the Portal.

amount

number

required

≥ 0

Defaults to 223.05

The payment amount.

expiryMinutes

integer

Defaults to 20

The time period after which payment expires. Overrides the default expiry limit.

currency

string

enum

required

length between 2 and 20

Defaults to EUR

The currency to display to end users. This can be any cryptocurrency code from the supported list or any standard fiat currency code.

returnUrl

string

Defaults to https://my-shop.com/payment-complete?ref=xyz

The URL that the customer will be redirected to if they click 'Back to Merchant' button on the payment web page. Must start with https://

reference

string

required

length between 6 and 255

Defaults to myUniqueRef333

The custom payment reference ID to tie the payment to your customer.

type

string

enum

required

Defaults to IN

Defines whether a payment is incoming (IN) or outgoing (OUT). IN is for receiving payments from customers, OUT is for sending payments.

Allowed:

payInDetails

object

The payment in details, only needed when "type" is IN.

payOutDetails

object

The payment out details, only needed when "type" is OUT

complianceDetails

object

Specify compliance details for payments and channels when required by your integration.

metadata

object

A key-value map containing metadata. Keys and values have specific length and format restrictions.

Responses

200OK

400Bad Request - The request was invalid or cannot be otherwise served.

500Internal Server Error - Something unexpected went wrong on the server.