Autoverified Deposits

Autoverified Auth Deposits
Note: Our free self-service API does not include auth deposits, only instant account verification. Contact us if you’d like to learn more about auth deposits.
Since not all institutions make full instant auth information available through a connection, Quovo offers an alternative workflow to help you validate an account and routing number combination in another way. With Autoverified Auth Deposits, Quovo will send and verify microdeposits. These “auth deposits” handle validation of an account number and routing number combination while removing the need for your users to come back after the deposits have hit their accounts, providing you with an easy solution to verify a user’s account information. 
After initiating the Auth Deposit process, Quovo will make two small deposits to the target bank account. After the   deposits   are successfully sent, Quovo will leverage its full aggregation capabilities to automatically verify the deposits by checking the transaction history of the account. This creates a smoother account verification workflow by eliminating the need for your end user to come back and verify the deposit amounts.
Remember that even though auth deposits represent an account auth use case, they use a full aggregation sync to auto-verify the deposits, since we must pull transactions to see if a deposit has hit the account.

Requesting an Auth Deposit

To begin the auth deposit process, create a connection and initiate a fullsync on it. Check the available accounts by sending a GET call to https://api.quovo.com/v3/connections/{connection_id}/accounts
Then, to send deposits to one (or more) of these   accounts  , send a POST request to https://api.quovo.com/v3/accounts/{account_id}/auth_deposits . You need to pass a valid   account_number   and    routing   number to successfully send an auth deposit.
curl -X POST \
    -H "Authorization: Bearer a724809d37d0a21b7e9257f45cee416f5aec61993ab4b09e" \
    -H "Content-Type: application/json" \
    -d '{"account_number": "569339485397", "routing": "306061549"}' \
With this information, we will send two small amounts to the bank account detailed above. It may take several days for the micro-deposits to travel through the ACH network and appear in the bank account’s transaction history.
Note: Only one auth deposit can be sent to an account at a time
With a full sync Quovo will update transactions every night. Once the deposits hit the account, Quovo will detect their validity by the amount and memo of the transaction—thus auto-verifying them, without additional action!
Note: in order for the verification process to work, the connection the auth deposit’s account is on needs to be in “good” status. 

Check Auth Deposit Status

Requesting an auth deposit will return a generated deposit ID in the /auth_deposits endpoint. You can use this ID to check the status of a specific auth deposit. Make a GET request and pass the deposit ID to https://api.quovo.com/v3/auth_deposits/{auth_deposit_id} .
curl -X GET \
	-H "Authorization: Bearer a724809d37d0a21b7e9257f45cee416f5aec61993ab4b09e" \
After an auth deposit is generated, it enters a sequence of statuses that track the deposits from the time they are requested to the time they are verified. The timeline of auth deposit statuses are as follows:
  • requested – the deposits have been requested by you but Quovo hasn’t sent it through the ACH network yet
  • deposit_failed – the deposits could not be sent properly. The error field in the response will contain an error code detailing why the attempt failed. You can see a full list of auth deposit error codes here
  • submitted – Quovo has successfully sent the micro-deposits through the ACH network
  • transferred – Quovo is reasonably sure the micro-deposits have hit the target account. The deposits have yet to be detected, but we are confident they will be verified soon.
  • verified – the auth deposits have been confirmed and validated
  • verification_failed – the deposits have not shown up after an extended period of time, or the user has incorrectly attempted manual verification twice
In the GET request to /auth_deposits, sending   updated_after   will return all auth deposits that have been updated after the given datetime (in ISO 8601 format). We recommend always checking your auth deposits after a certain time period. This will help you see the relevant auth deposits. 
curl -X GET \
    -H "Authorization: Bearer a724809d37d0a21b7e9257f45cee416f5aec61993ab4b09e" \
Response fields from this request will include the following   connection_id    account_id    connection_status    id  , and other details about the auth deposit.

Nongood Statuses and Auth Deposits

Because automatically verifying auth deposits requires updating an account’s transactions over the course of a few days, the account’s connection status must be “good” for this process to work. If a connection is in “good” status when a deposit is requested but falls into a “nongood” status afterwards, the auto-verification of the deposit may be delayed.
If the connection’s status is nongood and requires user action, follow the steps outlined in the connections section of this guide to restore a good status and enable auto-verification of deposits. If the connection’s status is nongood but does not require use action, wait for the issue to resolve itself.
Auth deposits are supported through Quovo Connect, our javascript widget to help users sync accounts and connections. Parameters for enabling auth deposit workflows can be found in our Connect documentation.
If you are unable to resolve a “nongood” connection status or Quovo does not cover the institution, we offer workflows for a more traditional microdeposit process. For more information about the workflow, click here.