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

Stellar Payments API

Endpoints related to payments. An SDP payment is an individual payment from an organization to a receiver. Each payment is part of a disbursement and occurs on the Stellar network. Granular payment status is stored in the SDP database and can be viewed in real-time on the SDP dashboard.

Stellar Payments API is one of 33 APIs that Stellar 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, API documentation, an API reference, a GitHub repository, and rate-limit docs.

This API exposes 6 operations across 5 paths, and defines 32 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://horizon-testnet.stellar.org, https://horizon-futurenet.stellar.org.

6 operations 5 paths 32 schemas 3 GET2 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://horizon.stellar.org
Authentication
API Key, API Key, API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 4

Stellar Payments API declares 4 security schemes for authenticating requests. An API key is passed in the header as Authorization (BearerAuth). An API key is passed in the header as Authorization (SEP10Auth). An API key is passed in the header as Authorization (SEP24Auth). An API key is passed in the query as token (SEP24QueryAuth).

  • BearerAuth — Authorization header containing an SDP JWT (ES256) or an SDP API key.
  • SEP10Auth — Authorization header containing a SEP-10 JWT (Bearer {token}).
  • SEP24Auth — Authorization header containing a SEP-24 JWT (Bearer {token}).
  • SEP24QueryAuth — Query parameter containing a SEP-24 JWT.

Paths & Operations 6

Across 5 paths, the API surfaces 6 operations — 3 GET, 2 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Payments 6

Endpoints related to payments. An SDP payment is an individual payment from an organization to a receiver. Each payment is part of a disbursement and occurs on the Stellar network…

GET
/payments
List All Payments
ListAllPayments 10 params → 200401403
POST
/payments
Create Direct Payment
CreateDirectPayment body → 201400401403404
GET
/payments/{id}
Retrieve a Payment
RetrieveAPayment 1 param → 200401403404
PATCH
/payments/retry
Retry Payments
RetryPayments body → 200400401403
PATCH
/payments/{id}/status
Update Payment Status
UpdatePaymentStatus 1 param body → 200400401403404
GET
/transactions/{transaction_hash}/payments
Retrieve a Transaction's Payments
RetrieveATransactionsPayments 4 params → 200

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are PathPaymentStrictReceive (21 properties), PathPaymentStrictSend (21 properties), ReceiverWalletLite (14 properties), Payment (14 properties). Each schema is shown below with its type and property counts.

PaymentStatus
string
The status of the payment
PaymentPagination
object
2 properties
DisbursementStatus
string
RegistrationContactType
string
MessageResponse
object
1 property 1 required
DisbursementLite
object
10 properties
CreateDirectPaymentRequest
object
5 properties 4 required
ReceiverWalletLite
object
14 properties
DisbursementStatusHistory
array
Pagination
object
4 properties
DisbursementStatusHistoryEntry
object
3 properties
ReceiverLite
object
1 property
PaymentStatusHistory
array
An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.
WalletLite
object
7 properties
PaymentStatusHistoryEntry
object
3 properties
Asset
object
The Stellar asset object
6 properties
ReceiversWalletStatus
string
Payment
object
14 properties
VerificationField
string
ReceiversWalletStatusHistoryEntry
object
2 properties
AccountMerge
object
11 properties 10 required
host_function_parameter
object
2 properties 2 required
PathPaymentStrictSend
object
21 properties 14 required
asset_balance_change
object
7 properties 3 required
InvokeHostFunction
object
14 properties 9 required
Links
object
1 property
PathPaymentStrictReceive
object
21 properties 14 required
CreateAccount
object
12 properties 11 required
Payment_2
object
1 property
link
object
2 properties 1 required
address
string
id
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stellar-payments-api-openapi.yml Raw ↑

Other APIs Stellar publishes across the network.

Stellar RPC API
Stellar Accounts API
Stellar Admin API
Stellar API Keys API
Stellar Assets API
Stellar Authentication API
Stellar Balances API
Stellar Bridge Integration API
Stellar Claimable Balances API
Stellar Customers API
Stellar Disbursements API
Stellar Effects API
Where this information came from

This is an independent, third-party profile of Stellar 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.