Transaction
Last updated
Was this helpful?
Last updated
Was this helpful?
A query submitted to the Anti-Fraud services is called a Transaction. A transaction may contain the execution of one or more services configured in the query model or informed in the request body. These services may be internal analyses or external queries that are performed on the processing conveyor. After that, based on validation rules, the status is set for the transaction.
Services and validation rules can be configured only in the query template.
A transaction is characterized by an endpoint where the required services can be informed and a set of rules validated.
Get your transaction list summarized with pagination and filters.
/transactions
The maximum amount of records that should be returned in the response, e.g. _limit=5. Max value is 10 and default is 10.
Sort the records returned in response by creation date in ascending or descending order. Descending (default): _order=desc Ascending : _order=asc
Search for too many template models by references of the templateId on the account. For multiple templates, separate the values using the pipe symbol, e.g. _templates=templateId1|templateId2|templateId3.
Search the records created on or after any given day, e.g. _startCreatedDate=2022-01-01.
Search the records created on or before a specified day, e.g. _endCreatedDate=2022-01-30.
Customer access token. See more in the 'Authentication' topic of this section.
Submission of the necessary person or company data and the template model against which the verification services shall be executed, as well as the set of rules to be validated.
/transactions
Parameter that defines the onboarding origin. Must be set to TRUST.
Customer access token. See more in the 'Authentication' topic of this section.
Unique ID of the Query Template (configured in Trust Platform).
Free to add any kind of attribute, ideal for linking IDs or other information in the transaction.
Callback URL (webhook).
Person or company data that can be included within the transaction request data.
List of files to be analysed.
Retrieve the result data of a transaction.
/transactions/{transactionId}
Transaction identifier.
Flag for including transactions related to onboarding pf_pf. e.g. _includePfRelationships=true.
Flag to include the cropped versions of the images of the sended documents. e.g. _includeCroppedImages=true.
Flag to set the language in the description of the reasons for manual failures. Possible values are 'en' or 'pt'. Default is 'pt'. e.g. _lang=en.
Customer access token. See more in the 'Authentication' topic of this section.