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

Modern Treasury PaymentOrder API

The PaymentOrder API from Modern Treasury — 4 operation(s) for paymentorder.

Modern Treasury PaymentOrder API is one of 44 APIs that Modern Treasury publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include PaymentOrder. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 6 operations across 4 paths, and defines 29 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against 2 base URLs: http://localhost:3000, https://app.moderntreasury.com.

6 operations 4 paths 29 schemas 2 GET1 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://app.moderntreasury.com/api
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Modern Treasury PaymentOrder API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basic_auth).

Paths & Operations 6

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

PaymentOrder 6
PUT
/api/invoices/{id}/payment_orders/{payment_order_id}
add paymentorderid to invoice
addPaymentOrderToInvoice 2 params → 200404422
POST
/api/payment_orders/create_async
create async payment order
createAsyncPaymentOrder 1 param body → 202403
GET
/api/payment_orders
list payment orders
listPaymentOrders 18 params → 200
POST
/api/payment_orders
create payment order
createPaymentOrder 1 param body → 201400401403409422
GET
/api/payment_orders/{id}
get payment order
getPaymentOrder 1 param → 200404
PATCH
/api/payment_orders/{id}
update payment order
updatePaymentOrder 1 param body → 200404409422

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are payment_order (51 properties), payment_order_create_request (41 properties), payment_order_async_create_request (40 properties), payment_order_update_request (36 properties). Each schema is shown below with its type and property counts.

contact_detail_create_request
object
2 properties
line_item_request
object
4 properties 1 required
payment_order_async_create_request
object
40 properties 4 required
accounting
object
2 properties
ledger_entry_create_request
object
10 properties 3 required
payment_order
object
51 properties 51 required
address
objectnull
11 properties 11 required
foreign_exchange_rate
object
7 properties 7 required
address_request
object
6 properties
payment_order_type
string
One of ach, sebankgirot, eft, wire, check, sen, book, rtp, sepa, bacs, aubecs, interac, neft, nics, nznationalclearingcode, sic, signet, provexchange, zengin.
account_detail
object
9 properties 8 required
virtual_account
object
16 properties 16 required
internal_account
object
24 properties 24 required
error_message
object
1 property 1 required
hold
object
12 properties 7 required
async_response
object
2 properties 2 required
payment_order_create_request
object
41 properties 4 required
payment_order_update_request
object
36 properties
currency
string
Three-letter ISO currency code.
payment_reference
object
7 properties 7 required
ledger_transaction_create_request
object
9 properties 1 required
document_create_request
object
4 properties 1 required
account_capability
object
9 properties 9 required
payment_order_subtype
stringnull
An additional layer of classification for the type of payment order you are doing. This field is only used for ach payment orders currently. For ach payment or…
external_account_type
string
Can be checking, savings or other.
return
object
27 properties 25 required
ledger_account_create_request
object
11 properties 4 required
connection
object
9 properties 9 required
routing_detail
object
11 properties 11 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

modern-treasury-paymentorder-api-openapi.yml Raw ↑

Other APIs Modern Treasury publishes across the network.

Modern Treasury AccountCapability API
Modern Treasury AccountCollectionFlow API
Modern Treasury AccountDetail API
Modern Treasury BalanceReport API
Modern Treasury BulkRequest API
Modern Treasury BulkResult API
Modern Treasury Connection API
Modern Treasury ConnectionLegalEntity API
Modern Treasury Counterparty API
Modern Treasury Document API
Modern Treasury Event API
Modern Treasury ExpectedPayment API
Where this information came from

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