Getting started

Intro

Use the Seller API from HTTP, an SDK, or MCP. Every face calls the same public operation with the same auth, permission, idempotency, and errors.

Create a human-rooted service account in the Dashboard.
Grant only the actions you need, then reveal the credential once.
Call retrieveRefund in sandbox with refund_ref.

Live examples are copy-only. Try It on this portal requests a short Trepzy token, calls sandbox directly, and never uses a Mintlify proxy. Continue to auth or the REST reference.

Quickstarts

The seven candidate SDKs share one client shape: explicit sandbox or live, a credential, and a timeout. Snippets in snippets/ compile against that overlay and the conformance sandbox.

const operationId: string = 'retrieveRefund'
const refund_ref: string = 'ref_0123456789AB'

Wire names stay refund_ref and operation_id in every language.

Embed checkout

Create the session on your server so the machine credential never reaches the browser:

const response = await fetch(`${process.env.TREPZY_BASE_URL}/api/v1/checkout-sessions`, {
  method: 'POST',
  headers: {
    authorization: `Bearer ${process.env.TREPZY_API_KEY}`,
    'content-type': 'application/json',
    'idempotency-key': crypto.randomUUID(),
  },
  body: JSON.stringify({ config_ref: 'ckt_0123456789AB', locale: 'en', currency: 'USD' }),
})
const { data } = await response.json()
// Return only data.checkout_session_ref to your browser.

Mount the Trepzy-controlled iframe on the seller page:

<div id="trepzy-checkout"></div>
<script src="https://checkout.trepzy.com/trepzy-checkout-v1.js"></script>
<script>
  const checkout = TrepzyCheckout.create({
    sessionId: 'cks_0123456789AB',
    mount: '#trepzy-checkout',
    onSuccess(event) {
      // Presentation callback only. Retrieve the session/order for commercial truth.
      console.log(event.checkoutSessionRef)
    },
  })
  checkout.mount()
</script>

Before mounting, an operator must propose, approve, and activate the seller’s exact HTTPS origin with the governed product-catalog CLI. There is no default origin. The iframe is refused when the active tenant/environment version does not contain location.origin. Register both the seller top-level origin and the Trepzy checkout origin as Stripe Payment Method Domains; Safari cross-origin wallets also require the SDK-provided allow="payment" iframe permission. Apple Pay and Google Pay buttons are rendered by Stripe only after it reports the wallet available on that browser, device, merchant, currency, and domain. A missing button is an availability result, not a signal to draw a replacement button. PAN/CVC remain inside the Basis Theory Hosted Fields nested in the Trepzy iframe, preserving the seller’s SAQ-A boundary.

Start

Tools

Operations

Getting started

Getting started

Intro

Quickstarts

Embed checkout

​Getting started

​Intro

​Quickstarts

​Embed checkout

Getting started

Intro

Quickstarts

Embed checkout