Create a Pay-in Instance

This endpoint allows you to create a new payment instance and receive a URL that can be used to launch the Tylt CrossRamp Open Banking Pay-In widget. Through the widget, the merchant's end customer can make a deposit or payment to the merchant using Open Banking. The payment is settled in USDC into the merchants wallet.

Endpoint

POSThttps://api.tylt.money/v2/prime-fiat/instance/payin

Request Headers

Name
Type
Example
Description

X-TLP-APIKEY

string

93ee3c5e133697251b5362bcf9cc8532476785t8768075616f58d88

Your Tylt API Key, used to identify your account in API requests.

X-TLP-SIGNATURE

string

d0afef3853dfc8489c8b9affa5825171fdd7y7685675e4966a05f66ed2b3eaf9462b3c9c0

HMAC SHA-256 signature generated using the API Secret Key to secure the request.

circle-exclamation

Request Body

Field Name

Type

Description

userDetails

JSON Object

Custom fields associated with the end user making a payment to the merchant. These fields are echoed back in webhook notifications and other API responses for tracking and reconciliation.You may send an empty object ({}).

Reserved keys (auto-populate payment widget)

The following keys are reserved. If you include any of them, they will be used to pre-fill the corresponding fields in the hosted payment widget:

  • firstName (string)

  • lastName (string)

  • email (string)

  • country (string)

  • dob (string, format: YYYY-MM-DD)

If a reserved field is not provided, the end user will be prompted to enter that field in the widget (if required by the flow).

merchantOrderId

string

Mandatory. A UUID used by the merchant to reference this instance or any transaction related to it.

callBackUrl

string

Mandatory. The URL to which payment status updates are sent.

redirectUrl

string

Mandatory. The URL to redirect the user after completing the payment.

amount

number

Mandatory. This is the amount the user wants to deposit in EUR.

currencySymbol

string

Mandatory. Supported Currency is "EUR" only

merchantDetails

JSON Object

The merchantDetails object identifies the merchant on whose behalf the transaction is being processed. This information is required for transaction attribution, reconciliation, risk screening, and regulatory reporting. If the integrator is acting as a Merchant of Record, the details of the underlying end merchant must be provided If the integrator is the end merchant, the details of its own business must be provided. The following fields must be provided inside the merchantDetails object:

  • merchantName The legal or DBA name of the merchant.

  • merchantUrl The official website URL of the merchant. This must be a valid HTTPS URL representing the merchant’s active operating website.

  • merchantInternalId A unique internal identifier assigned by the merchant. This identifier is used for reconciliation, reporting, and ongoing transaction tracking and must remain consistent across transactions.

All fields within merchantDetails are mandatory. Transactions submitted without this object, or with incomplete merchant details, will be rejected. Transactions with new merchantDetails go through an automated internal review process.

cryptoUi

number

Controls the visual mode of the hosted payment widget. Default is 1. If set to 1, the widget UI is adapted to showcase a crypto purchase flow. If set to 0, the widget UI is adapted to showcase a fiat payment flow.

Code Snippet

Response

Last updated