Get transaction verifications

API Library Usage

var transactionData = await client.fetchTransaction(transactionTokens)

$transactionData = $client->fetchTransaction($transactionTokens);

transaction_data = client.fetch_transaction(transaction_tokens)

transaction_data = client.fetch_transaction(transaction_tokens)

Transaction transactionData = client.fetchTransaction(Tokens tokens);

transactionData, err := client.FetchTransaction(transactionTokens)

Response Values

For a detailed explanation of the data contained within the payload, expand the sample 200 response below or review the linked resources.

• id: Transaction ID
• flags: Transaction Flags
• action: Decision based on Action Maps
• fields, value, confidence and sources: Transaction Fields
• customer_uid: Customer UID Best Practices
• images: URL links to captured images are not available in the payload by default. Reach out to [email protected] to discuss if this is needed for your workflow.
• duplicates: Duplicate Transactions
• dashboard_url: Link to the Transaction Report in the dashboard
• action_map_results: The Action Map used to determine the action broken down by condition and condition_triggered results.
• session_metadata: Session Information as determined by the user's device and ISP is not included in the payload by default. Please reach out to [email protected] to discuss if needed.

📘

Do we need to rely on Berbix to make the "action" decision?

By fetching the transaction metadata, you are able to consume the flags and fields associated with a transaction to create custom rules and decisions on your end.

With that said, we strongly recommend that you consume and rely on the action field for making business decisions. Berbix Action Maps are specifically built for this purpose, and by leveraging this tool, you can adjust business logic without any code changes on your end.