StackProcure
Docs

Guides & articles

Quickstart: Connect your first buyer

Create a vendor, store its secret, sync the catalog, and run a test punchout — end to end, in about fifteen minutes.
How B2B punchout works

cXML 1.2, OCI 5.0, HMAC-signed cart tokens, and the setup → shop → transfer → order round-trip.

Protocols

cXML 1.2 and OCI 5.0 from a single endpoint. Coupa, SAP Ariba, SAP SRM, Prendio, TradeCentric, Oracle iSupplier, Jaggaer, and in-house systems.

Catalog

Your nopCommerce store is the catalog source. StackProcure syncs categories and products and runs the punchout-mode shopping session on top of it.

Security

Per-buyer shared secrets, IP allow-listing, HMAC-signed cart tokens, one-time 30-minute sessions, and a full audit trail.

Endpoint reference

Base URL of your StackProcure instance, e.g. https://portal.stackprocure.com.

POST /api/sp/punchout/setup Receive a cXML PunchOutSetupRequest, authenticate the buyer (shared secret + IP allow-list), and return a PunchOutSetupResponse with the BrowserFormPostURL.
GET /api/sp/punchout/start Entry point the buyer's browser is redirected to; opens the punchout-mode shopping session on your store.
POST /api/sp/punchout/checkout Receive the transferred cart, build the cXML PunchOutOrderMessage, and post it back to the buyer's procurement system.
POST /api/sp/buyers/self-service-register Public buyer self-registration (DUNS + domain validation, rate-limited).
GET /health Liveness probe.

Punchout in four steps

  1. Setup — the buyer's system POSTs a cXML PunchOutSetupRequest; StackProcure authenticates and returns the start URL.
  2. Shop — the buyer browses your nopCommerce catalog in punchout mode.
  3. Transfer — "Transfer Cart" posts the cart to /api/sp/punchout/checkout.
  4. Return — StackProcure builds a PunchOutOrderMessage and posts it back to the buyer's cart.
See pricing Talk to an engineer