---
title: "Authorize Bank Transactions"
method: POST
path: "/v1/banking/bank_accounts/{bank_account_id}/authorize"
tags: ["Bank account"]
---

# Authorize Bank Transactions

`POST /v1/banking/bank_accounts/{bank_account_id}/authorize`

## Request

- Base URL: `https://api.cardda.com`
- URL: `https://api.cardda.com/v1/banking/bank_accounts/{bank_account_id}/authorize`
- Auth: HTTP bearer

Authorize bank transactions of a bank account

## Path parameters

- `bank_account_id` string, required

## Parameters

- `#/paths/~1v1~1banking~1bank_keys/get/parameters/0` (unresolved $ref)

## Request body

- object
  - `bank_key_id` string, required: The id of the bank key to be used.
  - `authorization_method` 'token' | 'itau_pass' | 'digipass' | 'santander_pass' | 'device', nullable: Authorization method to be used. In Mexican operation this field is not required.
  - `token` string
  - `device_id` string: Device to be used for authorization
  - `transactions_ids` string[]

## Response `200`

The authorization is being processed, and since that process is async the response is an empty object

- object

## Other responses

- `400`: The authorization was called with authorization method set to token, but only one transaction was in the queue which is not allowed. There must be 2 or more to use that method
- `401`: Unauthorized
- `402`: Payment required — the account does not have enough balance to authorize the selected transactions.
- `404`: Not found — there are no transactions eligible to authorize for this account.
- `409`: The authorization was called while there are some transactions pending to be enqueued
- `422`: The authorization method has a non valid value

---

[API](https://skmtc.dev/cardda/apis/banking-api.md) - [All operations](https://skmtc.dev/cardda/apis/banking-api/llms.txt) - [OpenAPI document](https://skmtc.dev/cardda/apis/banking-api/revisions/ff1aeb3fda8b?raw)