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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Tesser

Tesser Payments API

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

Documentation Provider Profile APIs.io OpenAPI GitHub

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.2.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.2.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
PaymentStepActualOverlay
object
Settled values once the step reaches status: completed. All-null until then; remains all-null on failure.
2 properties 2 required
PaymentEstimatedToLeg
object
Destination side.
4 properties 4 required
PaymentResponse
object
1 property 1 required
StepFee
object
4 properties 3 required
StatusReason
object
2 properties 2 required
SimulateInboundPaymentRequest
object
3 properties 2 required
PaymentStepEstimatedOverlay
object
Planned values for this step.
2 properties 2 required
UpdatePaymentDesiredOverlay
object
Account-only update to the payment's desired overlay (two-step PATCH flow).
2 properties 2 required
PaymentDesiredToLeg
object
Destination side of the payment.
4 properties 1 required
PaymentActualToLeg
object
Destination side.
4 properties 4 required
ReviewPaymentRequest
object
1 property 1 required
PaymentStep
object
18 properties 10 required
RiskStatusReason
object
4 properties 4 required
LegacyPaymentFee
object
4 properties 3 required
FundingAccount
object
5 properties 2 required
PaymentStepEstimatedToLeg
object
Destination side.
4 properties 4 required
PaymentDesiredFromLegResponse
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
PaymentDesiredOverlayRequest
object
Caller's stated intent for the payment.
2 properties 2 required
PaymentActualOverlay
object
What actually settled. Populated once at least one step has status: completed.
2 properties 2 required
UpdatePaymentDesiredToLeg
object
Destination side of the payment (account-only update).
1 property 1 required
CreatePaymentRequest
object
3 properties 1 required
InternalPaymentFull
object
28 properties 12 required
Payment
object
18 properties 14 required
PaymentStepActualFromLeg
object
Source side.
4 properties 4 required
PaymentStepActualToLeg
object
Destination side.
4 properties 4 required
InternalPaymentListResponse
object
2 properties 2 required
PaymentStepEstimatedFromLeg
object
Source side.
4 properties 4 required
PaymentEstimatedOverlay
object
Tesser's projection for how the payment will proceed.
2 properties 2 required
PaymentActualFromLeg
object
Source side.
4 properties 4 required
Pagination
object
6 properties 6 required
UpdatePaymentDesiredFromLeg
object
Source side of the payment (account-only update).
1 property 1 required
SignPaymentStepRequest
object
1 property 1 required
PaymentTableEntity
object
8 properties 2 required
ListPaymentsResponse
object
2 properties 2 required
PaymentEstimatedFromLeg
object
Source side.
4 properties 4 required
UpdatePaymentRequest
object
3 properties 2 required
PaymentDesiredToLegResponse
object
Destination side.
4 properties 4 required
LegacyPaymentStep
object
23 properties 11 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
AE Profile APIs.io
Tesser Admin API
AE Profile APIs.io
Tesser API Keys API
AE Profile APIs.io
Tesser Counterparties API
AE Profile APIs.io
Tesser Currencies API
AE Profile APIs.io
Tesser health API
AE Profile APIs.io
Tesser MCP API
AE Profile APIs.io
Tesser Networks API
AE Profile APIs.io
Tesser Organizations API
AE Profile APIs.io
Tesser Tenants API
AE Profile APIs.io
Tesser Treasury API
AE Profile APIs.io
Tesser Users API
AE Profile APIs.io
#Payments
← Back to T APIs
API Details
ID
tesser:tesser-payments-api
Base URL
https://api.tesser.xyz
Docs
https://docs.tesser.xyz
Provider
Tesser
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

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.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=tesser-payments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/tesser-payments-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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 Tesser 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.