---
title: "Pay bank slip"
method: POST
path: "/v1/bankslips/pay"
tags: ["Bank slip"]
---

# Pay bank slip

`POST /v1/bankslips/pay`

In Brazil, bank slips, known as *Boleto Bancarios* or simply *Boletos* in Portuguese, are a popular payment method for various services, bills, and purchases. When a payment needs to be made, the recipient (such as a business or service provider) generates a Boleto with the necessary payment details, such as the recipent's information, the payment amount, due date, barcode, and other relevant information.
Pismo works with [BTG Pactual](https://www.btgpactual.us), [Celcoin](https://celcoin.com.br), and [Itaú](https://www.itau.com.br) to implement Boleto payments. In the future, Pismo may work with additional financial companies.
This endpoint generates the following events:
* [Authorization created](https://developers.pismo.io/events/docs/authorization-authorization-event-1) - This event contains bank slip information (beneficiary name and document number, digitable line, amount, payment date, interest/fine and discount (if any) in the `metadata` field.
* [Financial bank slip status changed](https://developers.pismo.io/events/docs/integrated-payments-bankslip-status-change-1) - Before clearing, a bank slip's status is `PAID`. After clearing, Pismo changes its status to `SETTLED`.
* [Integrated payments financial reconciliation](https://developers.pismo.io/events/docs/integrated-payments-financial-reconciliation-1)- This event is generated after the transaction has been cleared and accounts debited or credited. If `x-skip-reconciliation` is `true` or the provider is JD Consultores, this event is not generated.<br>
See [Bank slips](https://developers.pismo.io/pismo-docs/docs/bank-slips) for more information.<br>
**Important**: You need to call [Validate bank slip](https://developers.pismo.io/pismo-docs/reference/post-integrated-payments-api-v1-bankslips-validate) before calling this endpoint and pass the `external_authorization` field value if it is returned from that call here.

## Headers

- `Authorization` string, required
- `Idempotency-key` string, required

## Request body

- BankslipsBankslipsPayRequest
  - `account_id` integer, required — Pismo Platform Account ID.
  - `amount` number, required — Amount to pay.
  - `bankslip` object — Bank slip information
    - `type` 1 | 2, required — bank slip type. (`1` = compensation form, `2` = dealership).<br> Compensation form refers to the method for processing the bank slip. Dealership (cedente) refers to the entity or individual that issues the bank slip.
    - `bar_code` string — Bar code encoding bank slip information such as the bank code, currency code, check digit, due date, amount, and beneficiary information.
    - `digitable_line` string — Digitable line. On a Brazilian bank slip, the digitable line contains numerical payment information encoding details like the payment amount, due date, beneficiary information, and other transaction-specific data.
    - `due_datetime` string, date-time — Due datetime. ISO 8601 format - `yyyy-MM-ddTHH:mm:ss.SSSSSSSSSZ`.
    - `original_amount` number — Original amount.
  - `currency_code` string — ISO 4217 currency code. Can be either numeric or alphabetic.
  - `external_authorization` string — External authorization. Some providers return this value to the `/v1/bankslips/validate` endpoint. If returned, this value must be passed on to a bank slip payment request. Some providers return this to a [Validate bank slip](https://developers.pismo.io/pismo-docs/reference/post-integrated-payments-api-v1-bankslips-validate) call. If returned, you **must** pass it in a [Pay bank slip](https://developers.pismo.io/pismo-docs/reference/post-integrated-payments-api-v1-bankslips-pay) endpoint call.

## Response `202`

Accepted

- BankslipsBankslipsPayResponse
  - `account_id` integer — Pismo Platform Account ID.
  - `amount` number — Amount paid.
  - `authorization_id` integer — Pismo Platform Account ID.
  - `bar_code` string — Bar code encoding bank slip information such as the bank code, currency code, check digit, due date, amount, and beneficiary information.
  - `currency_code` string — ISO 4217 currency code. Can be either numeric or alphabetic.
  - `customer_name` string — Customer name.
  - `digitable_line` string — Digitable line. On a Brazilian bank slip, the digitable line contains numerical payment information encoding details like the payment amount, due date, beneficiary information, and other transaction-specific data.
  - `due_datetime` string, date-time — Due datetime. ISO 8601 format - `yyyy-MM-ddTHH:mm:ss.SSSSSSSSSZ`.
  - `external_id` string — Client-generated ID for client tracking and monitoring.
  - `payment_datetime` string, date-time — Payment datetime.
  - `status` string — Bank slip status. Possible values are `PAID`, `PROCESSING`, `SETTLED`, `ERROR`, and `TIMEOUT`.
  - `additional_info` string — Additional information about the bank slip payment, including provider-specific details.

## Other responses

- `400` — Bad Request
- `403` — Forbidden
- `404` — Not Found
- `409` — Conflict
- `500` — Internal Server Error
- `502` — Bad Gateway
- `504` — Gateway Timeout

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)