Batch Processing Using API

To process a batch of transactions together, you will need to write a script or program that loops through each transaction and submits the relevant API request.

Steps

1. Compile a list of the transactions to be actioned and the required details for each transaction (e.g. transaction_id, phone number, email address, etc). If creating new transactions, no transaction_id is required in the request as this is created when the transaction is created.
2. Create a loop to run through each transaction and submit the API request for the transaction with the relevant transaction details. This can be developed programmatically in a script or other methods.
3. Submit an API request to generate an access token.
4. Begin looping through each transaction in the list and send the desired API request with the required transaction details for each transaction. You can choose to consume and store the response for each API request.

📘

Info:

The access token is available for 60 minutes. After 60 minutes have passed you will need to regenerate a new access token.

These actions require the API batch processing method described above to perform bulk updates:

• Initiate a transaction
• Get transaction results
• Resend a transaction

These actions have a specific API request available to perform bulk updates:

• Redact multiple transactions - this can be completed by a single API request that accepts multiple transactionId values. For details, see here.

Rate Limits

There is a limit to the number of API requests that can be submitted within a single day. See details here. Please communicate with IDVerse if you need the limit to be increased.

Protecting Against a Velocity Fraud Attack

You need to be aware of how we handle fraud velocity attacks. A fraud velocity identity verification style attack is a tactic wherein a fraudster attempts to exploit identity verification systems by making a high volume of rapid verification attempts using stolen or synthetic identities.

This means that if you perform a high volume of test cases over a short period in any environment, you run the risk that you will start to see real people or documents start to be flagged. The network sees this person and/or document as a possible fraudster and errs on the side of caution, i.e., flagging real people and documents.

💬 We Are Here to Help!

If you encounter an issue, a bug, or require assistance, please contact our support page here to find the solution. Don't forget to provide any important information on the issue.