Trustly offers a complete solution to handle legacy ACH ABA Routing Number and Account Number data that exists in your database to meet the new NACHA requirements for account tokenization and verification.

Summary

Account tokenization and verification can be done using Trustly’s Tokenize an Account to validate and or tokenize the existing merchant’s database. The primary steps of this tutorial are:

1. Collect the customers Account and Routing Number in your user interface. Pass this information to Trustly's Tokenize API endpoint.
2. Trustly tokenizes the account information. Account Tokens are unique per merchant per account.
3. If you pass the optional verifyAccount flag with a value of true, Trustly will also verify the account using our own database or a third party service.
4. Trustly returns the token and optional verification data to you via API response or batch file.
5. Update your records with the token and continue processing the transaction.

Tokenize API Endpoint

To initiate the request, pass in the following inputs:

• merchantId: A unique Trustly merchant identifier.
• account.accountNumber: This is the account number entered by the sender.
• account.routingNumber: This is the routing number entered by the sender.

You can optionally pass in more information to the request. For a full list of fields, consult the tokenize API reference.

Example Request

In this example, we use an account number of 123456576 and a routing number of 124003116. We are also requesting optional account verification and passing in optional customer information.

// POST https://{environment}.trustly.com/api/v1/accounts/tokenize?verifyAccount=true

{
  "merchantId": "1002463580",
  "account": {
    "accountNumber": "123456575",
    "routingNumber": "124003116",
    "type": 1
  }
}

Responses

As part of the response data, Trustly will echo back the information submitted and add the following fields:

• token: The Account Token
• verification.verified: true if the account is verified; false otherwise.
• verification.type: Will always be 3 (Database) in this use case.
• verification.score: This will be a score between 0 and 10. Score definitions can be found in the API Reference.
• verification.thirdPartyScore: If a third party was used as part of the verification, this property will be returned and have a value between 0 and 999. Third Party Score definitions can be found below Verification Score Values.
• verification.verificationDate: The date and time the verification was completed or updated.

Example Response

{
  "account": {
    "type": 1,
    "accountNumber": "123456575",
    "routingNumber": "124003116",
    "verification": {
      "verified": false,
      "type": 3,
      "score": 4,
      "thirdPartyScore": 400,
      "verificationDate": 1556740304129
    },
    "token": "K11612346575"
  }
}

Testing

The following table lists inputs and expected results that can be used for testing.

Note: All test values for Account Number and Routing Number will be 9-digit-integers.

FCRA Verification Third Party Score Values

The table below maps Trustly Verification thirdParty values to a related score value.

Non-FCRA Verification Score Values

The table below maps Trustly non-FCRA Verification score values to a related verified value.

Error Handling

The following table lists expected errors and suggested actions that are associated with this product. For more information on Error Handling, consult the Errors .