# JPMC-PDP Documentation from https://developer.payments.jpmorgan.com

# Receivables

This page provides a technical overview of our Receivables APIs, including references and OpenAPI specifications (OAS) for both the global and Brazil-specific versions of the Request to Pay via QR Code API. The OAS for Brazil is available in Portuguese to meet regional requirements and cannot be used outside of Brazil.

### Pay via QR Code Global OAS

View and download the global file in English.

[Learn more](/api/treasury/receivables/request-to-pay#/)

### Pay via QR Code for Brazil OAS

View and download the file in Portuguese, available exclusively for use in Brazil.

[Learn more](/api/treasury/receivables/request-to-pay-brazil#/)

## Request to Pay via QR Code API

The Request to Pay API is an API solution for generating on-demand payment requests and links. It uses real-time payment processing to create QR codes for instant payment links, supporting seamless integration with payment systems such as Pix in Brazil.

For more information, refer to the [Request to Pay developer documentation.](/docs/treasury/receivables/capabilities/request-to-pay-via-qr-code/overview)

### Versioning

The Request to Pay API supports [versioning](/api/versioning) using a prefix in the endpoint URL. This prefix has the following format: "vXX", where XX is the version number.

For example: `https://api-mock-payments.aws.jpmchase.net/receivables/request-to-pay/v1/payment-requests`

### Production endpoints

The Request to pay API has a single point of entry: `https://api.payments.jpmorgan.com/receivables/request-to-pay/v1`

### Status and error response codes

The Request to Pay API uses [standard HTTP response codes](/api/response-codes), and provides additional detail through the error response payload. Further details are provided in the [status responses and error codes page](/api/treasury/receivables/error-codes).