---
title: "Update a PAD by its ID."
method: PUT
path: "/customers/{customerId}/bank-accounts/{bankAccountId}/pads/{padId}"
tags: ["Customer"]
---

# Update a PAD by its ID.

`PUT /customers/{customerId}/bank-accounts/{bankAccountId}/pads/{padId}`

## Request

- Base URL: `https://api.helcim.com/v2`
- URL: `https://api.helcim.com/v2/customers/{customerId}/bank-accounts/{bankAccountId}/pads/{padId}`
- Auth: API key in header `api-token`

## Path parameters

- `customerId` number, required
- `bankAccountId` number, required
- `padId` number, required

## Request body

- Req2
  - `accepted` 0 | 1: Whether the PAD was accepted or not: * `0` - Unaccepted * `1` - Accepted If the PAD is set to accepted and the PAD is active, a side effect of updating the associated bank account to ready will also happen. If the PAD was set to unaccepted, it will unready the bank account.
  - `ipAddress` string
  - `type` 1 | 2: The type of the bank account: * `1` - Personal * `2` - Business
  - `status` 1 | 2: The status of the PAD: * `1` - Active * `2` - Inactive If the PAD is set to active and the PAD is accepted, a side effect of updating the associated bank account to ready will also happen. If the PAD was unaccepted, it will unready the bank account. Note: there can only be 1 active PAD per bank account.

## Response `200`

Successfully updated PAD.

## Other responses

- `400`: Invalid request.
- `403`: User does not have valid permissions.
- `500`: Unexpected internal error.

---

[API](https://skmtc.dev/helcim/apis/the-helcim-api.md) - [All operations](https://skmtc.dev/helcim/apis/the-helcim-api/llms.txt) - [OpenAPI document](https://skmtc.dev/helcim/apis/the-helcim-api/revisions/95aef350fef4?raw)