Connect your checkout
Link a marketplace, store, or other Acceptance Point to Priizy without putting Priizy server credentials in buyer-facing code.
Priizy Connect
Use Priizy Connect with a marketplace, store, or other Acceptance Point. Recognise a buyer’s Priizy wallet privately, check what value is accepted there, and apply the local checkout rules.
Open-source integrations are in development. Vendure, UCP, and WooCommerce have reached engineering complete / publication pending; public packages and the public Connect sandbox are not released yet.
Separate from sandbox. Use this only when you want a production integration conversation — not a trial start and not enrollment.
The simple path
Connect is the integration layer between the Acceptance Point and the same Priizy Core that governs wallet value and its lifecycle.
What Connect does
Priizy Connect provides the link. The Acceptance Point still decides what value it accepts and the rules that apply at checkout.
Link a marketplace, store, or other Acceptance Point to Priizy without putting Priizy server credentials in buyer-facing code.
Use a scoped wallet relationship for that Acceptance Point instead of exposing a global buyer ID or another channel’s identity.
The Acceptance Point stays in control of which value it accepts and how much can be used for that checkout.
How it connects
Checkout at an Acceptance Point (marketplace or store) collects cart and rule context. Buyer-facing code never holds Priizy server credentials.
The platform adapter evaluates that context and talks to Core. Vendure, UCP, and WooCommerce are accepted initial-v0.1 engineering surfaces — each is engineering complete / publication pending. Medusa remains post-v0.1 and is not yet implemented. Saleor remains future / evidence-gated. None are publicly installable.
Core applies Acceptance Point rules, wallet lifecycle, and measurement. This page does not expose Core, Ops, or admin URLs.
At checkout
Connect resolves the buyer’s scoped wallet relationship for this Acceptance Point.
Priizy evaluates the cart, available wallet value, and the Acceptance Point’s active rules.
Eligible value can be reserved and applied while blocked value remains unavailable.
Completion redeems the reserved value; failed or reversed transactions follow the lifecycle rules.
Scoped identity
An Acceptance Point can recognise the wallet relationship through its own scoped mapping. It does not need a global Priizy buyer ID or another channel’s identity. Acceptance remains local: a wallet balance is not a promise that every checkout will accept every source.
Integrations
Implementation maturity is shown separately from public installability. Engineering status does not mean a package is publicly available.
Checkout adapter for Vendure Acceptance Points (marketplaces and stores). Initial v0.1 engineering is complete; public package publication is pending. Not a public package and not installable from a registry.
Agentic checkout compatibility so agents can request the same rule-governed evaluation as a storefront. Initial v0.1 engineering is complete; public package publication is pending. Not a public package.
Acceptance Point integration path for WooCommerce checkout. Initial v0.1 engineering is complete; public plugin publication is pending. Not a public plugin.
Commerce adapter for Medusa storefronts. Post-v0.1 — not part of the initial v0.1 release set and not yet implemented. There is no public install path.
Shown only as a future / evidence-gated platform. There is no Saleor adapter to evaluate, implement, or install today.
Production onboarding
Tell us what commerce platform or checkout you operate and we can discuss the right integration path. Production onboarding is separate from a future public sandbox.
Separate from sandbox. Use this only when you want a production integration conversation — not a trial start and not enrollment.
Developer trial
The public Connect sandbox and package quickstart are not released yet. Starting a future sandbox will be a technical trial, not enrollment and not production onboarding.
A public Priizy Connect sandbox is not available yet. This control stays disabled until a real Connect/Vendure integration sandbox or package quickstart exists. Priizy Studio is a separate commercial simulator — not this sandbox.
Quickstart and GitHub stay visible but disabled until public destinations actually exist. Priizy Studio remains a separate planning simulator, not the Connect sandbox.
Public docs and package quickstart stay unlinked until a public destination exists. No install command is published yet.
A GitHub CTA will appear here only when a public Connect repository exists. No public source destination is linked today.
Priizy Studio is a commercial simulator and pilot-design surface. It is not a Priizy Connect sandbox and not a technical Vendure integration environment. Values shown there are simulation/planning only.