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

GetPaid Payments API

Create and manage payments initiated by the platform on behalf of the buyer.For recurring and unscheduled payments based on a previous standing instruction.

GetPaid Payments API is one of 6 APIs that GetPaid 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 and an API reference.

This API exposes 4 operations across 4 paths, and defines 102 schemas. It is described by OpenAPI 3.1.0, at version v2.

Requests are made against 2 base URLs: https://api.getpaid.io, https://api.sandbox.getpaid.io.

4 operations 4 paths 102 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v2
Base URL
https://api.getpaid.io
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 4

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

Payments 4

Create and manage payments initiated by the platform on behalf of the buyer. For recurring and unscheduled payments based on a previous standing instruction.

POST
/v2/payments
Create a payment
create_payment 1 param body → 201400401422429500
GET
/v2/payments/{payment_id}
Get a payment
get_payment 1 param → 200401404422429500
POST
/v2/payments/{payment_id}/refunds
Refund a payment
refund_payment 2 params body → 201400401422429500
POST
/v2/payments/query
Query payments
query_payments 1 param body → 200400401422429500

Schemas 102

The contract defines 102 schemas that model the data the API accepts and returns. The most detailed are GetPaymentResponse (18 properties), CreatePaymentResponse (11 properties), CreatePaymentRequest (7 properties), PaymentTotals (6 properties). Each schema is shown below with its type and property counts.

