Use the Create Account endpoint to create an account for a new customer. You can use this endpoint for personalized, instant issue, and secondary products.
This endpoint runs CIP if you are using Galileo's integrated CIP process. In contrast with the Start Enrollment endpoint, Create Account creates a customer record and at the same time creates an account. Depending on product settings, it also creates a card and loads funds onto it.
Consult the Creating an Account procedure for instructions on using this endpoint, and consult the Customer ID Verification guide for how to use this endpoint with Galileo's integrated CIP solution. The instructions include a flowchart to illustrate how Create Account works in the Galileo system. Also see Create Account vs Add Account in the About Accounts guide.
Note
You can receive PCI-sensitive information only if your provider parameters permit it.
Duplicate use of customer ID
Galileo can configure your product parameters to allow or disallow the duplicate use of customer IDs such as SSNs across your programs. (If one of your prospective customers already has a product with another Galileo partner, no duplicate is detected.)
If your program parameters disallow duplicate use of customer IDs, during the Create Account operation Galileo checks enrollment data across your programs to confirm that there are no accounts in application submitted (V), canceled without refund (Z), or active (N) status with the same ID. If no account is found in these statuses, the enrollment is allowed.
CIP response
If you are using Galileo's integrated CIP solution, the Create Account response includes the verdict. Consult Create Account and Create Virtual Account Process in the Customer ID Verification (CIP/KYC) guide for more information.
Test names in the CV environment
In the CV environment only, you can use specific names with the Create Account endpoint to trigger different CIP responses. For the firstName, middleName, and lastName parameters, use these values:
John F Smith— Triggers a CIP failure (F)John R Smith— Triggers a CIP refer (R)John P Smith— Triggers a CIP pass (P)
Do not use these test names in Production.
Note
If this endpoint returns a status code that does not match a status code that is specific to this endpoint, it may be an enrollment status code. See Enrollment Statuses for more information.
See Global Response Statuses for status codes that are common across endpoints.
The table below lists status codes that apply to this specific endpoint.
| Status Code | Code Description |
|---|---|
| 407-03 | Invalid instant issue card. An attempt was made to use an instant-issue card that has already been sold. Retry with an unissued instant-issue card number. |
| 407-04 | Load amount outside of load limits. Too much money is being loaded. Retry with an appropriate amount in loadAmount, or check your maxLimit and minLimit settings. |
| 407-05 | Could not create account. Contact Galileo for troubleshooting.` |
| 407-06 | Could not load card. Contact Galileo for troubleshooting. |
| 407-07 | Primary account is invalid. The account number in primaryAccount cannot be an instant-issue card. |
| 407-08 | Invalid real-time funding account. fundingAccountNo must contain an RTF funding account. |
| 407-09 | Maximum number of secondary accounts exceeded. Product settings do not permit this many secondary accounts per primary account. Set SECLM on the secondary account to a higher number. |
| 407-10 | ID type 2 is required as main ID for running CIP. Product settings require idType: 2 (SSN/SIN) to run Galileo's integrated customer ID verification. Pass a SSN in id. Controlled by IDSSN. |
| 407-11 | Account created, ID validation failed. Customer's personal info has failed the ID check. Take action depending on the result in the response: F — Fail. Take no action: the customer does not qualify for an account.R — Refer. Depending on your arrangements with Galileo, request valid documents from the customer or wait for Galileo's third-party CIP to complete. |
| 407-12 | An application with the same ID has already been submitted. Duplicate SSNs were used for enrollment. Follow your business plan for this outcome. Controlled by VLDLV. |
| 407-13 | Application successfully started and CIP run. The cipStatus parameter was set to 1, the application was successfully started, and CIP was run. An account was not created. Take action depending on the result in the response:P — Pass. Contact Galileo for instructions on creating the account. Do not run Create Account again.F — Fail. Take no action: the customer does not qualify for an account.R — Refer. Depending on your arrangement with Galileo, request valid documents from the customer or wait for Galileo's third-party CIP to complete. |
| 407-14 | Success -- partial limit violation. Only the amount permitted by project settings was loaded. |
| 407-15 | Success -- delayed payment. The account was created but funds were not loaded onto the card because of limit violations. An attempt will be made tomorrow to load the card. |
| 407-16 | Card is marked as fraudulent. Used for instant-issue cards which have been swiped before issuance. Retry with another instant-issue card. |
| 407-17 | Card not allocated to your store for issuance. The location does not match the location that this batch of cards was created for. Change the location on the account or retry with another instant-issue account number. |
| 407-18 | Specified load from account number is invalid. The loadFromAccountNo parameter contained an account number that does not exist in the Galileo system. Retry with valid account number. |
| 407-19 | A load was attempted for a non-positive amount. A negative load amount was passed. Retry with a positive amount. |
| 407-20 | The prodId for the secondary account is not allowed. Product parameters do not permit the prodId to be a secondary account for the account in primaryAccount. Check SECP on the primary account. |