Request Batch

You can create virtual accounts between 10 and 5000 through an array.

Availability via API: Argentina | Mexico

Availability Offline: Chile | Brazil (if you need batch Virtual Account creation, please contact our support team)

POST {{api_base_url}}/api/virtual-account-batch


To create virtual accounts in bulk, you'll need to send a POST request to the /api/virtual-account-batch endpoint.

Request

Headers

Parameter
Type
Required
Description

Authorization

String

Required

Mandatory. JWT token in format Bearer eyj0.... For more information about authentication, please refer to Authentication.

Request Body

Parameter
Type
Required
Description
Possible values
Example

externalId

String

Required

A unique identifier generated by your system to track the transaction (alphanumeric and hyphens). We recommend using UUID4 to ensure uniqueness.

0a8bc036-98bc-417e-984a-3ff8dd227d22

accountNumber

String

Required

Localpayment account number.

48.448.400.000.011

country

String

Required

Country. ISO 3166-1 alpha-3.

Countries

MXN

name

String

Optional

Descriptive name for the batch or group of virtual accounts.

accounts

Object

Required

List of virtual account objects to be created. Each object must include its own externalId and beneficiary details.

accounts.externalId

String

Required

Unique identifier for the individual virtual account.

e35e532e-5e2d-403d-89a9-e96f391e631f

accounts.beneficiary

Object

Required

Account Beneficiary Information.

accounts.beneficiary.type

String

Required

Beneficiary type.

COMPANY, INDIVIDUAL

INDIVIDUAL

accounts.beneficiary.name

String

Required

Beneficiary name.

John

accounts.beneficiary.lastName

String

Optional

Beneficiary lastname. Required for individuals, ignored for companies.

Doe

accounts.beneficiary.document

Object

Required

Beneficiary documentation.

accounts.beneficiary.document.type

String

Required

The type of identity document, such as a National Identity Number, Social Security Number, or Driver's License, depending on the country of issuance.

RFC

accounts.beneficiary.document.id

String

Required

Identity document number (usually a number). This must be a valid number according to the rules for the specific document type.

EXTF900101NI1

accounts.beneficiary.address

Object

Optional

Beneficiary's address.

accounts.beneficiary.address.street

String

Optional

Street name.

accounts.beneficiary.address.number

String

Optional

Street number.

accounts.beneficiary.address.city

String

Optional

City.

accounts.beneficiary.address.state

String

Optional

State.

accounts.beneficiary.address.country

String

Optional

Address country.

accounts.beneficiary.address.zipCode

String

Optional

Zip code.

accounts.beneficiary.address.comment

String

Optional

Additional address information.

accounts.beneficiary.website

String

Optional

Beneficiary's Website

https://localpayment.com

Example

Request

Below are examples using curl:

{
    "externalId": "c23c7d04-be6c-4f1a-9650-95bda4656fbd",
    "accountNumber": "{{YourAccountNumber}}",
    "country": "ARG",
    "name": "Virtual Account Test ARG",
    "accounts": [
        {
            "externalId": "0317baaa-7a4a-44c0-a96b-0f721ec41c8f",
            "beneficiary": {
                "type": "INDIVIDUAL",
                "name": "John",
                "lastname": "Doe",
                "document": {
                    "id": "27-32548697-5",
                    "type": "CUIL"
                },
                "address": {
                    "street": "Calle 34",
                    "number": "123",
                    "city": "Quilmes",
                    "state": "Buenos Aires",
                    "country": "Argentina",
                    "zipCode": "7400",
                    "comment": "Area centro"
                },
                "website": "https://mywebsite.com"
            }
        },
        {
            "externalId": "b42a27af-c082-4910-a833-6a800df634ae",
            "beneficiary": {
                "type": "INDIVIDUAL",
                "name": "Lisa",
                "lastname": "Doe",
                "document": {
                    "id": "27-32548697-3",
                    "type": "CUIL"
                },
                "address": {
                    "street": "Calle 41",
                    "number": "123",
                    "city": "Quilmes",
                    "state": "Buenos Aires",
                    "country": "Argentina",
                    "zipCode": "7400",
                    "comment": "Area centro"
                },
                "website": "https://myecommerce.com"
            }
        }
    ]
}

Response

A successful request returns an HTTP status code 200, with the account status set to INPROGRESS. In contrast, if an error occurs, the API responds with an HTTP status code in the 40X range, and detailed error information is provided within the status object.

{
    "externalId": "c23c7d04-be6c-4f1a-9650-95bda4656fbd",
    "internalId": "fe3b1235-b980-4ff0-8207-4d5b0ff976a9",
    "accountNumber": "{{YourAccountNumber}}",
    "status": {
        "code": "100",
        "description": "INPROGRESS",
        "detail": "Batch Process Virtual Account in progress"
    },
    "comment": "For obtaining the asynchronous response, kindly submit a request to the service after a brief interval. GET {api_environment_url}/api/virtual-account-batch/c23c7d04-be6c-4f1a-9650-95bda4656fbd"
}

Error response

{
    "timestamp": "2025-06-18T19:48:58.238+00:00",
    "status": 400,
    "error": "Bad Request",
    "message": "Count can not be blank",
    "path": "/virtual-account/batch"
}

You can check the current status of the virtual accounts using the Check Virtual Account Status endpoint.

Last updated

Was this helpful?