Accept payments and fulfill an order once

Choose the integration depth

Install the public payment entry

1. Open Receive in the merchant account

   Choose Checkout link or Accept payments anywhere.

2. Copy the supported code

   Use a normal link for URL-only platforms, an HTML button for custom-code blocks, or a widget where scripts/framing are permitted.

3. Verify the destination

   Open as a customer and inspect the public receiving identity before sharing.

4. Confirm receipt in your account

   Match the actual recorded payment before handing over goods.

<a href="https://bankeiz.com/pay/yourname/?amount=12.30"
   target="_blank" rel="noopener noreferrer">Pay @yourname</a>

<div class="receiz-pay-embed" data-username="yourname"></div>
<script src="https://receiz.com/receiz-pay-embed.js" async></script>

Prepare a trusted card session

import { createReceizClient } from '@receiz/sdk';
import { prepareMerchantCardCheckout, readMerchantCardCheckout }
  from './merchant-checkout';

const receiz = createReceizClient({ baseUrl: 'https://receiz.com' });
const pending = await prepareMerchantCardCheckout(receiz, {
  referenceId: order.id,
  merchantUsername: merchant.username,
  merchantUserId: merchant.userId,
  amountUsdCents: order.amountUsdCents,
});
// Persist pending against the trusted order before exposing frameUrl.
const result = await readMerchantCardCheckout(receiz, pending);
if (result.status === 'paid') {
  // Atomically fulfill this exact order once in your order system.
}

The helper calls payments.embeddedCheckout and reads the existing retained session-status route. It matches session, currency, integer cents, reference, stable merchant UID and accepted positive credit. Keep frameUrl and its short-lived secret out of logs, analytics, public links and model context.

Confirm, do not infer, payment

A success URL, iframe message or customer screenshot is only a signal to inspect the trusted result. Paid requires the accepted terminal paid state and matching connect_payment_checkout credit. Pending means the session remains open; closed means a terminal unpaid result. Trusted host observations are distinct from a self-contained cryptographic receipt; retain actual original proof when independent offline verification is required.

Retries, unknown creation and later services

Serialize session creation per order. referenceId is correlation, not documented idempotency. A lost creation response is uncertain and cannot authorize another session. Reopen the same retained result on return or explicit recovery; this integration requires no recurring polling. Refunds, subscriptions, tax, shipping, inventory, payouts and fulfillment automation require their own admitted contracts, scopes, configured host and qualification. A checkout snippet grants none of them automatically.

• Recover unknown operations ↗
• Qualify your actual deployment ↗