Creating an Account

⚠️

New process

This guide provides instructions for using Create Account when the integrated ID verification process is the Identity Verification Service (IVS), which replaced the previous integration solution in June 2026.

If you are using the SoFi Tech Solutions legacy CIP process, refer to the <a href="doc:creating-an-account-with-legacy-cip target="_blank">Creating an Account with Legacy CIP guide.

This guide describes the procedure for creating a new customer account using the Create Account endpoint. With these endpoints you can optionally issue a card and deposit funds into the account at the same time that you create the new account.

📘

Note

When creating an account for a new customer you must perform Customer ID Verification. You should also read the About Accounts guide to familiarize yourself with SoFi Tech Solutions' account structure and conventions.

Follow this procedure to:

• Onboard a new customer for a physical card.
• Onboard a new customer for a virtual card.
• Create a secondary account for a different customer than the primary account holder, such as a spouse or child.

Do not follow this procedure to:

• Add a secondary account to an existing customer; instead, see the Adding an Account guide.
• Add an overdraft account; instead, see the Creating an Overdraft Account guide.
• Create an instant-issue card; instead, see Setup for Instant Issue.
• Create an account for a Digital First account, where you provide a digital version of the card for customers to use while the physical card arrives; instead, consult Digital First cards in the Choose a Card Strategy guide.

Result of calling Create Account

When Create Account has run successfully, these new items are created in the system. See New account creation in the About Accounts guide for details.

• Customer record — Contains the customer's personal data such as address, date of birth, and contact information.
• Account record — Contains general account information.
• Card record (for card products) — Contains card information.

Parameters

This table contains the parameters that are typically populated for the Create Account endpoint when creating a standard account (with or without a card). See the Create Account reference for details. Parameters that are omitted from this table are strictly optional.

📘

Note

Parameters marked with § might be required for Mexican programs when SoFi Tech Solutions is the BIN sponsor.

Account-creation workflow

Consult these sections for the Create Account workflows: the first when using a standalone identity-verification system and the second when using SoFi Tech Solutions' integrated IVS process.

📘

Note

Call the Create Account endpoint only once per customer when onboarding. Because these endpoints create a customer record, it is important that only one record be created per customer.

Create Account without integrated ID verification

This section describes the logical progression of the Create Account endpoint and subsequent backend processes when using a standalone customer ID validation solution, either SoFi Tech Solutions' IVS or a third-party solution. The actual sequence of events in the system may vary.

📘

Note

The Account Events messages are sent to you according to the arrangements you have made with SoFi Tech Solutions.

1. Retrieve customer information from your web page or mobile app.
2. Send the customer information to your customer ID validation provider.
3. When customer ID validation is successful, populate the Create Account request and send.
4. The system performs a number of preliminary checks. Failures return these status codes:
   • 407-04 — Load amount outside of load limits.
   • 407-12 — An application with the same ID has already been submitted.
   • 407-18 — Specified load from account number is invalid
