Stage Sandbox is live. Create and retrieve payments against https://payment-gateway.learnagent.cloud with Morphosis HMAC v2. Use only issued sandbox credentials. Production availability is not part of this release.

Accept a payment with one integration

Server-to-server sandbox deposits through one payment resource. MorphosisBlock Payment API v2 gives merchants a small, provider-neutral surface for accepting a deposit on Tron Shasta:

Create one payment for a merchant order.
Show the returned TRX amount and deposit address to the customer.
Track state with webhooks and GET /v2/payments/{payment_id}.
Fulfil only after the payment is paid and your own order checks pass.

The machine-readable contract is OpenAPI 3.1. These guides explain merchant decisions around that contract without adding a second source of API truth.

What you get in the first slice

Capability	Interface	Merchant outcome
Create a payment	`POST /v2/payments`	Receive one payment identifier, quoted TRX amount, and deposit address
Retrieve a payment	`GET /v2/payments/{payment_id}`	Read the latest known payment state
Receive an update	`payment.updated` webhook	Process a signed, deduplicated state notification

Every create request carries a signed Idempotency-Key. Monetary values use decimal strings for display and string-encoded minimum-unit values for exact accounting (minor_units for USD, sun for TRX).

Contract conventions

Convention	Rule
Money	Decimal and minimum-unit values are JSON strings, never floating-point numbers
Time	Timestamps are UTC strings in RFC 3339 format
Settlement	`network` and `asset` remain separate fields inside `payment_instructions`
State	One `status` value represents the current payment lifecycle state
Auth	Requests use Morphosis HMAC v2; webhooks use callback HMAC v1

Integration flow

Obtain sandbox credentials

Ask Morphosis for a Stage Sandbox merchant profile: request key id + HMAC secret, webhook key id + HMAC secret, and a registered webhook URL.

Create one sandbox payment

Submit the merchant order reference and an exact USD amount to POST /v2/payments. Persist the returned payment_id before showing payment instructions to a customer.

Present the quoted deposit

Display the returned TRX decimal amount, its exact sun amount, and the deposit address exactly as received. Do not round, reformat, or substitute another address.

Track the lifecycle

Consume payment.updated events and use GET /v2/payments/{payment_id} when your system needs a fresh view.

Fulfil only after paid

Deliver the purchased product only after the payment state is paid and your own order checks pass.

See it working before you code

Resource	Purpose
Reference cashier	End-to-end TRX checkout that creates payments through Payment API v2
Routing console	Operator view of Payment Gateway routes, including `/v2/payments`
Gateway OpenAPI	Live contract artifact served by the sandbox gateway
Gateway docs stub	SHA-256 of the OpenAPI file currently loaded by the gateway

Boundary

Stage Sandbox only — Tron Shasta testnet funds.
Production cutover, SLA, and commercial terms are out of scope for this release.
Do not send mainnet funds to sandbox addresses.
Do not put signing secrets in browsers, mobile apps, or public repositories.

Continue

Read Sandbox environments for base URLs and operator links.
Follow the Quickstart to sign a real POST /v2/payments call.
Study Authentication before implementing HMAC v2.
Walk the Reference cashier flow.
Review the Payment lifecycle before mapping states to fulfilment.

Getting started

Guides

API reference

Overview

Accept a payment with one integration

What you get in the first slice

Contract conventions

Integration flow

See it working before you code

Boundary

Continue

​Accept a payment with one integration

​What you get in the first slice

​Contract conventions

​Integration flow

​See it working before you code

​Boundary

​Continue

Accept a payment with one integration

What you get in the first slice

Contract conventions

Integration flow

See it working before you code

Boundary

Continue