Collection

Using the collection information generated in the functionalities below, the client can generate a QR CODE through own automation, which, when read, will retrieve the payment data.

⚠️

Important:

The two-dimensional barcode QR Code must be generated following the Brazil Central Bank specifications (<https://www.bcb.gov.br/estabilidadefinanceira/participantespix>).

Collection with due date - Create collection

This functionality allows generating a collection for payment at a future date. In addition to the collection amount, it is also possible to configure interest, fines and discounts.

We request the fields:

FieldDescriptionFormatMandatory
txIdUnique identifier that allows the receiver to identify the collectionstringYes
calendarioDue date and the validity date after expiration (optional, default 30 days)objectYes
devedorData of the individual or legal entity to whom the collection will be addressed. Not necessarily the final payerobjectNo
locPayload location identificationintegerNo
valorCollection amounts are: original amount, interest, fine, price reduction and discountobjectYes
chavePIX key for generating the collectionstringYes
solicitacaoPagadorMessage intended for the payer (limited to 140 characters)stringNo
infoAdicionaisEach respective additional information contained in the list (name and amount) must be presented to the payerArrayNo

Response:

FieldDescriptionFormatNullablle
calendarioCollection creation date, due date and validity date after expiration (if provided)objectNo
txIdCollection transaction identificationstringYes
revisaoDenotes the collection review, starting at zero and varying in increments of 1. The increment in a collection must occur whenever an object of the collection in question is changed. The loc field is an exception to this rule. If in a given change to a collection, the only field changed is the loc field, then there is no increment.integerNo
devedorData of the individual or legal entity to whom the collection will be addressedobjectNo
recebedorData of the bank slip receiver, who is the BS2 clientobjectNo
locPayload location identificationobjectNo
statusCollection status, see table [Collection Status]stringNo
valorCollection amounts are: original amount, interest, fine, price reduction and discountobjectNo
chavePix key used to generate the collectionstringYes
solicitacaoPagadorMessage intended for the payer (limited to 140 characters)stringNo
infoAdicionaisEach respective additional information contained in the list (name and amount) must be presented to the payerArrayYes

Cobrança com vencimento - Criar cobrança

Collection with due date - Review

This functionality allows changing a previously created collection for payment on a future date.

We request the fields:

FieldDescriptionFormatMandatory
txIdUnique identifier that allows the receiver to identify the collectionstringYes
calendarioDue date and validity date after expiration (the latter is optional)objectYes
devedorData of the individual or legal entity to whom the collection will be addressed. Not necessarily the final payerobjectNo
locPayload location identificationobjectYes
statusCollection status, see table [Collection Status]stringYes
valorCollection amounts are: original amount, interest, fine, price reduction and discountobjectYes
chavePix key for generating the collectionstringNo
solicitacaoPagadorMessage intended for the payer (limited to 140 characters)stringNo
infoAdicionaisEach respective additional information contained in the list (name and amount) must be presented to the payerArrayNo

Response:

FieldDescriptionFormatNullablle
calendarioDisplays the collection creation date, due date and validity date after expiration (if provided)objectNo
txIdUnique identifier that allows the receiver to identify the collectionstringYes
revisaoDenotes the collection review, starting at zero and varying in increments of 1. The increment in a collection must occur whenever an object of the collection in question is changed. The loc field is an exception to this rule. If in a given change to a collection, the only field changed is the loc field, then there is no increment.integerNo
devedorData of the individual or legal entity to whom the collection will be addressedobjectNo
recebedorData of the bank slip receiver, who is the BS2 clientobjectNo
locPayload location identificationobjectNo
statusDisplays the collection status, see table [Collection Status]stringNo
valorDisplays the collection amounts, which are: original amount, interest, fine, price reduction and discountobjectNo
chavePix key used to generate the collectionstringYes
solicitacaoPagadorMessage intended for the payer (limited to 140 characters)stringNo
infoAdicionaisEach respective additional information contained in the list (name and amount) must be presented to the payerArrayYes

Cobrança com vencimento - Revisar

Collection - Create collection

This functionality allows generating an immediate payment collection.

We request the fields:

FieldDescriptionFormatMandatory
calendarioExpiration date in seconds from the time the collection is issued. Once the collection has expired, it cannot be paidobjectYes
devedorData of the individual or legal entity to whom the collection will be addressed. Not necessarily the final payerobjectYes
valorRequests the collection amounts and the type of change (If equal to 0, the original amount is assumed, and equal to 1 the user can change the amount)objectYes
chavePix key for generating the collectionstringYes
solicitacaoPagadorMessage intended for the payer (limited to 140 characters)stringNo
infoAdicionaisEach respective additional information contained in the list (name and amount) must be presented to the payerArrayNo

Response:

FieldDescriptionFormatNullablle
calendarioCollection creation and expiration dateobjectNo
statusDisplays the collection status according to table [Collection Status]stringNo
txIdUnique identifier that allows the receiver to identify the collectionstringYes
revisaoDenotes the collection review, starting at zero and varying in increments of 1. The increment in a collection must occur whenever an object of the collection in question is changedintegerNo
locationLocation of the payload to be informed when creating the collectionstringYes
devedorData of the individual or legal entity to whom the collection will be addressed. Not necessarily the final payerobjectNo
valorCollection amountobjectNo
chavePix key used to generate the collectionstringYes
solicitacaoPagadorMessage intended for the payer (limited to 140 characters)stringNo
infoAdicionaisEach respective additional information contained in the list (name and amount) must be presented to the payerArrayYes

Cobrança - Criar cobrança

Collection - Review

This functionality allows changing an immediate payment collection.

We request the fields:

FieldDescriptionFormatMandatory
txIdUnique identifier that allows the receiver to identify the collectionstringYes
calendarioRequests due date and validity date after expiration (the latter is optional)objectYes
devedorRequests data from the individual or legal entity to whom the collection will be addressed. Not necessarily the final payerobjectNo
locPayload location identificationobjectYes
statusCollection status, see table [Collection Status]stringYes
valorRequests the collection amounts, which are: original amount, interest, fine, price reduction and discountobjectYes
chavePix key for generating the collectionstringYes
solicitacaoPagadorMessage intended for the payer (limited to 140 characters)stringNo
infoAdicionaisEach respective additional information contained in the list (name and amount) must be presented to the payerArrayNo

Response:

FieldDescriptionFormatNullablle
calendarioDisplays the collection creation date, due date and validity date after expiration (if provided)objectYes
statusDisplays the status of the collection, see table [Collection Status]stringNo
txIdUnique identifier that allows the receiver to identify the collectionstringNo
revisaoDenotes the collection review, starting at zero and varying in increments of 1. The increment in a collection must occur whenever an object of the collection in question is changed. The loc field is an exception to this rule. If in a given change to a collection, the only field changed is the loc field, then there is no increment.integerNo
locationLocation of the payload to be informed when creating the collection detail what it isstringYes
devedorDisplays data on the individual or legal entity to whom the collection will be addressedobjectNo
valorDisplays the collection amounts, which are: original amount, interest, fine, price reduction and discountobjectNo
chavePix key used to generate the collectionstringYes
solicitacaoPagadorMessage intended for the payer (limited to 140 characters)stringNo
infoAdicionaisEach respective additional information contained in the list (name and amount) must be presented to the payerArrayYes

Cobrança - Revisar

Collection - Create by Transaction Id

This functionality allows generating a collection for immediate payment.

We request the fields:

FieldDescriptionFormatMandatory
txIdUnique identifier that allows the receiver to identify the collectionstringYes
calendarioRequests due date and validity date after expiration (the latter is optional)objectYes
devedorRequests data from the individual or legal entity to whom the collection will be addressed. Not necessarily the final payerobjectYes
valorRequests the collection amounts, which are: original amount, interest, fine, price reduction and discountobjectYes
chavePix key for generating the collectionstringSim
solicitacaoPagadorRequests message intended for the payer (limited to 140 characters)stringNo
infoAdicionaisEach respective additional information contained in the list (name and amount) must be presented to the payerArrayNo

Response:

FieldDescriptionFormatNullablle
calendarioDisplays the collection creation date, due date and validity date after expiration (if provided)objectNo
statusDisplays the collection status, see table [Collection Status]stringNo
txIdUnique identifier that allows the receiver to identify the collectionstringYes
revisaoDenotes the collection review, starting at zero and varying in increments of 1. The increment in a collection must occur whenever an object of the collection in question is changed. The loc field is an exception to this rule. If in a given change to a collection, the only field changed is the loc field, then there is no incrementintegerNo
locationLocation of the payload to be informed when creating the collectionstringYes
devedorDisplays data on the individual or legal entity to whom the collection will be addressedobjectNo
valorDisplays the collection amounts, which are: original amount, interest, fine, price reduction and discountobjectNo
chavePix key used to generate the collectionstringYes
solicitacaoPagadorMessage intended for the payer (limited to 140 characters)stringYes
infoAdicionaisEach respective additional information contained in the list (name and amount) must be presented to the payerArrayYes

Cobrança - Criar por Id da transação

Collection - Check by TxId

This functionality allows checking a specific collection based on the identification created by the client when generating the collection.

We request the fields:

FieldDescriptionFormatMandatory
txIdUnique identifier that allows the receiver to identify the collectionstringYes
revisaoDenotes the collection review, starting at zero and varying in increments of 1. The increment in a collection must occur whenever an object of the collection in question is changed. The loc field is an exception to this rule. If in a given change to a collection, the only field changed is the loc field, then there is no increment.integerNo

Response:

FieldDescriptionFormatMandatory
calendarioDisplays the collection creation date, due date and validity date after expiration (if provided)objectNo
statusDisplays the collection status, see table [Collection Status]stringNo
txIdUnique identifier that allows the receiver to identify the collectionstringYes
locationLocation of the payload to be informed when creating the collectionstringYes
revisaoDenotes the collection review, starting at zero and varying in increments of 1. The increment in a collection must occur whenever an object of the collection in question is changed. The loc field is an exception to this rule. If in a given change to a collection, the only field changed is the loc field, then there is no increment.integerNo
devedorDisplays data on the individual or legal entity to whom the collection will be addressedobjectNo
valorDisplays the collection amounts, which are: original amount, interest, fine, price reduction and discountobjectNo
chavePix key used to generate the collectionstringYes
solicitacaoPagadorDisplays the text to be presented to the payer, if definedstringYes
infoAdicionaisMessage intended for the payer (limited to 140 characters)ArrayYes
pixEach respective additional information contained in the list (name and amount) must be presented to the payerArrayYes

Cobrança - Consultar por TxId

Collection - Check list of collections

This functionality allows recovering one or more collections generated from some parameters.

We request the fields:

FieldDescriptionFormatMandatory
InicioStart of desired search periodstringYes
FimEnd of desired search periodstringYes
CPFIf you wish to filter by document, the payer's CPF cannot be used with the CNPJ fieldstringNo
CNPJIf you wish to filter by document, the payer's CNPJ cannot be used with the CPF fieldstringNo
StatusCollection status, see table [Collection Status]stringYes

Response:

FieldDescriptionFormatNullablle
inicioInformed start dateobjectNo
fimInformed end datestringNo
cpfPayer's CPFstringYes
cnpjPayer's CNPJstringYes
calendarioCollection creation date, due date and validity date after expiration (if provided)objectNo
statusCollection status, see table [Collection Status]stringNo
txIdUnique identifier that allows the receiver to identify the collectionstringYes
revisaoDenotes the collection review, starting at zero and varying in increments of 1. The increment in a collection must occur whenever an object of the collection in question is changed. The loc field is an exception to this rule. If in a given change to a collection, the only field changed is the loc field, then there is no incrementintegerNo
locationLocation of the payload to be informed when creating the collectionstringYes
devedorData of the individual or legal entity to whom the collection will be addressedobjectNo
valorCollection amounts are: original amount, interest, fine, price reduction and discountobjectNo
chavePix key used to generate the collectionstringYes
solicitacaoPagadorMessage intended for the payer (limited to 140 characters)stringYes
pixEach respective additional information contained in the list (name and amount) must be presented to the payerArrayYes

Cobrança - Consultar lista de cobranças

Collection status

The table below shows the collection status:

FieldDescription
ATIVAThe collection is ready for payment
CONCLUIDAThe collection was paid
REMOVIDA_PELO_USUARIO_RECEBEDORThe collection was canceled by the user
REMOVIDA_PELO_PSPThe collection was canceled by Banco BS2