Payment Possible Errors

In the table below, it is possible to observe which are the possible returns of the rejectionReason field, inside the consent flow, that can be sent in each step involved with the consent, for the payment flow:

Consent funnel steps	Code

Consent funnel steps	Code
start of authentication	FALHA_INFRAESTRUTURA, TEMPO_EXPIRADO_AUTORIZAÇAO
authentication completion	FALHA_INFRAESTRUTURA, TEMPO_EXPIRADO_AUTORIZAÇAO, REJEITADO_USUARIO
Customer Authorization	FALHA_INFRAESTRUTURA, CONTAS_ORIGEM_DESTINO_IGUAIS, CONTA_SALARIO, SALDO_INSUFICIENTE, VALOR_ACIMA_LIMITE, QRCODE_INVALIDO
Authorization code issued	FALHA_INFRAESTRUTURA, TEMPO_EXPIRADO_CONSUMO

And below are the possible returns for the same rejectionReason field, but for the business rejection of the payment flow.

example: SALDO_INSUFICIENTE
Defines the code for the reason why the payment was rejected

SALDO_INSUFICIENTE - The selected account does not have enough balance to make the payment.

VALOR_ACIMA_LIMITE - The amount exceeds the limit established [in the institution/in the arrangement/other] to allow the client to carry out transactions.

VALOR_INVALIDO - The value sent is not valid for the informed QR Code.

COBRANCA_INVALIDA - Expiration validation, expiration validation or Valid Status.

NAO_INFORMADO - Not reported/identified by the institution holding the account.

PAGAMENTO_DIVERGENTE_CONSENTIMENTO - Payment data different from consent data.

DETALHE_PAGAMENTO_INVALIDO - Parameter [name_field] does not comply with business rules.

PAGAMENTO_RECUSADO_HOLDER - [Description of reason for refusal].

PAGAMENTO_RECUSADO_SPI - [Error code according to reason PACS.002 domain table].

FALHA_INFRAESTRUTURA - [Description of which failure in the infrastructure made processing unfeasible].

FALHA_INFRAESTRUTURA_SPI - Indicates a failure in the Instant Payment System (SPI).

FALHA_INFRAESTRUTURA_DICT - Indicates a failure in the Directory of Transactional Account Identifiers (DICT).

FALHA_INFRAESTRUTURA_ICP - Indicates a failure in the Public Key Infrastructure (PKI).

FALHA_INFRAESTRUTURA_PSP_RECEBEDOR - Indicates a failure in the Payment Service Provider (PSP) infrastructure that receives the payment.

FALHA_INFRAESTRUTURA_DETENTORA - indicates a failure in the infrastructure of the institution that owns the information or resources.

CONTAS_ORIGEM_DESTINO_IGUAIS - Indicates a payment attempt where the source account and the destination account are the same.

The rejectionReason FALHA_INFRAESTRUTURA will not be deleted, it will only cease to be used, thus allowing backward compatibility and integrity between participants.

If you use "x-rejection-reason" in the API header /api/smart-keys/payment-initiation/v1/consents/callback , with the values informed below, the PIX will assume the “Reject” status.

INSUFFICIENT FUNDS
VALUE_ABOVE_LIMIT
INVALID VALUE
BILLING_INVALID
UNINFORMED
PAYMENT_DIVERGENT_CONSENTMENT
INVALID_PAYMENT_DETAIL
PAYMENT_REFUSED_HOLDER
PAYMENT_REFUSED_SPI
FAILURE_INFRASTRUCTURE
CONSENT_EXPIRED

"rejectionReason": {
        "code": "NAO_INFORMADO",
        "detail": "Não Informado"
      }

Journey expired due to timeout or canceled by the user

As of this product update, you have the whitelabel journey expiration scenario, in which a user who has canceled the flow, before being redirected to the transaction confirmation institution, or exceeds the token generation timeout, tries return to the same journey that was generated (same JourneyID). An error screen is presented, as shown in the example below, and the user is redirected to the same endpoint registered in the Redirect URL field in your application.

Example of return on journey cancellation event, in the webhook

{
  "event": "journey:cancel",
  "eventDate": "2023-11-22T18:55:54.335Z",
  "data": {
    "journeyId": "FlxcMSUD4q_tTiCipuCOrSwfBKhbUP0_"
  }
}

Example of return on journey expiration event, in the webhook

{
  "event": "journey:expired",
  "eventDate": "2023-11-22T18:55:54.335Z",
  "data": {
    "journeyId": "FlxcMSUD4q_tTiCipuCOrSwfBKhbUP0_"
  }
}