Boleto (Brazil)
Boleto Bancario is a voucher/cash-based payment method used exclusively in Brazil.
Create a Boleto
POST
https://api.stage.localpayment.com /api/payin
Headers
Name | Type | Description |
---|---|---|
Authorization* | string | Mandatory. JWT token in format |
Request Body
Name | Type | Description |
---|---|---|
paymentMethod* | OBJECT | Manatory. Payment method details |
paymentMethod.type* | string | Mandatory. Cash |
paymentMethod.code* | string | Mandatory. method code 1302 |
externalId* | string | Mandatory. An ID that is meaningful to you and your system. It must be unique and alphanumeric, no characters allowed. |
country | string | Mandatory. Your end user's country (i.e. country in which the payment will be processed), in ISO format. BRA |
amount | number | Mandatory. Amount to charge to your end user. Must be sent with 2 decimal places, separated by a dot. |
currency | string | Mandatory. BRL |
accountNumber* | string | Mandatory. Your Localpayment account number in which the amount will be credited. |
conceptCode | string | Mandatory. Choose the suitable concept code from our Concept Code List. Based on our experience, the most usual are 0039 (remittances) and 0040 (corporate payments). |
comment | string | Optional. A comment related to the transaction. It should be something meaningful to your business. |
merchant* | OBJECT | Mandatory. Party Object. Information related to the merchant. |
merchant.type* | string | Mandatory. Possible values: |
merchant.name* | string | Mandatory. merchant name |
merchant.lastname* | string | Optional for INDIVIDUAL merchat.type / Ignored for COMPANY. |
document | OBJECT | Optional. Party Object. Valid identity document. |
document.type | string | Optional. Document type: CNPJ for |
document.id | string | Optional. Identity document id. Usually numbers or combination of numbers and letters. |
birthdate | string | Optional. Individual birthdate / company incorporation date. ISO 8601 format (YYYY-MM-DD) |
nationality | string | Optional |
address | OBJECT | Optional |
address.street | string | Optional |
address.number | string | Optional |
address.city | string | Optional |
address.state | string | Optional |
address.country | string | Optional |
address.zipCode | string | Optional |
address.comment | string | Optional |
payer | OBJECT | Mandatory. Party Object. Information related to the payer. |
type | string | Mandatory. Possible values: COMPANY, INDIVIDUAL |
name | string | Mandatory. COMPANY, INDIVIDUAL name |
lastname | string | Mandatory only for INDIVIDUAL type / Ignored for COMPANY, |
document | OBJECT | Mandatory. Party Object. Valid identity document. |
type | string | Mandatory. Document type: CNPJ for |
id | string | Mandatory. Identity document id. Usually numbers or combination of numbers and letters. |
string | Mandatory | |
phone | OBJECT | Optional.Party Object. |
countryCode | string | Optional |
areaCode | string | Optional |
number | string | Optional |
birthdate | string | Optional. Individual birthdate / company incorporation date. ISO 8601 format (YYYY-MM-DD) |
nationality | string | Optional |
address | OBJECT | Mandatory.Party Object. Contact address |
street | string | Mandatory |
number | string | Mandatory |
city | string | Optional |
state | string | Optional |
country | string | Mandatory |
zipCode | string | Optional. Zip code / Postal code |
comment | string | Optional |
userReference | string | Optional. Username or Id in your platform. |
intermediaries | string | Optional. Array of Party objects. It represents others parties in the payment chain because of the end user is not your direct customer. Take into account the array sequence: your client should be the first element, the client of your client should be the second and so on, until there are no more intermediaries. |
commercialData | OBJECT | Optional. Party Object. Extra information related to the goods or services traded. |
invoice | Optional. Invoice reference | |
items | array | Optional. List of sold items |
items.id | string | Optional. Item Id |
items.tittle | string | Optional. Item title |
items.description | string | Optional. Item description |
items.pictureUrl | string | Optional. URL pointing to an item picture |
items.categoryId | string | Optional. Item category Id |
items.quantity | number | Optional. Item quantity |
items.unitPrice | number | Optional. Unit price |
shipments | array | Optional. List of shipping addresses |
shipments.street | string | Optional. Shipping street |
shipments.number | string | Optional. Shipping Number street |
shipments.city | string | Optional. Shipping City |
shipments.state | string | Optional. Shipping State/Province |
shipments.country | string | Optional. Shipping country |
shipments.zipCode | string | Optional. |
shipments.comment | string | Optional. |
device | OBJECT | Optional. Party Object. |
device.deviceId | string | Optional. Android / iPhone device ID. Can be blank for other device types such as PC / Mac. |
device.ip | string | Optional. Device IP address |
device.browser | string | Optional. Browser |
metaData | OBJECT | Optional. Party Object. Unstructured object to record any metadata meaningful to you. |
Examples: Boleto payin request
Below are examples for creating a payment Boleto through our API.
A Boleto expires by default within 7 days of the creation date, however, through the LP API, any cash payment order that is in "IN PROGRESS" status can be cancelled. If you require another expiration date, it can be configured between 1 and 7 days.
Examples: Cash payin response
How to create a Boleto?
To generate a Bank Ticket, the Payin response data that you must select and add to the ticket are: the “image”, the “barcode” and the “expiration date”.
Elements necessary to create a Boleto in Brazil
How to pay a cash payment ticket?
Payment for a Ticket can be made by reading the "ticket.image" or by entering the "ticket.barcode".
Check the Payin Status Codes
PayinLast updated