payments

Your internal orderId. Only can be used for once. 
you can use it to associate a payment and you can use UUID generation algorithm to generate it

clientRequestId

institutionId

Payment initiation type:
PIX_INIC - Pre registration of payee's account
PIX_MANU - The creditor object must be sent with all payee information.
PIX_DICT - The pixKey field represents creditor information.
PIX_QRCODE - The qrCode field represents creditor information.

initType

User (natural person) who is logged in to the payment initiator institution

customer

Payment initiation date, the date here must be utc-3
maxLength: 10
pattern: ^(\d{4})-(1[0-2]|0?[1-9])-(3[01]|[12][0-9]|0?[1-9])$
example: 2021-01-01

date

User (natural person) who is logged in to the Payment Initiator institution.
maxLength: 11
example: 11111111111
pattern: ^\d{11}$
[Restriction] Required if customer.identifierType is CNPJ

loggedUserCpf

ibge town code
minLength: 7
maxLength: 7
pattern: ^\d{7}$
example: 5300108

ibgeTownCode

Pix key
maxLength: 77
pattern: [\w\W\s]*
example: 12345678901
The types of keys can be: phone, e-mail, CPF/CNPJ or random key.
In the case of a mobile phone, it must be informed in the E.1641 standard. 
In the case of e-mail, it must have the format xxxxxxxx@xxxxxxx.xxx(.xx) and a maximum of 77 characters. 
In the case of CPF, it must be informed with 11 numbers, without dots or dashes. In the case of CNPJ, it must be informed with 14 numbers, without dots or dashes. 
[Restriction] If initType is PIX_MANU, the proxy field should not be filled in. If initType is PIX_INIC, PIX_DICT, PIX_QRCODE, the proxy field should always be filled with the Pix key.

proxy

QR code
maxLength: 512
pattern: [\w\W\s]*
example: 00020104141234567890123426660014BR.GOV.BCB.PIX014466756C616E6F32303139406578616D706C652E636F6D27300012 BR.COM.OUTRO011001234567895204000053039865406123.455802BR5915NOMEDORECEBEDOR6008BRASILIA61087007490062 530515RP12345678-201950300017BR.GOV.BCB.BRCODE01051.0.080450014BR.GOV.BCB.PIX0123PADRAO.URL.PIX/0123AB CD81390012BR.COM.OUTRO01190123.ABCD.3456.WXYZ6304EB76
This field should be in UTF-8 format.  
[Restriction] Required for PIX_QRCODE payments, with a maximum size of 512 bytes.

qrCode

Amount that will be paid by the user
minLength: 4
maxLength: 19
pattern: ^((\d{1,16}\.\d{2}))$
example: 100000.12
[Restriction] The value with 2 decimal places. 

amount

maxLength: 3
pattern: ^([A-Z]{3})$
example: BRL
National currency code according to ISO-4217, i.e., 'BRL'. All reported monetary values are represented with the current currency of Brazil.

currency

The URL redirected after completing user authentication and consent in an institutional environment.

redirectURL

Payment description
maxLength: 140
pattern: [\w\W\s]*
example: Pagamento da nota XPTO035-002.
It must be filled in whenever the paying user enters some additional information in a payment, to be sent to the recipient.

remittanceInformation

debtorAccount

creditorAccount

externalInfo

clientMetadata

Authorization

status

statusReason

When status is CONSENT_AWAITING_AUTHORIZATION

consentRedirectUrl

Learn how to create a payment initiation using the Klavi payment API with this example Curl command. Includes endpoint, authorization requirements, request payload parameters, and details about the response. Keep an eye out for a possible response code 40

Create a payment initiation