Call this endpoint to assign and activate the card to an account.

Also, you can activate several cards for the same account in case o enterprise users creation. This endpoint supports two modes of operation: 1. If `customer_id` is provided in the request body, it will associate the new card with the existing customer. 2. If `customer` object is provided instead, a new customer will be created using that information and the card will be linked to it. Accounts with a Composite Balance can also use this endpoint to register and activate their accounts. You can learn more about these accounts here: Composite Balance #### Example 1: Only `customer_id` provided ```json { "customer_id": "12345678", "card_identifier": "CARD-001", "reference_batch": "7e4b85e27c4610824900af48f340394d" } ``` #### Example 2: When using **Composite Balance (only for Credit Engine)**. Just in case of a **Composite Balance**, a param **balance** is required. It will be an object with the id of the balance: ```json { "pin": "1234", "card_identifier": "CARD001", "reference_batch": "7e4b85e27c4610824900af48f340394d", "device_id": "2fc54683d5fad405360419f720457ccbcf9bacac414f6296f846e2e4fad99d47", "customer_id": "85", "balance": { "id": 10249 } } ``` #### Successful response (applies to all cases) ```json { "text": "Success", "timestamp": "2024-11-15T14:32:18.123Z", "endpoint": "debit/v1/activateCardForCustomer", "error": {}, "payload": { "card_id": "card_987654321", "customer_id": "12345678", "status": "activated" } } ``` #### Here some error responses, for instance: > **Note**: Empty error in successful requests ```json { "text": "Error", "timestamp": "2025-11-18T11:50:57.960232171-06:00", "endpoint": "/debit/v1/activateCardForCustomer", "error": { "code": 7000, "text": "Server error", "hints": [ "Please contact the customer care", "rfc:invalid" ] } } ``` #### The following are listed errors that may be occurring due to incorrect data being sent or any other problems that may arise. ##### Error with the reference batch. A reference batch does not exist. ```json "error": { "code": 4400, "hints": [ "Bad parameters request, please refer the documentation", "Mismatch in reference batch." ] } ``` ##### Error with card identifier. A card identifier does not exist. ```json "error": { "code": 4400, "hints": [ "Bad parameters request, please refer the documentation", "Mismatch in card batch." ] } ``` #### Error in communication with the card service provider. ```json "error": { "code": 5001, "text": "Wrong parameters" } ``` #### Invalid RFC for the data submitted or existing in the customer list. ```json "error": { "code": 7000, "text": "Server error", "hints": [ "Please contact the customer care", "rfc:invalid" ] } ``` #### Invalid email. ```json "error": { "code": 4400, "hints": [ "Customer whith this email is already created" ] } ``` #### First name. ```json "error": { "code": 4400, "hints": [ "Customer first name is required and can't be empty" ] } ``` #### For a single physical card, and it is already activated for the user. ```json "error": { "code": 4400, "hints": [ "This customer already have a physical card" ] } ``` #### Lastname. ```json "error": { "code": 4400, "hints": [ "Customer first name is required and can't be empty" ] } ``` #### Empty reference batch. ```json "error": { "code": 4400, "hints": [ "Reference batch can't be empty" ] } ``` #### Empty card identifier. ```json "error": { "code": 4400, "hints": [ "Card identifier can't be empty" ] } ``` #### There is no card for that card identifier. ```json "error": { "code": 4400, "hints": [ "Missing card to provided batch reference and card identifier" ] } ``` #### PIN validations. ```json "error": { "code": 4400, "hints": [ "Invalid pin. Pin should have only digits" ] } "error": { "code": 4400, "hints": [ "Invalid pin. Pin should have 4 digits" ] } ``` #### Card already activated. ```json "error": { "code": 4433, "hints": [ "Card has already been activated" ] } ```