Skip to main content

Introduction

The API lets a third-party application request and collect payments from a Gladys user's wallet, on behalf of a business. These docs cover the third-party integration surface only: the OAuth2 authorization server and the Payments API.

Who these docs are for​

You're a developer building an integration for a business that wants to accept payments through Gladys — a checkout flow, a subscription billing system, an invoicing tool, anything that needs to request money from a Gladys user and know when it's been paid.

How the pieces fit together​

  • OAuth2 is how your application authenticates. You register an application ("OAuth client") tied to your business, and use it to get an access token — either for your own server-to-server calls, or to act on behalf of a specific Gladys user who has authorized your app.
  • Payments is the API you call with that token to create a payment request, hand the payer a checkout link, and find out whether they paid.

See Getting Started to register your first application, or jump straight to the API Reference if you already know the flow.

Before you build against production​

Every OAuth client starts in the TEST environment — a fully working sandbox with simulated money, no verification required. Read Environments before you request live credentials.