5. The system creates an account with status: W (Waiting to Be Processed). If the account cannot be created the endpoint returns status_code: 407-05.
6. According to product settings, the system creates a card entry in the database and deposits funds into the account.
   • The card-related fields (card_number [PAN], expiry_date, and card_security_code [CVV] are masked or empty unless you are PCI compliant.
   • If depositing funds is not successful, these status codes are returned:
     • 407-14 — Success -- partial limit violation
     • 407-15 — Success -- delayed payment
7. If all processes have been successful, the system sends two messages:
   • Endpoint response with status_code: 0 (successful)
   • Account Events webhook message CAPP: app_completed.
8. The system runs an account setup process to determine whether other criteria for the account have been fulfilled, according to product settings. When all criteria are fulfilled, the system checks the XAACT product parameter for how to set the account status:
   • First character — Account active/inactive (Y/N)
   • Second character — Account status
   • Third character — Card status (if any)

For example, if the product is a card account, and XAACT is YNX, then when account setup is completed these are the settings:

• Account active: Y
• Account status: N (active)
• Card status: X (set to emboss)

See Lifecycle of a card in Setting Up a Card Program for the next steps when the account has a card.

Create Account using IVS integration

This section describes the logical progression of the Create Account endpoint and subsequent backend processes when using SoFi Tech Solutions' integrated IVS. The actual sequence of events in the system may vary.

📘

Note

The Account Events messages are sent to you according to the arrangements you have made with SoFi Tech Solutions.

1. Collect customer information from your web page or mobile app.
   • SoFi Tech Solutions recommends that you make primaryPhone required on your interface for IVS integration. This number is used in combination with mobilePhoneCountryCode to send an SMS message for the customer to upload additional documentation.
2. Populate the Create Account request and send.
3. The system performs a number of preliminary checks. Failures return these status codes:
   • 407-04 — Load amount outside of load limits.
   • 407-12 — An application with the same ID has already been submitted.
   • 407-18 — Specified load from account number is invalid
4. The system sends the customer information to IVS.
   • If there is a technical error while contacting IVS or receiving its response, the endpoint returns status_code: 407-05. No account is created.
5. The system creates the customer account with status: W (Waiting to Be Processed).
6. According to product settings, the system creates a card entry in the database and deposits funds into the account.
   • The card-related fields (card_number [PAN], expiry_date, and card_security_code [CVV] are masked or empty unless you are PCI compliant.
   • If depositing funds is not successful, these status codes are returned:
     • 407-14 — Success -- partial limit violation
     • 407-15 — Success -- delayed payment
7. The system evaluates the response from IVS:
   • If it reports success (Pass) the system sends you two messages:
     • Endpoint response with status_code: 0 (Success).
       • The cip array contains the result (Pass) plus entity_id and customer_id, which both contain the app ID.
     • Account Events webhook message CAPP: app_completed.
   • If it reports a result that is not Pass, the system sends these messages:
     • Endpoint response with status_code: 407-11 (Account created, ID Validation failed).
       • Even with a non-pass result, the endpoint still creates the account and card, so the card and account-related fields such as pmt_ref_no and card_id are present in the response.
       • The cip array contains the results plus entity_id and customer_id, which both contain the app ID.
         • Fail — The customer or business is on a watch list or is unlikely to be a real person or business and therefore does not qualify for an account. The account will not be activated.
         • In Progress — Verification is still in progress. The customer or business is likely real, because there was a partial match for the personal or business information and identifier. Additional steps (such as document upload via SMS link) may be triggered asynchronously; they are not returned in the endpoint response.
         • Refer — Verification was referred for manual review. The account is created but will not activate until the review has completed.
     • Account Events webhook message BFID: failed_id.
8. The system launches an account setup process, which verifies whether all criteria for account creation have been fulfilled.
   • If IVS was successful, the system moves the account to status: P (passed ID verification).
   • If IVS was not successful, SoFi Tech Solutions moves the account to the status in TIDST (default: F).
9. For accounts that pass verification, SoFi Tech Solutions checks the XAACT product parameter for how to set the account status:
   • First character — Account active/inactive (Y/N)
   • Second character — Account status
   • Third character — Card status (if any)

For example, if the product is a card account, and XAACT is YNX, then when account setup is completed these are the settings:

• Account active: Y
• Account status: N (normal, active)
• Card status: X (set to emboss)

See Lifecycle of a card in Setting Up a Card Program for the next steps when the account has a card.

📘

Note

The account setup process is a cron job with an interval between 5 and 30 minutes, according to your product settings. For this reason, you will receive the CAPP: app_completed event webhook message and the API response before the account is usable.

• See the Activating a Card guide for more information.
• To see account status, call an endpoint such as Get Account Overview or see Retrieving account information in the About Accounts guide for a list of endpoints that retrieve the account status.

View the new account

Use the Get Account Cards endpoint to retrieve account status and other information. Consult Retrieving account information in the About Accounts guide for a list of endpoints and the specific account information they retrieve.