Create a Pay-in Instance
This endpoint allows you to create a new payment instance and receive a in the response an instanceId.
The instanceId can be used further along with the other exposed API's to create a completely customisable host to host integration.
Endpoint
POST
https://api.tylt.money/h2h/in/upi/createPayinInstance
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
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
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.
amount
number
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
Mandatory. Supported Currency is "USDT" or "INR" only.
userEmail
string
Mandatory. The emailId of the end user.
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
1 or 0. If set to 1, the user will be required to provide the UTR (Unique Transaction Reference) number after making the payment. This is a recommended
setting as it significantly reduces payment failures, disputes, and chargebacks while also enabling seamless processing through our automated Lightning Bridge.
Flow Modularity
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