Overview

The Customer Name Change API provides customers with a seamless experience when requesting a name change due to a legal event such as marriage, divorce, court order, etc.

Prior to this feature, name-change requests required customers to provide the following confidential documents to both the Partner and to Green Dot:

• Driver’s License or State ID
• Marriage/Divorce Certificate (if applicable)
• Certified court order for legal name change

With this feature, customers provide the information only once under a secure, controlled process.

By design, the API operates under two Customer ID Program (CIP) processes:

• BaaS Partner Managed CIP
• Green Dot Managed CIP

Following is a description of the BaaS Partner Managed CIP process.

Note: The Green Dot Managed CIP is still under development and will be available in a future release.

BaaS Partner Managed CIP Flow

How It Works

1. The customer sends the Partner a name-change request due to a legal event (marriage, divorce, legal name change, etc.).
2. The Partner requests the supporting legal documents (marriage certificate, divorce certificate, certified court order for name change).
3. The customer provides the requested documents.
4. The Partner validates the documents (CIP + OFAC) and approves the name-change request.
   NOTE: Per the BSA (Bank Secrecy Act 31 CFR 1010.100), customer name-change records should be maintained for at least five years.
5. The Partner sends the Name Change API request to BaaS endpoint.
6. BaaS Core performs the following:
   1. Updates the database with the new name.
   2. Sends a Publish Notification to the Partner confirming a successful name change.
   3. Issues new cards automatically.
   4. Calls CRM to create a case for documenting the name change.

Customer Name Change API Endpoints

Update User Name

This API updates the user's first, middle, and last names.

NOTE: The user's information must be encrypted. This endpoint is intended only to change the user's first, middle, and last names following a legal name change.

API Call Structure

PUT /accounts/{accountIdentifier}/users/{userIdentifier}/name)

Sample Partner User Name Change Request - Decrypted View

{
    "ProfileData": {
	"FirstName": "Happy",
	"LastName": "Lucky",
	"MiddleName": "Go"
    }
}

Sample Partner User Name Change Request - Encrypted View

{
    "encryptedUserData": {
        "version": "string",
        "ephemeralPublicKey": "string",
        "publicKeyHash": "string",
        "data": "string"
    }
}

Partner Request Parameters

• firstName -- Required. The customer’s current name as shown on documents provided for the name-change request.
• middleName - Optional. The customer’s middle name as shown on documents provided for the name-change request.
• lastName - Required. The customer’s last name as shown on documents provided for the name-change request.

Response Body

{
    "responseHeader": {
	"responseId": "cfd06987-47cd-4924-b3e6-367cb8cdb6e6",
	"statusCode": 0,
	"subStatusCode": 0,
	"message": "Success"
    }
}