Priizy Studio

Pilotless first-contact experience for Acceptance Point operators.

Priizy Connect

A four-step path for an Acceptance Point to connect, enroll buyers, test checkout in sandbox, and review before go-live. Studio explains the public contract — it does not grant production access.

  1. 1Connect
  2. 2Wallet
  3. 3Checkout
  4. 4Go-live

Step 1

Connect your Acceptance Point

Connect the Acceptance Point to Priizy using the supported integration package.

  • Add Priizy Connect to your commerce stack.
  • Use the TypeScript integration package or the Vendure reference integration.
  • Start in sandbox, not production.
Technical details

The public integration contract is delivered as a TypeScript integration package, with a Vendure reference integration for commerce stacks that use it.

The optional UCP public surface is published at wallet.priizy.me.

Step 2

Add wallet & enrollment

Let buyers create and use their Priizy wallet without Priizy taking over the Acceptance Point’s customer account.

  • Embed the Priizy wallet/enrollment experience.
  • Buyers authenticate with a passkey.
  • The Acceptance Point keeps ownership of its customer relationship and remains Business/Merchant of Record.
  • Priizy uses an opaque buyer reference rather than requiring the Acceptance Point to hand over customer identity.
Technical details

Wallet and enrollment identifiers such as wallet.priizy.me, me.priizy.wallet, and store_credit belong to the integration package, not the Acceptance Point’s customer account model.

Step 3

Test the checkout lifecycle

Test incentive application safely in sandbox.

  1. 1. Check

    confirm what value is eligible (summary)

  2. 2. Reserve

    lock the value for checkout (reserve)

  3. 3. Confirm

    consume it when the order completes (redeem)

  4. 4. Release / refund

    release on cancellation/failure (void) or handle post-purchase refund (refund)

Technical details

The sandbox lifecycle maps to summary, reserve, redeem, void, and refund.

Split-payment and replay-safe, idempotent request handling are part of the integration package. They are not extra public products.

Step 4

Review before go-live

Sandbox completion does not equal production authorization.

  • Review the integration with Priizy.
  • Confirm operational/commercial setup.
  • Move to production only after Priizy approval.

Priizy keeps campaign governance, funding controls, operational safeguards and reconciliation on the Priizy side.

Request assisted pilotDiscuss go-live
Technical details

Priizy-controlled internals remain off the public Studio surface. That includes ledger, Source Acceptance, funding/liability mutation, Launch Control / LIVE-PAUSE / stage advance, issuance governance, reconciliation, and Priizy intelligence.