Guides developers through uploading a document file (PDF, image, spreadsheet, etc.) to a Payroc processing account (also called a merchant account) via the Boarding API multipart POST /v1/processing-accounts/{processingAccountId}/attachments endpoint. Use this skill when the user wants to upload or attach a document to a processing account, submit a supporting document file for merchant boarding or compliance, upload a bank statement or banking evidence document, attach merchant statements, tax documents, an MPA or amendment, proof of business, financial statements, personal identification documents, or any other file attachment to a Payroc processing account. Also use when the user asks how to use the /processing-accounts/{id}/attachments API endpoint, how to send a multipart/form-data upload to a processing account, how to retrieve attachment metadata or check the status of a previously uploaded file, or how to check the uploadStatus of an attachment. Do NOT use for creating or registering a new processing account, adding a bank account or funding account to a merchant, running payments or transactions, or any operation that does not involve uploading or retrieving file attachment metadata for an existing processing account.
Guides developers through adding a processing account (a new MID) to an EXISTING merchant platform via the Payroc Boarding API (POST /merchant-platforms/{merchantPlatformId}/processing-accounts), and through retrieving, listing, and sending signing reminders for processing accounts. Use this skill whenever the user wants to add another processing account, provision a new MID for an already-boarded merchant, add a store / location / outlet / DBA to an existing merchant platform, onboard a second business line under the same merchant, build the request body for POST .../processing-accounts, retrieve or list a merchant platform's processing accounts (GET /processing-accounts/{id} or GET /merchant-platforms/{id}/processing-accounts), look up a processing account's owners, contacts, funding accounts, or pricing agreement, or prompt a merchant to sign their pricing agreement (reminders) — even if they don't say "skill", "processing account", or "boarding API" explicitly. This is distinct from create-merchant-platform (initial boarding of a brand-new merchant) — reach for this skill when the merchant platform already exists and you have its merchantPlatformId.
Guides developers through creating a new merchant platform record via the Payroc Boarding API (POST /v1/merchant-platforms). Use this skill when the user wants to board a new merchant, onboard a merchant, register a merchant with Payroc, create a merchant account or merchant platform, implement the boarding flow, or work with the /v1/merchant-platforms endpoint. Also use when the user is building a boarding integration, asking how to submit merchant data to Payroc, generating a boarding request payload, asking about MID provisioning, merchant registration, owner/control-prong requirements, pricing agreements, or signature capture during boarding — even if they don't use the word "skill" or "boarding API" explicitly.
Guides developers through creating and managing pricing intents — reusable Merchant Processing Agreement (MPA) fee templates — via the Payroc Boarding API (POST/GET/PUT/PATCH/DELETE /v1/pricing-intents). Use this skill whenever the user wants to: create or reuse a pricing template / fee schedule across many merchants; choose a pricing program (interchange plus, interchange plus plus, tiered, flat rate, consumer choice / surcharge / cash discount, reward pay choice); define processor, gateway, base, or ACH fees (transaction or discount rates, gateway monthly/setup/per-transaction fees, annual, PCI non-compliance, or chargeback fees); build, fix (including 400 validation errors), update, replace, retrieve, list, or delete a /v1/pricing-intents request; or obtain a pricingIntentId to assign to a processing account during boarding — even if they don't say "skill" or "pricing intent" explicitly (for example, they describe reusing one fee structure for many merchants). A pricing intent is a fee *template* and never takes, authorises, captures, or refunds money. Do NOT use this skill for taking, authorising, or refunding payments or transactions — some gateways call that a "payment intent", but Payroc handles it via its separate transactions/payments API — nor for boarding a merchant end-to-end or adding processing accounts (use create-merchant-platform), nor for general merchant or transaction management. If the user says "payment intent" but clearly wants a reusable fee template, use this skill and confirm.
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.