P-Card Level 3: Glossary
Short, neutral definitions of the key terms used across the P-Card L3 documentation.
🎭 Actors & scopes
| Term | Definition |
|---|---|
| Buyer | End user entering card details on the PayPage. |
| Storefront (Front) | Your UI that opens the PayPage and polls backend status after submission. |
| Djust backend | Runs tokenization handling, automatic authorization, orchestration, and pre-capture checks. |
| Tenant | Logical customer space; holds settings for PayPage, postbacks, and redirects. |
| Admin scope | API surface for operators (e.g., ADM-SETTINGS-201/500, ADM-PAY-101). Buyers don’t call admin APIs. |
🔄 Flow concepts
| Term | Definition |
|---|---|
| CIT (Customer-Initiated Transaction) | Cardholder is present and initiates payment. All P-Card flows described here are CIT. |
| PayPage | Hosted payment form (redirect or iFrame). Collects card data; your app never handles PAN/CVC. |
| Tokenization | Replaces card details with an opaque token returned via S2S postback. |
| Postback (S2S) | Server-to-server notification to Djust after PayPage completes; triggers Djust’s authorization. |
| Redirect / iFrame returns | Browser redirects after PayPage; UX-only, not a source of truth. |
| Front-end polling | Storefront repeatedly reads order/payment status until a terminal outcome (required). |
| Authorization (auth) | Card hold obtained automatically by Djust after postback; no public auth API. |
| Capture | Settlement of shipped items (can be later, per shipment). Exposed as ADM-PAY-101; details abstracted. |
🧩 Modes & checks
| Term | Definition |
|---|---|
| Full-amount pre-auth | Djust authorizes the order total at payment time, then captures in partials. |
| Per-shipment auth | Djust creates separate authorizations at payment time for shipment groups; captures later. |
| PAY-502 (pre-authorization check) | Your call before payment; validates required identifiers for the FR market (see CF below). |
| Pre-capture check (L3) | Djust validation before each capture to ensure Level 3 completeness and math consistency. |
🧾 Level 3 (data)
| Term | Definition |
|---|---|
| Level 3 (L3) data | Enhanced line-item data (SKU/desc, qty, UOM, unit price, tax/discounts, freight/duty) used for commercial cards. |
| Market ID (CF) | Custom Field stored on Account (role name MARKET_ID); validated by PAY-502. |
| Engagement ID (CF) | Custom Field stored on Order (role name ENGAGEMENT_ID); validated by PAY-502. |
| Capture amount reconciliation | Sum of shipped lines (after discounts/taxes) ± header adjustments must equal the capture amount. |
🛠️ Settings & configuration
| Term | Definition |
|---|---|
| ADM-SETTINGS-500 | GET tenant settings for PayPage/postbacks; returns previews using effectiveRedirectBaseUrl. |
| ADM-SETTINGS-201 | PUT tenant settings (onSuccessPath, onErrorPath, postbackUrl, payPageUrl). |
| payPageUrl | Absolute HTTPS endpoint used by PAY-101. |
| postbackUrl | HTTPS S2S destination where Djust receives tokenization results. |
| effectiveRedirectBaseUrl | Read-only base URL resolved from store_view (used only to compute previews). |
| onSuccessPath / onErrorPath | Relative paths (must start with /) appended to the base URL for UX redirects. |
🧪 APIs (surface only)
| Term | Definition |
|---|---|
| PAY-101 | Create PayPage token (CIT). URLs are settings-driven; do not pass returnPath. |
| ADM-PAY-101 | Capture API (admin). Invoked per shipment when ready; pre-capture L3 check runs inside. |
| PAY-502 | FR pre-auth gate. Must pass before tokenization/authorization. |
🚦 Statuses
| Term | Definition |
|---|---|
| PENDING_AUTHORIZATION | Postback received; Djust is authorizing. Keep polling. |
| AUTHORIZED | Authorization success; proceed in checkout. |
| REFUSED | Issuer decline; offer retry or alternate method. |
Updated 1 day ago