For the complete documentation index, see llms.txt. This page is also available as Markdown.
Create Transaction
To initiate a new transaction with the Tutelar Server, the following steps must be adhered to for proper setup and execution:
Whitelist Server IP Address:
Before initiating the transaction process, ensure that your server’s IP address is whitelisted in the Tutelar Panel. This step is crucial as it authorizes your server to communicate with the Tutelar Server.
Generate API Keys:
Generate the necessary API keys from the Tutelar Panel. These keys will be used to authenticate your API requests to the Tutelar Server, ensuring secure and verified communication.
Submit Transaction via Create Transaction API:
Utilize the Create Transaction API to submit a new transaction to the Tutelar Server. Ensure that all relevant transaction details are included in your request. The Tutelar Server will validate the submitted transaction data.
Receive Transaction Validation Response:
After validation, you will receive a response from the Tutelar Server containing the following critical pieces of information:
Risk Score: A numerical value indicating the risk level of the transaction.
Risk Status: A status indicator (e.g., high, medium, low) that reflects the assessed risk.
Reference Number: A unique identifier for the transaction, useful for tracking and reference purposes.
Customer Information: Details about the customer involved in the transaction.
Decision Making Based on Risk Assessment:
Use the risk score, risk status, reference number, and customer information to decide whether to allow or deny the customer's payment. This decision is vital for fraud prevention and ensuring the security of transactions.
Update Transaction Status:
Upon successful or failed payment, it is imperative to call the Transaction Status API to update the status of the previously completed transaction. This step ensures that the transaction records are accurate and up-to-date.
By following these steps, you can effectively manage and assess transaction risks, making informed decisions to approve or deny payments, thereby maintaining a secure and reliable payment process
The customer IP address involved in the transaction
Example: 49.207.180.255
amountnumber · floatRequired
The total amount of the transaction
Example: 299.99
currencyCodestringRequired
The currency code in which the transaction is conducted (e.g.,INR, USD, EUR).
Example: INR
riskCodestringOptional
A code representing the risk level of the transaction
Example: CL00001
productTypestringOptional
The type of product being purchased
Example: Ecommerce
productDescriptionstringOptional
A description of the product being purchased
Example: Table
paymentChannelstring · enumOptional
Indicates the channel through which the payment is processed, such as a payment gateway (pg), quick_collect, or other supported payment channels.
Example: pgPossible values:
paymentOptionstring · enumOptional
Represents the specific payment option selected by the customer, such as payment link, EMI, or other supported payment options.
Example: payment_linkPossible values:
paymentInstrumentstring · enumRequired
The type of payment instrument used (card, netbanking, upi etc)
Example: cardPossible values:
Responses
106
Duplicate order id received
application/json
200
Successful transaction creation
application/json
successbooleanOptionalExample: true
messagestringOptionalExample: Transaction risk results are
401
Invalid authentication credentials
application/json
422
Merchant status issues
application/json
500
Product is unsubscribed
application/json
post/api/v2/fraud-detector/transaction/create
The Customer object is optional. If values are provided, they will be validated
Info:
The maximum length of request parameters
Info:
Request Parameter Validation Rules
MCC API
Industry API
Pre Auth and Post Auth
The Transaction Create API has been enhanced to support both pre-authorization (pre-auth) and post-authorization (post-auth) transaction flows.
API Description
The Create API handles the creation of transactions in the pre-auth flow. For the post-auth flow, it also updates transaction details if transactionId and status are present in the request payload (postData).
API Endpoint: https://stgsecctrl.tutelar.io/api/v1/fraud-detector-onstream/transaction/create
Process Flow
Pre-Auth Flow:
The API performs the standard transaction creation logic.
Post-Auth Flow:
The API performs the standard transaction creation logic.
Additionally,
It updates the transaction status, velocity, and risk results.
It calculates SLA durations and schedules jobs to update SLA transactions if required.
Post Data
The request payload should be a JSON object containing the necessary transaction details.
For post-auth flows, it should include transactionId, status, and optionally statusReason.
If the transaction is made in the post-auth flow, add the following data to the create API post data: