Cash
Create a cash payment
Create a cash payin
POST
https://api.stage.localpayment.com /api/payin
Create a cash payin order
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. Select among the codes available in each country for a payin cash payment type. Each code is also related to the brand and country in which it operates. NOTE: payment method code might affect the collection currency in bimonetary countries. For more info, see the side note on |
paymentMethod.flow* | string | Mandatory. The payment method data could be embeded in the API request ( |
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. Please refer to Country Codes for a full list of supported countries. |
amount* | number | Mandatory. Amount to charge to your end user. |
currency* | string | Mandatory. The currency in which the amount is expressed. It could be A) the local currency of the selected country or B) the account's currency. If A), the amount will be charged to the customer's cash payment method. If B) and it differs from the local currency, the amount specified will be credited to your account and Localpayment will perform a Foreign Exchange operation to collect the amount expressed in local currency. In bimonetary countries, paymentMethod.code resolves possible ambiguity: the payment will be executed in the currency of that specific payment method network. e.i.: SPID (USD); SPEI (MXN) |
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. |
exchangeRateToken | string | Optional. Token provided by the Foreign Exchange service in order to use an upfront agreed exchange rate. |
payer* | OBJECT | Mandatory. Party Object. Information related to the payer. |
type* | string | Mandatory. Possible values: |
name* | string | Mandatory. |
lastName | string | Mandatory only for |
document* | OBJECT | Mandatory. Party Object. Valid identity document. |
document.type* | string | Mandatory. Document types. Check the regonized document type list per country |
document.id* | string | Mandatory. Identity document id. Usually numbers or combination of numbers and letters. |
userReference | string | Optional. Username or Id in your platform. |
string | Optional. | |
phone | OBJECT | Optional. Party Object. Contact phone number |
phone.countryCode | string | Optional |
phone.areaCode | string | Optional |
phone.number | string | Optional |
birthdate | string | Optional. Individual birthdate / company incorporation date. ISO 8601 format (YYYY-MM-DD) |
nationality | string | Optional |
address | OBJECT | Optional. Party Object. Contact address |
address.street | string | Optional |
address.number | string | Optional |
address.city | string | Optional |
address.state | string | Optional |
address.country | string | Optional |
address.zipCode | string | Optional. Zip code / Postal code |
address.comment | string | Optional. Additional info, such as floor or apartment number. |
merchant* | OBJECT | Mandatory. Party Object. |
intermediaries | array | 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. |
device | OBJECT | Optional. Party Object. |
device.id | 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. |
commercialData | OBJECT | Optional. Party Object. Extra information related to the goods or services traded. See Commercial Party Object below. |
invoce | string | Optional. Invoice reference |
items.pictureUrl | string | Optional. URL pointing to an item picture |
items.description | string | Optional. Item title |
item | array | Optional. List of sold items |
item.id | string | Optional. Item ID |
shipments.number | String | Optional. Number address |
shipments.city | string | Optional. City |
items.quantity | number | Optional. Item description |
items.categoryId | string | Optional. Item category |
shipments | array | Optional. List of shipping addresses |
items.unitPrice | number | Optional. Unit price |
shipments.street | string | Optional. Street address |
shipments.zipCode | string | Optional. Zip code |
shipments.comment | string | Optional. Additional info |
shipments.country | string | Optional. State/Province |
shipments.country | string | Optional. Shipping country |
item.title | string | Optional. Item title |
document | OBJECT | Optional. . Party Object. |
lastName | string | Optional only for |
name* | string | Mandatory. |
type* | string | Mandatory. Possible values: |
birthdate | string | Optional. Individual birthdate / company incorporation date. ISO 8601 format (YYYY-MM-DD). |
phone.number | string | Optional. |
phone.areaCode | string | Optional. |
phone.countryCode | string | Optional. |
phone | OBJECT | Optional. Party Object. Contact phone number |
string | Optional. | |
userReference | string | Optional. Username or id in your platform. |
document.id | string | Optional. Identity document id. Usually numbers or combination of numbers and letters. |
document.type | string | Optional. Document type (related to the merchant's residence) |
address.state | string | Optional. |
address.city | string | Optional. |
address.number | String | Optional. |
address.street | string | Optional. |
address | OBJECT | Optional. Party Object. Contact address |
nationality | string | Optional. |
address.comment | string | Optional. Additional info, such as floor or apartment number. |
address.zipCode | string | Optional. Zip code / Postal code |
address.country | string | Optional. |
beneficiary | OBJECT | Optional. Party Object. |
type | string | Optional. Possible values: |
name | string | Optional. |
lastName | string | Optional only for |
document.id | string | Optional. Identity document id. Usually numbers or combination of numbers and letters. |
document.type | string | Optional. Document type (related to the beneficiary's residence) |
document | OBJECT | Optional. Party Object. |
string | Optional. |
Please refer to this article to learn more about the document type required for the different payment methods by country.
Examples: Cash payin request
To create a payin cash payment through LP api, the request body examples are detailed below.
A Cash payment order expires by default within 7 days iafter the creation date. However, through the LP API, you could cancel any "INPROGRESS" cash order.
Moreover, the cash payment order expiration date can be set according to our clients requirements between 1 to 7 days.
Examples: Cash payin response
Note: The response depends on the payment method and the payment provider configured for this metod. For testing purposes in Stage environment, the responses are mockuped so they may include:
barcode: 3335008800000000006001885552100005200211740749
QR: 00020101021126950014BR.GOV.BCB.PIX2573spi.dev.cloud.itau.com.br/documentos/198e49c5-2330-4ad7-9d0b-967c7b5371225204000053039865802BR5923PMD Gotham NegA cios ME6009SAO PAULO62410503***50300017BR.GOV.BCB.BRCODE01051.0.063040866
QR: 00020126580014br.gov.bcb.pix013627a44d0a-0736-4bbf-a4a4-6e11063973315204000053039865406150.005802BR5911Telequiet496008Campinas62230519mpqrinter12397252666304FA23
How to create a cash paymet ticket?
In most countries, to generate a cash payment ticket, the Payin response data that you must select and add to the ticket are: the "id", the "image", the "barcode" and the "expirationDate". However, take into account that in Peru, you will only need the "ticket id"
element. Please, see the examples bellow.
Elements necessary to create a cash payment ticket in almost all countries:
Note: The response depends on the payment method and the payment provider configured for this metod. For testing purposes in Stage environment, the responses are mockuped so they may include:
barcode: 3335008800000000006001885552100005200211740749
QR: 00020101021126950014BR.GOV.BCB.PIX2573spi.dev.cloud.itau.com.br/documentos/198e49c5-2330-4ad7-9d0b-967c7b5371225204000053039865802BR5923PMD Gotham NegA cios ME6009SAO PAULO62410503***50300017BR.GOV.BCB.BRCODE01051.0.063040866
QR: 00020126580014br.gov.bcb.pix013627a44d0a-0736-4bbf-a4a4-6e11063973315204000053039865406150.005802BR5911Telequiet496008Campinas62230519mpqrinter12397252666304FA23
How to pay a cash payment ticket?
The payment of a cash ticket can be made by reading the "barcode image"
. Another possibility is to pay the cash ticket by informing the "ticket id".
In Peru, the payer will only need to inform the "ticket id".
Check the Payin Status Codes
PayinLast updated