order-a-terminal

Guides developers through ordering a physical payment terminal (a card reader / PIN pad / POS device) for an EXISTING Payroc processing account via the Boarding API (POST /processing-accounts/{processingAccountId}/terminal-orders), and through reading the order back. Use this skill whenever the user wants to order a terminal or device, ship a card reader or PIN pad to a merchant, provision hardware for a MID, configure a terminal's gateway/device/app settings (batch closure, tips, taxes, receipts, tokenization) at order time, build the request body for POST .../terminal-orders, check the status of a terminal order, list a processing account's terminal orders (GET /processing-accounts/{id}/terminal-orders), retrieve one order (GET /terminal-orders/{id}), specify who pays for the terminal and how (paymentIntent — merchant or sales partner, hosted payment page / account on file / residual offset), retrieve a payment intent (GET /payment-intents/{id}), or read the provisioned processing terminal and its host-processor configuration — even if they don't say "skill", "terminal order", or "boarding API" explicitly. This is distinct from add-processing-account (creating the MID itself) — reach for this skill once the processing account exists and you have its processingAccountId and want to send it hardware.

Version

0.2.0