Max Pay API

Welcome to the public API documentation for Max Pay, a payment platform regulated by the BCRA (Argentine Central Bank) as a PSPCP (Payment Service Provider with Payment Account Function).

About this API

This API is focused on integrating ERP, accounting and treasury systems with the Max Pay collection platform. It enables you to:

• Sync the integrator's commercial structure (clients, branches, associates).
• Record debt and its modifications (receivables: invoices, credit notes, returns, adjustments) on receivable accounts with CVU.
• Query movements, balances, settlements and operational reports.
• Transfer funds from the customer's current accounts, with a recipients address book.
• Receive notifications of events via webhooks.

Where to start

• Just getting started? → Getting Started — a complete flow in 10 minutes: authenticate, create a client, create a receivable account, issue a receivable, and collect.
• Want to understand the model before integrating? → Concepts — overview, account patterns, how receivables, movements and settlements relate.
• Looking for a specific endpoint? → Available resources below.

Available resources

Resource	Description
Authentication	How to obtain a token and authenticate requests.
Clients	Manage the clients that the customer invoices.
Associates	Manage the associates that operate on behalf of the customer (drivers, guardians, etc.).
Receivable accounts	Accounts with a dedicated CVU where clients transfer payments.
Current accounts	Accounts where the customer's settlements are credited.
Transfers	Send funds from the customer's current accounts, outgoing to third parties or internal between own accounts.
Recipients	Address book of frequent recipients to reuse in transfers.
Receivables	Documents that record debt or its modifications (invoices, credit notes, returns, adjustments).
Settlements	Periodic movement of funds from receivable accounts to the customer's account.
Route settlements	Summary of receivables registered by an associate during a working day.
Webhooks	Real-time event notification to the customer's system.

Global conventions

• Requests and responses in JSON (Content-Type: application/json).
• Errors in application/problem+json (RFC 7807).
• Timestamps in ISO 8601 with offset. E.g. 2026-05-14T10:30:00-03:00.
• Dates (without time) in YYYY-MM-DD.
• Currency codes in ISO 4217. Today only ARS.
• Resource IDs: numeric identifiers (int64).
• Tax ID (taxId): always 11 digits, no dashes. Example: 30999999999.
• Pagination: query params page (1-indexed) and count (default 20, max 200). Total in X-Total-Count header.
• Versioning: /v1/ in every path. Additive changes keep backward compatibility; breaking changes will land in future versions of the API.

Environments

Environment	Base URL
Sandbox	https://api-sandbox.maxpay.com.ar/v1
Production	https://api.maxpay.com.ar/v1

Changes in this version

See Changelog.