Application Boarding Conventions
This page provides conventions for use with the Application Boarding API resource. For instructions on implementing Application Boarding API requests, see the Application Boarding implementation guide as well as the relevant endpoints' implementation guides and API reference.
'Save Data' Request Conventions
The following table shows key and value pairs accepted in the data array in a 'Save Data' request. The sets marked "Required" will ultimately be required for the application's approval in underwriting, but they are not required for a 'Save Data' request to succeed. For instructions on sending this request, see the Save Data implementation guide:
| Requirement for Application Approval |
|
|---|---|---|
|
| The legal name of the business. |
| Required | The 'Doing Business As' (DBA) name of the business. This will appear on a cardholder's statement. |
| Required | A list of URLs. |
| Required | An email address for the business. |
| Optional | The telephone number for the business. This will appear on a cardholder's statement. |
| Required | The mailing address for the business. |
| Required | The business type. Send one of the following: |
| Required | Send |
| Required | The trading status of the business. Send one of the following: |
| Required | The type of tax ID provided in the application. Send one of the following: |
| Required | The tax ID for the business. |
| Required | The U.S. state in which the business files taxes. |
| Required | The date the business was established, formatted as YYYY-MM-DD. |
| Required | The Merchant Category Code (MCC) of the business's industry. |
| Required | A detailed description of the type of clients the business sells to. |
| Required | An object containing an array of objects, the requisite form of which is determined by |
| Required | Send |
| Required | At what point the business processes a payment. Send one of the following: |
| Required | The number of days before fulfillment the business takes payment. Send one or more of the following: |
| Required | The card brands the business accepts. This should be an object of five Booleans: |
| Required | The projected annual volume of all card payments to the business. |
| Optional | The projected annual volume of ACH payments to the business. |
| Required | The projected total annual sales, including cash. |
| Required | The high ticket business to consumer (B2C) amount. |
| Required | How the order is filled. Send one of the following: |
| Required | How the order is received. This should be an object of four Booleans: |
| Required | Send |
| Optional | The name of the fulfillment center. |
| Optional | The name of the fulfillment contact. |
| Optional | The email address of the fulfillment contact. |
| Optional | The phone number of the fulfillment contact. |
| Optional | The address of the fulfillment center. |
| Optional | Send |
| Required | The 9-digit routing number of the bank receiving the money. |
| Required | The account number of the bank account receiving the money (usually 10-12 digits). |
Updated about 1 month ago