Skip to main content

Registration And Access

Registration and Access covers online banking registration, self-service password reset (OTP to a chosen contact method), and administrative user unlock.

End-user benefits

  • Register for digital banking through partner apps with validation aligned to Candescent enrollment.
  • Reset password using an OTP sent to SMS or voice (after listing contact methods — see Contact Info).
  • Unlock a locked user without forcing a full password-reset flow when permitted.

Integration capabilities

  • Registering new customers with comprehensive validation and error handling
  • Implementing self-service password reset with OTP delivery
  • Supporting administrative user unlock functionality

Customer Registration

The Registration API provides third-party application developers with access to the same registration process used in Candescent Digital Banking. No scope required.

Common Use Cases:

  • Online banking vendors registering users for additional offerings after account opening
  • Mobile banking vendors providing products to FIs using Candescent Digital Banking
  • Application developers extending Candescent Digital Banking functionality

Required Personal Data:

  • First name, Last name, Middle name (optional)
  • Social Security Number (9 digits)
  • Date of Birth (yyyy-mm-dd format)
  • Address: Street, City, State, Zip Code, Country
  • Phone Number (10 digits)
  • Email Address
  • Mother's Maiden Name

Username Policy:

  • Default: 8-20 characters (configurable: min 6, max 20)
  • Cannot be only numbers, can be all letters
  • Allowed special characters: @$*_-=.!~
  • No spaces allowed

Password Policy:

  • Length: 6-32 characters (configurable within limits)
  • Must contain characters from at least 2 of: Letters, Numbers, Special characters
  • No spaces allowed
  • Cannot be a substring of the username

Reset Password (Self-Service)

The Reset Password API enables customers to reset their password using a one-time passcode sent to their preferred contact method.

  • Verify that a customer exists at a specified financial institution
  • Provide a list of contact methods (SMS, Voice, Email) for the customer
  • Send a one-time passcode to the customer's desired contact method

Reset Password Flow:

  1. Retrieve Contact Methods: GET /ux-users/v1/customers/\{customerId\}/contactMethods
    • Returns available destinations (SMS, Voice, Email) with masked contact info
    • See endpoint documentation for response example
  2. Customer Selects Destination: Choose where to receive the OTP
  3. Initiate Reset: PUT /ux-users/v1/customers/\{customerId\}:resetPassword
    • Send destinationId in the request body
    • OTP is sent to the selected contact method

Scopes

Reset Password and Unlock User

ScopeDescription
institution-users:readList contact methods for the customer
institution-users:writeTrigger OTP delivery for password reset

Error codes

Registration

CodeMessageHTTP Status Code
20006Invalid input (member number, channel TPV_API, name length, SSN, etc.)400
26201LoginID is already taken400
26214Too many destinations passed400
26330Registration already in progress (duplicate request)409
26331User is already registered409
26340Could not create record in database400
220001SSN is not 9 digits400
220002First name exceeds 39 characters400
220003Last name exceeds 39 characters400
220005Middle name exceeds 39 characters400
220006Email exceeds 64 characters400
220007Postal code not found400
220008City not found400
220009State not found or invalid length (US: 2 chars)400
220010Street/Address1 missing or exceeds 128 characters400
220011Country not found400
220012Mother's maiden name missing or exceeds 128 characters400
220013Invalid date of birth format400
220014Phone number is missing400
220015Invalid LoginID (6–256 chars, allowed @$*_-=.!~, no spaces)400
220016LoginID cannot match member number400
220018Invalid password400
220019Login must be within preconfigured range400

Reset Password and Unlock User

CodeMessageHTTP Status Code
UXU_10001Invalid JWT token400
UXU_10002Required role not present in JWT token403
UXU_10003JWT token has expired400
UXU_10004JWT token does not contain institution id400
UXU_10005Required Authorization header is missing400
UXU_10006Required Correlation Id header is missing400
UXU_10007Correlation Id is not a GUID400
UXU_10008Invalid IP address in the header400
UXU_10009Invalid Authorization in the header400
UXU_10010JWT token does not contain institution customers id400
UXU_10011JWT token institution customers id not matching path param400
UXU_10012Invalid path param400
UXU_10013Invalid path400
UXU_10014Invalid query param400
UXU_13001Combined firstname, middleName, lastname exceeds 39 chars400
UXU_13002Invalid user password400
UXU_13003Login Id is already taken400
UXU_13004You are already a registered user400
UXU_13005Invalid Date Format400
UXU_13006Soft failure, contact institution400
UXU_13007Login id and Member number can't be the same400
UXU_13008Member number/username is already registered409
UXU_13009Error while registering user400
UXU_30001Error interacting with the service503
UXU_30002Error interacting with the external service503
UXU_88888No entitled customers found404
UXU_88889Contact method Id not found400
UXU_88890Institution customer id not found400
UXU_88891Host phone postal address not found400
UXU_99998Internal server error500
UXU_99999Cannot handle this request — check URL, body and parameters400

Endpoints