EstimatedUpdateBefore
Reference
SplitsCalculatedAndCalculatingFees
object
The list of payment splits for the accounts involved in the funds flow. The final split amounts and processing fees have been calculated.
2 properties 2 required
Version
string
A resource version.
DateTimeOffset
string
Date-time with time zone offset in ISO 8601 format without second fractions ([RFC 9557](https://www.rfc-editor.org/rfc/rfc9557.html)).
AccountId
CreatePaymentRequest
object
7 properties 5 required
PaymentOriginCheckout
PaginationData
array
The list of queried elements.
Percentage
number
PaymentMethodDetails
The payment method used.
PartialRefundPaymentResponse
AmountMinor
integer
The payment amount in the minor currency unit (e.g. 100 cents for 1 EUR).
CreatePaymentResponse
object
11 properties 8 required
PaymentWebhooksRequest
object
Configuration for webhooks to receive payment status updates.
1 property 1 required
PaymentCheckoutDescription
SplitBaseAmount
object
The amount in payment currency to be allocated to this account. The sum of all split amounts for all accounts must be exactly the total amount of the payment o…
1 property 1 required
PaymentOriginApi
BasePaymentMethodDetails
PaginatedResponse
object
2 properties 1 required
QueryPaymentsRequest
SplitRemainingAmountRequest
SplitPercentageAmountRequest
AccountVersion
PaginationCursor
string
The cursor to the last item. If non-empty, can be used to fetch the next page. If not set, there is no more elements.
RefundPaymentResponse
CardPaymentMethodRequest
ProcessingFeeAmount
SddPaymentMethodDetails
PaymentMethodRequest
The payment method configuration for this payment.
CheckoutId
BaseSortsRequest
array
Fields to sort the data by. If not set, the data will be sorted by the creation date descending.
CardDynamicDescriptor
string
The card dynamic descriptor. It will be prefixed with GPD when displayed on the buyer statement. You don't need to include the GPD prefix in the value sent.
QueryPaymentsResponse
BasePaymentMethodHint
StatementDescriptorResponse
string
The final statement descriptor shown on the buyer statement. This value is calculated per payment method: - Cards: dynamicdescriptor with the GPD prefix. - SEP…
BaseRefundPaymentRequest
object
3 properties 2 required
Currency
string
The processing currency code according to the [ISO-4217 standard](https://en.wikipedia.org/wiki/ISO4217)
SplitsRequest
object
The list of payment splits for the accounts involved in the funds flow. See [how splits work](/monetize/splits) for more information.
2 properties 2 required
StandingInstructionStatus
string
The status of the standing instruction. - new: requested to creation as part of an initial payment. - active: standing instruction is active and can be used fo…
PaymentMethodType
string
The type of payment method.
SplitPercentageAmountCalculated
DateTime
string
UTC timestamp in ISO 8601 format with milliseconds ([RFC 3339](https://www.rfc-editor.org/rfc/rfc3339.html)). Always includes the 'Z' UTC indicator.
FullRefundPaymentRequest
PartialRefundPaymentRequest
ReasonBase
object
Reason of the status of the resource when it requires additional steps or is a failure state.
2 properties 2 required
SplitRemainingAmountCalculated
StandingInstructionDetails
object
The details of the standing instruction the payment is associated with.
4 properties 3 required
RefundOriginBase
object
1 property 1 required
BaseQueryRequest
object
5 properties
UpdatedAt
CreatedAt
PaymentsSortsRequest
array
Fields to sort the data by. If not set, the data will be sorted by the creation date descending.
PaginationAfter
string
Pagination. The cursor from next page will be retrieved.
CardScheme
string
The card scheme.
SplitFixedAmount
CardPaymentMethodHint
SplitAmountMinor
BaseSortItemRequest
object
Each field to sort by.
2 properties 2 required
PaymentOrigin
The origin of the payment creation.
StandingInstructionId
SplitsAccountType
string
The type of account. Exactly one account of type platform and one of type seller are required and allowed per payment.
PaymentMethodBase
object
1 property 1 required
FullRefundPaymentResponse
ProcessingFeeCalculating
PaginationFirst
integer
Pagination. The number of elements that will be retrieved.
StandingInstructionTerms
object
Terms for standing instructions of recurring payments.
1 property 1 required
BasePaymentMethodRequest
object
The payment method configuration for this payment.
1 property 1 required
PaymentOriginBase
object
1 property 1 required
ProcessingFeeRequest
object
The processing fee covered by this account. If not specified, the account will not cover any processing fee. The sum of all processing fees covered by all acco…
1 property 1 required
RefundStatus
string
The status of the refund payment. See the [list, transitions, and description of each status](/payments/refunds/lifecycle) for more details.
GetPaymentResponse
object
18 properties 13 required
CardPaymentMethodDetails
ShortString
string
PaymentTotals
object
The payment totals summary to provide an overview of captured, refunded, refundable amounts and processing fees overall and per account associated with the pay…
6 properties 6 required
PaymentMethodHint
The payment method used.
RefundPaymentRequest
ProblemDetailsBase
object
The Problem Details JSON Object [[RFC7807](https://tools.ietf.org/html/rfc7807)].
4 properties 3 required
Url
string
SellerRef
object
A reference to the seller account.
2 properties 2 required
SddRemittanceInfo
string
The SEPA Direct Debit remittance information shown on the buyer statement.
PaymentStatus
string
The status of the payment. See the [list, transitions, and description of each status](/payments/lifecycle) for more details.
PaymentRefunds
array
A list of refunds associated with the payment if any.
PaymentReason
PaymentId
SubsequentStandingInstructionRequest
object
Standing instruction for recurring payments.
1 property 1 required
PaymentMethodDisplayHint
MediumString
string
RefundType
string
The type of refund to be processed.
AccountLegalName
SplitsType
string
The type of payment split.
BaseRefundPaymentResponse
object
6 properties 6 required
PartyRef
object
A reference to a party account involved in the transaction.
3 properties 3 required
RefundSplitAccount
object
A refund split account.
2 properties 2 required
Id
string
RefundId
SddPaymentMethodRequest
RefundReason
RefundOrigin
The origin of the refund creation.
PaymentAuthentication
object
Information about the authentication performed for the payment if any.
3 properties 2 required
PaymentsFiltersRequest
object
Filtering payments.
4 properties
RefundOriginApi

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

getpaid-payments-api-openapi.yml Raw ↑

Other APIs GetPaid publishes across the network.

GetPaid Accounts API
GetPaid Applications API
GetPaid Authentication API
GetPaid Checkouts API
GetPaid Queries API
Where this information came from

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