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 Prime Pay-In widget. Through the widget, the merchant's end customer can make a deposit or payment to the merchant using UPI. The payment is settled in USDT into the merchants wallet.
Endpoint
POST
https://api.tylt.money/p2pRampsMerchant/createInstance
Request Headers
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.
When using the API, ensure to include your API Key and generate the signature for the request payload using your API Secret. The tables provided above contain example values for illustration purposes only. Please refer to the code snippets for detailed instructions on how to sign the request and generate the signature properly.
Request Body
Field Name
Type
Description
isBuyTrade
number
Must be set to 1 for a Pay-In transaction.
userDetails
JSON Object
Custom fields associated with the user, supplied by the merchant. These fields are included in webhook notifications and other API responses for easy reference and tracking. An empty object can be sent.
merchantOrderId
string
A UUID used by the merchant to reference this instance or any transaction related to it.
callBackUrl
string
The URL to which payment status updates are sent.
redirectUrl
string
The URL to redirect the user after completing the payment.
amount
number
Non-mandatory. This is the amount the user wants to deposit in USDT or INR equivalent. If this field is empty user can enter the value in the payment flow.
currencySymbol
string
To be used if using amount
. Supported Currency is "USDT" or "INR" only.
userEmail
string
Non-mandatory. If the merchant wants to share the user email id they can use this field. If this field is empty, the user will have to provide the email or SSO login during the payment flow.
isKYCNeeded
number
1 or 0. If set to 0 the user will not be required to complete KYC or provide KYC. If field is in passed, default behaviour is KYC is required. This bypass needs to be approved by the admin for the Merchant.
isUTRNeeded
number
To be set Mandatorily
as 1. The user will be required to provide the UTR (Unique Transaction Reference) number after making the payment. This is a compliance
step as it significantly reduces payment failures, disputes, and chargebacks while also enabling seamless processing through our automated Lightning Bridge.
Flow Modularity
Merchants have the flexibility to enable or disable the following modules within the customer flow:
User Email Sign-in:
The system requires an email for user identification.
Merchants can provide the email by passing it in the
userEmail
field within the request body.Alternatively, if the merchant prefers the user to enter their email during the payment process, this field can be left empty.
KYC Bypass:
In certain use cases, KYC verification may not be required for the end user.
To bypass KYC, set
isKYCNeeded
to 0.When enabled, the user will not be required to complete KYC, and any existing KYC records will not be checked.
Important: Merchants must have admin pre-authorisation to use the KYC bypass feature.
Code Snippet
Response
Last updated