SVB offers APIs to connect to clients' applications to initiate payments such as Wires, ACH, and FX Contracts. Clients are required to first onboard to our API Banking to use our APIs. We support clients to onboard to API Banking, Delete their registration and Update their registration.
Onboarding to API Banking
Please complete the following steps to onboard to our service.
- Please reach out to our SVB Support Partners to onboard to our API Banking.
- Provide the details mentioned in the 'Client Information for Onboarding' section below
- On completion of registration, SVB Support will provide Client ID and Secret. Please provide these details to your technology team for connecting to our API services.
- Please refer to our OAuth documentations for further details on connection between your application and our API services.
Delete Registration to API Banking
We allow our clients to delete their registration entirely. Please refer to the details mentioned in 'Client Information for Onboarding'.
- Please reach out to SVB Support Partners to delete registration to our API Banking
- On completion of the deletion, SVB Support will provide confirmation
Update Registration Details
We allow our clients to update their registration details. Please refer to the details mentioned in 'Client Information for Onboarding'
- Please reach out to SVB Support Partners to update registration details to our API Banking
- Please provide the attributes for updates
- On completion of the update, SVB Support will provide confirmation
Get Registration Details
We allow our clients to request for details of existing registration.
- Please reach out to SVB Support Partners to get their existing registration details to our API Banking.
- SVB Support will provide the details of the registration.
Client Information for Onboarding
- Please provide the following details for onboarding
| # | Information to provide | Descriptions | Update Allowed? |
|---|---|---|---|
| 1 | Client Name | Clients Entity Name | Yes |
| 2 | Debit Account | Debit Account Details. Please list all debit accounts if you want to link more than one debit account for a scope. Provide the following fields for every Debit Account: Scope, CIF, Daily Max Limit, Transactions Limit, Direction, Default, Company Capability ID, Account Name, and Sec Code. | Yes |
| 2.1 | CIF Number | Customer Number associated with the Debit Account. This information can be found on the web channel. | Yes |
| 2.2 | Scope | Scope for which API Service the client can initiate with a Debit Account. Examples: "ach", "fx", "wires" or "vcn" | Yes |
| 2.3 | Daily Max Limit |
Daily Max Limit for a given Debit Account & Scope. The cumulative limit for the day for a payment type. For Example: SVB will only process the total number of wires payments which is within the 10,000 USD limit for that day |
Yes |
| 2.4 | Transaction Limit |
Daily Transaction Limit for a given Debit Account & Scope. The limit for a single payment type. For Example: Debit Account: 3334567890 SVB will only process wires payment which is within the 5,000 USD limits |
Yes |
| 2.5 | Direction |
Direction of the payment; Debit or Credit. ACH payments we allow both Debit & Credit. For Wires & FX we allow only Debit. Please provide this value only for ACH. We allow same account with both debit or credit. Different accounts with different direction. |
Yes |
| 2.6 | Default |
Applicable only for FX & ACH. Default Account for FX Contract and ACH for each of the direction. Clients must specify any one of the Accounts as True for each direction. At the time of processing, if the user does not provide an account, then SVB will process the fx contract/ACH payment with the Account provided during registration with the value "True". |
Yes |
| 2.7 | Capability Company ID | This is the unique company id for a given Debit Account for ACH payment. Please provide this only for ACH payment and is not applicable for Wires or FX | Yes |
| 2.8 | account_name | Company name that would make it to the NACHA file for ACH payment. Please provide this only for ACH payment and is not applicable for Wires or FX | Yes |
| 2.9 | sec_code |
Standard Entry Class code, designates how the ACH transfer was authorized by the originator. ccd: Cash Concentration and Disbursement ppd: Prearranged Payment and Deposit web: Internet-Initiated Entry This field is mandatory for ACH and is not applicable for Wires or FX |
Yes |
| 3.0 | VCN Card Information | Please provide VCN card information to use VCN API. Provide only one set of VCN card information per client | Yes |
| 3.1 | rcn_id | ID of the real card that will be used to create virtual cards | Yes |
| 3.2 | rcn_alias | The alias name of a real card to use | Yes |
| 3.3 | supplier_id | ID of the supplier | Yes |
| 3.4 | template_id | ID of the pre-configured Mastercard purchase request template | Yes |
| 3.5 | aging_velocity_template_id | ID of the pre-configured Mastercard purchase request template that allows aging velocity | Yes |
| 3.6 | company_id | Company identifier on the SmartData system | Yes |
| 3.7 | max_card_amount | Maximum allowed amount to be set on a virtual card | Yes |
Notes
- If you want to provide more than one debit account please ensure to provide all details from 3.1 to 3.7 as applicable i.e. ensure to provide all details for each debit account you want to register.
Examples:
| Example 1 |
|---|
|
1.Debit Account: 3300660155 & CIF: 100003666
2.Debit Account: 3300660156 & CIF: 100003666
3. VCN Card Information
|
| Example 2 |
|---|
| 1.Debit Account: 3300660155 & CIF: 100003666
2.Debit Account: 3300660156 & CIF: 100003666
|