The Process
Please reach out to your SVB relationship team to get started. The typical implementation involves the following steps:
- Once request is received, the SVB team will set the customer up with an equivalent ACH v2 environment in the test environment
- The customer can have both environments active at the same time (i.e. v1 and v2 environments), so that parallel testing can occur
- Once satisfied with testing of the v2 integration, the SVB team will create a production environment for ACH v2
- With production as well, the customer can have their existing v1 production environment active at the same time as the v2 production environment
- Once confirmed that the ACH v2 integration is working as desired in production, request the SVB team to disable the v1 environments
Authentication
ACH v2 leverages SVB's strategic OAuth 2.0 implementation. This authentication framework is incorporated into all of the latest versions of SVB APIs, so that customers have one mechanism to obtain a token that will allow them to take any action across ACH, VCN, Wires, and Webhooks APIs. Please see the documentation here
ACH v2
Version 2 of the ACH API is very similar to version 1, but there are some key differences. It's important to review the full set of documentation (including the Postman Collection that will help show Auth and ACH creation) here
For simplicity please also see exact field differences in the table below:
Revised ACH API Field Name | Current ACH API Field Name | NACHA Field Name |
---|---|---|
svb_account_number |
account_number |
N/A |
addenda | addenda | Addenda |
amount | amount | Amount |
company_entry_description | company_entry_description | Company entry description |
provider_id | counterparty_id | N/A |
currency | currency | N/A |
direction | direction | Service class code |
effective_entry_date | effective_date | Effective entry date |
identification_number | memo | Identification number |
additional_information | metadata | N/A |
receiver_account_number | receiver_account_number | DFI account number |
receiver_account_type | receiver_account_type | Transaction Code |
receiver_name | receiver_name | Receiving company name |
receiver_routing_number | receiver_routing_number | Receiving DFI identification |
sec_code | sec_code | Standard entry class |
settlement_priority | service | N/A |
Webhooks
Finally, ACH v2 works with our new Webhooks API as well. Please review the documentation here
Other than differences in the schema, one key thing to be aware of for ACH webhook events, is that v2 now has a "Processed" status in between "Processing" and "Succeeded/Failed". This status specifically lets the user know that SVB has accepted the request and sent the ACH transaction to the receiving bank.