Guides developers through uploading a file (PDF, image, spreadsheet) to a Payroc processing account (also called a merchant account) via the Boarding API multipart POST /v1/processing-accounts/{processingAccountId}/attachments endpoint. Use to upload or attach a document to a processing account, submit a supporting document for merchant boarding or compliance, upload a bank statement or banking evidence, attach merchant statements, tax documents, an MPA or amendment, proof of business, financial statements, or identification documents. Also use for how to send a multipart/form-data upload to the /processing-accounts/{id}/attachments endpoint, retrieve attachment metadata, or check an uploaded file's status (uploadStatus). Do NOT use for creating a new processing account, adding a bank or funding account to a merchant, running payments or transactions, or anything not about uploading or retrieving 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 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, 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. Distinct from create-merchant-platform (initial boarding of a brand-new merchant): use 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 (/v1/pricing-intents). Use to: create or reuse a pricing template or fee schedule across 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 (discount rates, gateway fees, PCI non-compliance, chargeback); build, fix (400 errors), update, retrieve, list, or delete a pricing intent; or get a pricingIntentId for a processing account. Do NOT use for taking, authorising, or refunding payments (some gateways call that a "payment intent"), boarding a new merchant (use create-merchant-platform), adding a processing account (use add-processing-account), or general merchant or transaction management. If the user says "payment intent" but wants a reusable fee template, use this skill and confirm.
Guides developers through ordering a physical payment terminal (card reader / PIN pad / POS) for an EXISTING Payroc processing account via the Boarding API (POST /processing-accounts/{processingAccountId}/terminal-orders), and reading the order back. Use to order a terminal or ship a card reader or PIN pad to a merchant, provision hardware for a MID, configure a terminal's settings at order time (batch closure, tips, taxes, receipts, tokenization), build the body for POST .../terminal-orders, check a terminal order's status, list a processing account's terminal orders, retrieve one order (GET /terminal-orders/{id}), specify who pays for the terminal (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. Distinct from add-processing-account (creating the MID itself): use this skill once the processing account exists.