How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Paxos Payments API

Payments represent actual transfers of rewards to the payout address associated with a given statement. Payments are made on-chain to a specified payout address. Payments tie 1:1 with a statement amount.Use the `ref_id` to link payments to statements. > Some fields (e.g., `account_id`, `profile_id`) are populated for consistency but are not relevant to reward-specific flows.*These endpoints are only relevant for Global Dollar Network (GDN) partners.*

Paxos Payments API is one of 43 APIs that Paxos publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 1 operation across 1 path, and defines 5 schemas. It is described by OpenAPI 3.0.0, at version 2.0.

Requests are made against 2 base URLs: https://api.paxos.com/v2, https://api.sandbox.paxos.com/v2.

1 operations 1 paths 5 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
2.0
Base URL
https://api.paxos.com/v2
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Paxos Payments API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the clientCredentials flow, exposing 36 scopes.

  • OAuth2 — Paxos APIs use [OAuth 2](https://tools.ietf.org/html/rfc6749) with the [client credentials](https://tools.ietf.org/html/rfc6749section-4.4) grant flow. Token U…

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

Payments 1

Payments represent actual transfers of rewards to the payout address associated with a given statement. Payments are made on-chain to a specified payout address. Payments tie 1:1…

GET
/statements/paymentsdeprecated
List Payments
ListPayments 8 params → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Payment (17 properties), ListPaymentsResponse (2 properties). Each schema is shown below with its type and property counts.

Payment
object
17 properties
Product
string
ListPaymentsResponse
object
2 properties
PaymentType
string
PaymentStatus
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paxos-payments-api-openapi.yml Raw ↑

Other APIs Paxos publishes across the network.

Paxos Account Members API
Paxos Accounts API
Paxos Address Verification API
Paxos API Credentials API
Paxos Claims API
Paxos Crypto Deposits API
Paxos Crypto Withdrawals API
Paxos Deposit Addresses API
Paxos Events API
Paxos ExchangePublic API
Paxos Fees API
Paxos Fiat Transfers API
Where this information came from

This is an independent, third-party profile of Paxos Payments API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.