Payments

Payments are the core entity in the Tesser platform, representing a transfer of stablecoins from one address to another. Each payment goes through a structured lifecycle with multiple steps.

Payment Lifecycle

Payments in Tesser follow a two-phase process:

1. Payment Intent Creation (/sendPaymentIntent)
2. Payment Execution (/sendPayment)

This separation enables validation and approvals before any funds move.

• Intent Creation
  • Performs balance checks, route planning, and compliance screening
  • May reserve available balance according to policy
  • No funds are moved and nothing is committed on the network at this stage
• Execution
  • Uses the signing keys configured for the organization to authorize transfers
  • Requires explicit initiation/approval by the customer (or their configured signing automation) — Tesser cannot execute unilaterally
  • Results in funds actually moving on the network
  • Triggers any required post-steps (e.g., off-ramp fulfillment)

Note: Payment intent creation requires the entity to have completed KYB. You can create accounts prior to KYB for integration and testing, but they cannot be used to create payment intents until KYB is complete.

Payment Steps

Each payment consists of multiple steps that track the money movement through the system:

• On-Network Transfer: Transfer stablecoins on the underlying network
• Fiat Conversion: Convert stablecoins to/from fiat currency (for on-ramp/off-ramp payments)
• Cross-Network Bridge: Move assets between different networks (when needed)
• Token Swap: Convert between different stablecoins or tokens (when needed)

Steps are tracked individually, allowing you to monitor the exact progress of each money movement operation.

Payment Properties