Bud Financial Manage Payments API is one of 32 APIs that Bud Financial publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 2 JSON Schema definitions.
Tagged areas include Manage Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 2 JSON Schemas.
This API exposes
6 operations
across 6 paths,
and defines 28 schemas.
It is described by OpenAPI 3.2.0, at version 2.10.10.
Requests are made against a single base URL, https://api-sandbox.thisisbud.com.
6 operations6 paths28 schemas6 GET
Metadata
The identity and technical contract details declared by the specification.
Bud Financial Manage Payments API declares
2 security schemes
for authenticating requests.
It accepts HTTP basic authentication (Basic).
It supports OAuth 2.0 (OAuth2) using the clientCredentials flow.
OAuth2 — Authentication flow: 1. Perform OAuth2 Client Credentials authentication using API Credentials (clientid,clientsecret) to obtain an accesstoken against /v1/oau…
Paths & Operations 6
Across 6 paths, the API surfaces 6 operations — 6 GET. Each is listed below with its method, path, parameters, and response codes.
Manage Payments 6
Manage payments to initiated through Bud's Payments API
The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are StandingOrderData (15 properties), SinglePaymentStatus (14 properties), ScheduledPaymentData (13 properties), PaymentSender (5 properties). Each schema is shown below with its type and property counts.
StatusStandingOrderResponse
object
2 properties2 required
PaymentSender
object
Details of the payment sender
5 properties2 required
ScheduledPaymentData
object
Data structure for the Scheduled Payment object
13 properties11 required
GetScheduledPaymentResponse
object
Response structure when retrieving a specific Scheduled Payment status
3 properties2 required
StandingOrderFrequencyEnum
string
The payment frequency for a Standing Order
BudMonetaryValue
string
The value of the monetary amount. The value is formatted with the number of decimal places for the respective currency. Example: 10.98
ScheduledPaymentStatusCodeEnum
string
The payment status code for a Scheduled Payment
BadRequestResponse
object
Expected response structure
4 properties4 required
PaymentRecipient
object
Details of the recipient of the payment
3 properties3 required
ListStandingOrderResponse
object
Response structure when retrieving a filtered list of Standing Order status'
3 properties3 required
ScheduledPaymentStatusMessageEnum
string
The payment status message for a Scheduled Payment
StandingOrderStatusCodeEnum
string
The payment status code for a Standing Order
KnownCharges
object
A list detailing information surrounding any known charges that may be associated with the payment
2 properties2 required
BudCurrency
string
The three-letter [ISO currency code](https://www.iso.org/iso-4217-currency-codes.html) of the monetary amount. Example: GBP
ListScheduledPaymentResponse
object
Response structure when retrieving a filtered list of Scheduled Payment status'
3 properties3 required
BudAmount
object
The monetary amount.
2 properties2 required
StatusMessageEnum
string
The payment status message
Error
objectnull
Contains a field specific error message
SinglePaymentStatus
object
Detailed information for a given payment and it's status
14 properties14 required
StandingOrderStatusMessageEnum
string
The payment status message for a Standing Order
Errors
object
Contains a list of error messages
PaymentAccountType
string
The account type structure for the payment sender or receiver
SupplementaryStatusDetail
object
The payment supplementary as described by the provider
2 properties2 required
StandingOrderData
object
Data structure for the Standing Order object
15 properties14 required
StatusCodeEnum
string
The payment status code
OperationId
string
A unique identifier/reference associated with a given endpoint/operation
StatusSinglePaymentResponse
object
2 properties2 required
ListSinglePaymentResponse
object
3 properties3 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of Bud Financial Manage 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.
