docs

API Introduction

Overview

The FyPay Public API is a comprehensive platform for integrating with PIX payment services and account management. Our API allows you to:

  • Generate dynamic PIX charges for receiving payments
  • Send PIX payments to any key
  • Send PIX payments via QR Code
  • Query balances in real time
  • Manage transaction refunds
  • Integrate instant payments into your application

Environment

Production

ResourceURL
API base URLhttps://api.fypay.me/api
Health checkGET https://api.fypay.me/health
Dashboardhttps://banking.fypay.me

All API endpoints live under the /api prefix (for example, https://api.fypay.me/api/balance). The health check is the only route outside that prefix.

Authentication

All API endpoints (except token generation) require Bearer token authentication. The token is obtained with your OAuth 2.0 credentials and an X.509 client certificate presented in the TLS handshake (mTLS):

In the FyPay Dashboard, go to Settings → Credentials and generate your clientId and clientSecret. The clientSecret is shown only once.

Use the X.509 certificate (PEM, RSA 2048, valid for 2 years) linked to your account and its private key.

Call POST https://api.fypay.me/api/auth/token with your credentials, presenting the certificate in the TLS handshake (for example, curl --cert client.crt --key client.key).

Include the token in the Authorization: Bearer <token> header on all other requests. They do not require a certificate.

The token lifetime is returned in the expires_in field (in seconds) of the response. Renew the token before it expires.

HTTP Status Codes

The API uses standard HTTP status codes to indicate the success or failure of a request:

CodeMeaningDescription
200OKSuccessful request
201CreatedResource created successfully
400Bad RequestInvalid data in the request
401UnauthorizedToken missing, invalid, or expired
403ForbiddenAccess to the resource denied
404Not FoundResource not found
429Too Many RequestsRate limit exceeded
500Internal Server ErrorInternal server error
503Service UnavailableService temporarily unavailable

Date Format

All dates in the API follow the ISO 8601 standard with UTC timezone:

2024-01-15T10:30:00.000Z

Getting Started

Support

For technical questions or support, contact us:

On this page