Overview

Glede integrates with procurement and purchase-to-pay systems so buyers can order gift cards from within their own purchasing tool — no manual order entry, no copying of order lines. There are three patterns, and which one you use depends on your procurement system:

Pattern	Protocol	Typical systems	What happens
PunchOut (interactive shopping)	OCI	Basware	Buyer "punches out" to Glede, shops, the cart is returned as NEW_ITEM-* form fields
PunchOut (interactive shopping)	cXML	Coupa, SAP Ariba, Oracle Procurement Cloud, Visma Proceedo	PunchOutSetupRequest → shop in Glede → PunchOutOrderMessage returned
Purchase Order / catalog	cXML	Static/hosted catalogs	Buyer sends a cXML OrderRequest directly to Glede — no shopping session

How PunchOut works (OCI and cXML share this flow)

1. Setup — From their procurement system, the buyer's browser is sent to Glede with a setup request (OCI form POST or cXML PunchOutSetupRequest), authenticated with the credentials Glede issued.
2. Redirect — Glede creates a short-lived session and returns a one-time URL to the Glede shopping flow (send.glede.app/punchout/<token>). The buyer is redirected there.
3. Shop — The buyer chooses gift card amounts, recipients, greeting and branding — the same flow as a normal Glede order.
4. Return cart — On checkout, Glede posts the cart back to the buyer's HOOK_URL as a finished requisition (OCI NEW_ITEM-* fields, or cXML PunchOutOrderMessage).
5. Approve & issue — The requisition is approved in the buyer's own system. For cXML, the approved purchase order is sent back to Glede, which then issues the gift cards.

🔒

Authentication is not the REST API key. Punchout buyers authenticate with per-buyer credentials (cXML shared secret + From identity, or OCI username/password) that Glede provisions.

Getting started: contact Glede to have your credentials and endpoint provisioned, then test end-to-end in the sandbox before going live. Continue to the page that matches your system.