Skip to main content
This topic covers some of the basic error scenarios with the Associate Billing Account to User Process.

No Account Found

If the user-supplied mobile number do not match any account in the integrated B/OSS, then Storefront Gateway responds to your client with an HTTP 400 status. The response body includes a operationErrors array with the reason(s) as to what went wrong:
The response also includes a lastStepFailedAction object that repeats the previous Process step’ response, so the user re-attempt their request.

Account Already Associated

If the B/OSS returns an account that is already associated to the current User, then the Storefront Gateway responds with an HTTP 409 status. The body includes a operationErrors array with the reason(s) as to what went wrong:
Note: If the account is already associated to a separate User, then the response is similar except for the message:

Error Codes

Below is a list of potential error codes that may be returned during the execution of this Process. Note: See Common Process Error Codes.