Launch checklist

Agree the test tenant and POS with Nexus and the restaurant before submitting orders. This API has no request-level test mode. A successful API response is one part of a complete checkout test.

Verify the customer journey

• Register and enable your webhook before the first test order. Verify signed status and metadata updates reach your backend without polling, then reconcile with GET after a receiver outage.
• Fetch the restaurant’s actual menu and render categories, prices, required choices and unavailable options.
• Submit a simple pickup order; have staff accept it in Register and verify its receipt and Kitchen routing.
• Submit a delivery order with a complete address and the correct fixed delivery fee.
• Submit a combo with defining choices, included components and an extra. Verify quantities, deposits, packaging and total.
• Exercise each payment method you offer. Confirm online payment independently and verify Retail records each method as paid without a second collection or terminal charge.
• Reject an order in Register; show the outcome to the customer and exercise your agreed refund process where applicable.
• Follow status to completion without requiring every intermediate state.

Verify failure and recovery

• Replay an identical confirmed order. Confirm the same intake receipt and no second restaurant order.
• Simulate losing the response after dispatch; recover with the saved connection, ID and body.
• Change a previously reserved body under the same ID and verify order_id_already_used.
• Publish a new menu revision and handle an outdated cart without silently accepting a new price.
• Test pause/resume, opening hours, an unavailable option and an invalid combination. Refresh availability even when the revision is unchanged; verify an identical reserved retry remains recoverable while ordering is paused.
• Enable another POS in Retail, discover it with the same tenant key, and verify its orders reach the selected POS. Keep carts and order history scoped to their original connection.
• Exercise invalid credentials and verify that another tenant’s key cannot access your connections. Verify missing connection IDs return 400 connection_required and disabled or foreign connections return 404 connection_not_found.
• Restart your backend with unconfirmed submissions in its outbox and verify recovery continues.
• Make status polling temporarily fail; show a refresh problem without changing the order to rejected.

Agree the production handoff

Confirm the tenant key for https://website.api.pionier.ro, tenant/location/POS routing, menu publication responsibility, offered fulfillment and payment modes, traffic limits, retry/reconciliation ownership and customer support process with your Nexus contact.

Enable real ordering only after the restaurant confirms that orders, receipts, payment declarations and Kitchen routing reach the intended location. Keep staging keys and test customers out of production configuration.

Integration resources

The reference is generated from the running gateway’s contract. There is no official client SDK in v1; use your HTTP client and the supplied schemas. Examples are integration building blocks, not a complete checkout or durable retry worker.

If using webhooks, verify valid/invalid signatures, duplicate delivery, receiver outages, secret rotation, disabled POS connections and replay of an older sequence.

Additional capabilities to verify

• Change menu language; verify product images, holiday closures and per-product schedules.
• Place a scheduled order, accept it late, and verify its estimate, kitchen timing and printed scheduled note.
• Race cancellation of an immediate order against acceptance; only one may succeed. For scheduled orders, test cancellation before acceptance and after acceptance but strictly before preparation starts, rejection at the cutoff, staff cancellation of active orders, and rejection for completed orders.
• Combine a scoped checkout coupon, multiple bundles, extras, deposits and a staff tip. Reconcile exact totals, coupon allocation and immutable retries; reject a coupon exceeding its eligible base.
• Assign a courier, mark the order ready, report pickup and delivery; confirm this does not trigger another payment.
• Report partial refunds and failed attempts; retry each report and inspect signed notifications after completion.