> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fastpaybrasil.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Update customer

> Updates an existing customer. Document ID and type cannot be changed after creation.



## OpenAPI

````yaml /api-reference/openapi.yaml put /v1/customers/{id}
openapi: 3.0.0
info:
  title: FastPay API
  version: 1.0.0
  description: >-
    API for creating and managing payment charges.


    ## Authentication


    This API uses **Basic Authentication** for direct API access, such as
    creating charges.

    Use your API key as the username and an empty string as password.

    The header should be formatted as:


    `Authorization: Basic {base64(apiKey:)}`.


    For example:


    ```

    Authorization: Basic YWxleG91dG9uOiIi

    ```


    ## Webhooks


    FastPay sends webhooks to notify your application about charge status
    changes in real-time.

    Webhooks are sent via HTTP POST requests to your configured webhook
    endpoints.


    ### Webhook Events


    The following webhook events are available for charges:


    - `charge.created` - Sent when a new charge is created

    - `charge.pending` - Sent when a charge is pending payment

    - `charge.paid` - Sent when a charge is successfully paid

    - `charge.updated` - Sent when a charge is updated


    ### Webhook Payload Structure


    All webhook payloads follow this structure:


    ```json

    {
      "id": "webhook_event_id",
      "event": "charge.paid",
      "data": {
        // Complete charge object
      }
    }

    ```


    ### Webhook Delivery


    - Webhooks are sent via HTTP POST requests

    - Content-Type: `application/json`

    - Retry logic is implemented for failed deliveries

    - Webhook events are stored in the database for audit purposes

    - Delivery logs are maintained for debugging and monitoring


    ### Webhook Security


    - Webhooks are sent to pre-configured endpoints

    - Endpoints can be enabled/disabled per merchant

    - Event filtering is supported (only receive specific events)

    - Failed deliveries are retried with exponential backoff
servers:
  - url: https://api-global.fastpaybrasil.com
    description: Produção e Sandbox (diferenciados pela API key)
security: []
paths:
  /v1/customers/{id}:
    put:
      tags:
        - Customers
      summary: Update customer
      description: >-
        Updates an existing customer. Document ID and type cannot be changed
        after creation.
      parameters:
        - name: id
          in: path
          required: true
          description: Unique customer identifier
          schema:
            type: string
          example: 2RhQg9M7ZCg3X3nMb9W1kX8Q
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UpdateCustomer'
      responses:
        '200':
          description: Customer successfully updated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Customer'
        '401':
          description: Unauthorized - invalid credentials
          content:
            application/json:
              schema:
                type: object
                properties:
                  statusCode:
                    type: integer
                    example: 401
                  message:
                    type: string
                    example: Unauthorized
        '404':
          description: Customer not found
          content:
            application/json:
              schema:
                type: object
                properties:
                  statusCode:
                    type: integer
                    example: 404
                  message:
                    type: string
                    example: Customer not found
      security:
        - basic: []
components:
  schemas:
    UpdateCustomer:
      type: object
      properties:
        name:
          type: string
          description: Customer's full name
          example: John Doe Updated
        email:
          type: string
          format: email
          description: Customer's email address
          example: john.doe.updated@example.com
        phoneNumber:
          type: string
          description: Customer's phone number
          example: '+5511888888888'
    Customer:
      type: object
      properties:
        id:
          type: string
          description: Unique customer identifier
          example: 2RhQg9M7ZCg3X3nMb9W1kX8Q
        gatewayId:
          type: string
          description: Gateway identifier
          example: 2RhQg9M7ZCg3X3nMb9W1kX8Q
        name:
          type: string
          description: Customer's full name
          example: John Doe
        email:
          type: string
          format: email
          description: Customer's email address
          example: john.doe@example.com
        documentId:
          type: string
          nullable: true
          description: Identification document number
          example: '12345678900'
        documentType:
          type: string
          nullable: true
          description: Type of document
          example: cpf
        phoneNumber:
          type: string
          nullable: true
          description: Customer's phone number
          example: '+5511999999999'
        createdAt:
          type: string
          format: date-time
          description: Creation timestamp
          example: '2024-01-15T10:30:00.000Z'
        updatedAt:
          type: string
          format: date-time
          description: Last update timestamp
          example: '2024-01-15T10:30:00.000Z'
  securitySchemes:
    basic:
      type: http
      scheme: basic
      description: |-
        HTTP Basic authentication. Use your secret key as the
        username and an empty string as password. The API key
        should be base64 encoded in the format 'username:' when
        sending the Authorization header.

````