Create Transaction
To initiate a new transaction with the Tutelar Server, the following steps must be adhered to for proper setup and execution:
Last updated
To initiate a new transaction with the Tutelar Server, the following steps must be adhered to for proper setup and execution:
Last updated
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 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
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
Pre-Auth Flow:
The API performs the standard transaction creation logic.
The API performs the standard transaction creation logic.
Additionally, if transactionId
and status
are present in the request payload:
It updates the transaction status, velocity, and risk results.
It calculates SLA durations and schedules jobs to update SLA transactions if required.
The request payload should be a JSON object containing the necessary transaction details. For post-auth flows, it should include transactionId
and status
:
If the transaction is made in the post-auth flow, add the following data to the create API post data:
Valid Transaction ID and Status:
Invalid Status With Transaction ID:
Status Without Transaction ID:
Existing Transaction ID:
/api/v1/fraud-detector/transaction/create
Encoded device fingerprint information
ewogICJpcEFkZHJlc3MiOiAiNDkuMjQ5LjYyLjE5OCIsCiAgImJyb3dz
Unique order ID to identify the transaction
ORD_10726
The customer IP address involved in the transaction
49.207.180.255
The total amount of the transaction
299.99
The currency code in which the transaction is conducted (e.g.,INR, USD, EUR).
INR
A code representing the risk level of the transaction
CL00001
The type of product being purchased
Ecommerce
A description of the product being purchased
Table
The type of payment instrument used (e.g., credit card, debit card)
card
Contains detailed information about the customer involved in the transaction, including their name, email address, phone number, and the country code associated with their phone number.
Contains detailed information about the merchant processing the transaction, including a unique identifier, name, email address, website URL, business name, and phone number
The billing details for the transaction
The shipping details for the transaction
Contains specific details related to the payment method used for the transaction, including the name on the payment instrument, a secure token hash for the payment data, and the Bank Identification Number (BIN) of the payment instrument.
The Merchant Category Code, which classifies the type of business.
The industry in which the merchant operates.
UDF (User Defined Fields) allow for custom data storage: udf1-udf8 are customizable fields. name: Label of the field. value: Content of the field, tailored to user needs.