Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Tesser Payments API

The Payments API from Tesser — 7 operation(s) for payments.

Tesser Payments API is one of 14 APIs that Tesser 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 getting-started guide, and authentication docs.

This API exposes 9 operations across 7 paths, and defines 40 schemas. It is described by OpenAPI 3.1.0, at version v1.

Requests are made against the base URL https://api.tesser.xyz.

9 operations 7 paths 40 schemas 4 GET1 PATCH4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://api.tesser.xyz
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Tesser Payments API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer). By default, every request must be authenticated.

  • bearer — Enter your JWT token. To obtain a token, make a request to Auth0: bash curl --request POST \ --url https://dev-awqy75wdabpsnsvu.us.auth0.com/oauth/token \ --he…

Paths & Operations 9

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

Payments 9
GET
/v1/payments
Get payments
payments_getPayments 5 params → 200400
POST
/v1/payments
Create payment
payments_createPayment body → 201400
GET
/v1/payments/internal
[INTERNAL] Get payments for UI table
payments_getPaymentsInternal 7 params → 200400
GET
/v1/payments/internal/{paymentId}
[INTERNAL] Get single payment for UI
payments_getPaymentInternal 1 param → 400
POST
/v1/payments/simulate-inbound
Simulate an inbound payment with a chosen risk status (staging)
payments_simulateInbound body → 201202
GET
/v1/payments/{paymentId}
Get payment by ID
payments_getPaymentById 1 param → 200400
PATCH
/v1/payments/{paymentId}
Update payment
payments_updatePayment 1 param body → 200400
POST
/v1/payments/{paymentId}/review
Submit risk review
payments_reviewPayment 1 param body → 200400
POST
/v1/payments/{paymentId}/steps/{stepId}/sign
Sign payment step
payments_signPaymentStep 2 params body → 200400

Schemas 40

The contract defines 40 schemas that model the data the API accepts and returns. The most detailed are InternalPaymentFull (28 properties), LegacyPaymentStep (23 properties), Payment (18 properties), PaymentStep (18 properties). Each schema is shown below with its type and property counts.

PaymentDesiredFromLeg
object
Source side of the payment.
4 properties 1 required
UpdatePaymentDesiredOverlay
object
Account-only update to the payment's desired overlay (two-step PATCH flow).
2 properties 2 required
PaymentStepEstimatedOverlay
object
Planned values for this step.
2 properties 2 required
SignPaymentStepRequest
object
1 property 1 required
UpdatePaymentDesiredFromLeg
object
Source side of the payment (account-only update).
1 property 1 required
PaymentDesiredFromLegResponse
object
Source side.
4 properties 4 required
UpdatePaymentDesiredToLeg
object
Destination side of the payment (account-only update).
1 property 1 required
PaymentActualFromLeg
object
Source side.
4 properties 4 required
PaymentDesiredOverlay
object
Caller's stated intent at creation. Frozen except by the two-step PATCH flow which fills account IDs.
2 properties 2 required
PaymentStep
object
18 properties 10 required
PaymentTableEntity
object
8 properties 2 required
ReviewPaymentRequest
object
1 property 1 required
SimulateInboundPaymentRequest
object
3 properties 2 required
Payment
object
18 properties 14 required
PaymentStepActualToLeg
object
Destination side.
4 properties 4 required
ListPaymentsResponse
object
2 properties 2 required
PaymentDesiredToLegResponse
object
Destination side.
4 properties 4 required
PaymentEstimatedOverlay
object
Tesser's projection for how the payment will proceed.
2 properties 2 required
InternalPaymentFull
object
28 properties 12 required
UpdatePaymentRequest
object
3 properties 2 required
Pagination
object
6 properties 6 required
PaymentStepEstimatedToLeg
object
Destination side.
4 properties 4 required
PaymentActualOverlay
object
What actually settled. Populated once at least one step has status: completed.
2 properties 2 required
StatusReason
object
2 properties 2 required
PaymentDesiredToLeg
object
Destination side of the payment.
4 properties 1 required
LegacyPaymentStep
object
23 properties 11 required
FundingAccount
object
5 properties 2 required
PaymentActualToLeg
object
Destination side.
4 properties 4 required
PaymentStepActualFromLeg
object
Source side.
4 properties 4 required
PaymentEstimatedToLeg
object
Destination side.
4 properties 4 required
CreatePaymentRequest
object
3 properties 1 required
PaymentDesiredOverlayRequest
object
Caller's stated intent for the payment.
2 properties 2 required
PaymentEstimatedFromLeg
object
Source side.
4 properties 4 required
PaymentStepEstimatedFromLeg
object
Source side.
4 properties 4 required
StepFee
object
4 properties 3 required
LegacyPaymentFee
object
4 properties 3 required
RiskStatusReason
object
4 properties 4 required
InternalPaymentListResponse
object
2 properties 2 required
PaymentResponse
object
1 property 1 required
PaymentStepActualOverlay
object
Settled values once the step reaches status: completed. All-null until then; remains all-null on failure.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tesser-payments-api-openapi.yml Raw ↑

Other APIs Tesser publishes across the network.

Tesser Accounts API
Tesser Admin API
Tesser API Keys API
Tesser Counterparties API
Tesser Currencies API
Tesser health API
Tesser MCP API
Tesser Networks API
Tesser Organizations API
Tesser Tenants API
Tesser Treasury API
Tesser Users API