save-a-payment-method
Guides developers through saving and tokenizing customer payment details via the Payroc Secure Tokens API (POST /v1/processing-terminals/{processingTerminalId}/secure-tokens). Use this skill when the user wants to: save a card or bank account for future use without charging it now; tokenize card details into a reusable vault token; store a payment method; implement card-on-file or bank-account-on-file storage; vault a card or ACH/PAD bank account for later use; create a reusable secure-token (secureTokenId) via the /secure-tokens endpoint; save payment details to enable future merchant-initiated charges (recurring, installment, or unscheduled); manage stored tokens (retrieve, list, delete, or update account details); or replace a customer's saved card with a new one. Do NOT use this skill when the user wants to create a single-use token for a one-time transaction (use create-single-use-token), set up or configure recurring billing schedules or payment plans (use set-up-a-payment-plan or manage-subscriptions), charge a customer using a saved token (use run-a-card-sale), or take a bank transfer/ACH payment right now (use take-an-ach-payment).
- Version
- 0.1.1
Pinned to revision a3761e0e5c18, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/save-a-payment-method/SKILL.md
- skills/save-a-payment-method/references/_sources.md
- skills/save-a-payment-method/references/api-schema.md
- skills/save-a-payment-method/references/error-response-format.md
- skills/save-a-payment-method/references/identity-call.md
- skills/save-a-payment-method/references/save-payment-details-guide.md
Every link opens the file at its source, pinned to the revision this page describes.