---
title: "Accept/reject recurrence authorization"
method: POST
path: "/inst-pull-pay/v1/pix/automatic/payer/authorization"
tags: ["Automatic Pix"]
---

# Accept/reject recurrence authorization

`POST /inst-pull-pay/v1/pix/automatic/payer/authorization`

Pix Automatic payee recurrence payment authorization acceptance or rejection

## Headers

- `Authorization` string, required
- `Idempotency-Key` string, required

## Request body

- AuthorizationRequest — Authorization request
  - `recurrence_id` string, required — BACEN recurrence ID
  - `status` 'ACCEPTED' | 'REJECTED', required — Authorization status
  - `reason` 'AP13' | 'AP14' — Rejected authorizations reason code. Mandatory when `status` is `REJECTED`. * `AP13` - Paying user rejects recurrence confirmation for periodic payments due to receiving user not recognized * `AP14` - Paying user rejects recurrence confirmation for periodic payments due to receiving user not interested in using Automatic Pix
  - `max_payment_amount` number — Payer-defined maximum payment amount for dynamic amount recurrences.
  - `journey_type` 'AUT1' | 'AUT2' | 'AUT3' | 'AUT4', required — Recurrence payment type: `AUT1` - Bank notification. If the merchant has the payer's banking information, a push notification can be sent directly to the payer's bank app, prompting them to authorize the recurring payment. `AUT2` - Authorization via QR Code. Payer scans a merchant provided QR Code to authorize recurring payments. This method does not initiate an immediate payment, allowing the first payment to be scheduled for a later date. `AUT3` - Authorization via QR Code with first payment. Similar to the second method, but the QR Code includes information for both the authorization and the initial payment, enabling the payer to authorize the recurring payment and make the first payment in a single step. `AUT4` - Post-payment sign-up path. After completing a one-time payment via QR Code, the payer is offered the option to authorize recurring payments for future transactions For more information, refer to [Pix automatic use cases (journeys)](https://developers.pismo.io/pismo-docs/docs/pix-automatic-beta-copy-2#pix-automatic-use-cases-journeys).
  - `payment_date_time` string, datetime — Date time from a successful payment. Mandatory for the `AUT3` journey. RFC 3339 value. Format: YYYY-MM-DDThh:mm:ss.SSSZ.
  - `transaction_identification` string — Transaction ID from a successful payment. **REQUIRED** for the `AUT3` journey.

## Response `201`

OK

- AuthorizationResponse — Authorization response for a credit or debit purchase.
  - `mti` string — Message type ID. For example: `0100` = auth. request, `0110`` = auth. response, `0120` = auth. advice. For more information, see [MTI](https://en.wikipedia.org/wiki/ISO_8583#Message_type_indicator_(MTI)).
  - `authorization_code` string — Authorization code.
  - `response_code` string — Network two-digit response code. For example: 00 = approve, 51 = insufficient funds, 57 = card not active, 96 = system failure, etc. For more information, see [Validation codes for authorization events](https://developers.pismo.io/pismo-docs/docs/validation-codes-for-authorization-events). If `approve` = `false`, you can use this value to respond to the network.
  - `authorization_date_time` string — Authorization date and time in Coordinated Universal Time (UTC), i.e., 2020-01-01T10:10:00.000-03:00.
  - `custom_code` 'FL2' | 'FL8' | 'FLB' | 'FLE' | 'DCM' | 'VMN' | '998' | 'LUD' | 'LUE' | 'LUT' | 'LGE' | '810' | 'PFT' | 'IAT' | 'BND' | 'ANF' | 'CTE' | 'CED' | 'ZBD' | 'FRB' | 'UBT' | 'FL6' | 'BNF' | 'BNP' | 'BNR' | 'VED' | 'BNU' | 'VEV' | 'UBN' | 'CSU' | 'NPL' | 'OP1' | 'TNF' | 'Z26' | 'Z24' | 'Z29' | 'Z23' | 'Z22' — Internal custom code generated in authorization flow for declined requests, indicating the reason the request was declined. For more information, see [authorization validations](https://developers.pismo.io/pismo-docs/docs/validation-codes-for-authorization-events#authorization-validations).
  - `match_address` boolean — Is cardholder address street and number the same as that contained on the platform?
  - `match_postal_code` boolean — Is cardholder postal code the same as the one contained on the platform?
  - `postal_five_digits` boolean — Is this a valid postal code with five digits?
  - `no_address_data` boolean — Is address registered on platform?
  - `authorization_id` integer — Authorization ID
  - `account_id` integer — Account ID
  - `installment_value` string — Installment value. If there are no installments, this is the same as `contract_amount`.
  - `interest_rate` number — Monthly interest rate
  - `number_of_installments` number — Number of installments
  - `contract_amount` string — Transaction value
  - `crediario_responses` CrediarioResponse[] — If there is more than one installment, this is the data for them.
    - `installmentValue` string — Installment value
    - `monthlyInterestRate` string — Monthly interest rate
    - `totalAmount` string — Total amount
    - `numberOfInstallments` string — Number of installments
    - `feeAmount` string — Fee amount
    - `taxesAmount` string — Taxes amount
    - `taxesPercentageOfTotalAmount` string — Taxes percentage of total amount
    - `feePercentageOfTotalAmount` string — Fee percentage of total amount
    - `planType` string — Plan type - with interest (20), without interest(21) or a crediario type(25)
    - `annualInterestRate` string — Annual interest rate
    - `monthlyTotalEffectiveCost` string — Monthly total effective cost
    - `annualTotalEffectiveCost` string — Aannual total effective cost
    - `installmentDate` string — Installment date - format = yyyymmdd
    - `insurance` string — Insurance
    - `insurancePercentageOfTotalAmount` string — Insurance percentage of total amount
    - `other` string — Any other added values, if applicable, that the cardholder is paying
    - `otherPercentageOfTotalAmount` string — Other percentage of total amount
    - `totalAmountToMerchant` string — Total amount to be paid to merchant (purchase amount)
    - `merchantAmountPercentage` string — Percentage of the total amount to be paid to merchant
    - `reservedForFutureUse` string — Reserved for future use

## Other responses

- `400` — Bad request
- `401` — Access token is missing or invalid
- `404` — Not Found
- `500` — Internal server error

---

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