Prompt Library

Copy any prompt below and paste it into your AI assistant — with or without the MCP Server connected. Prompts marked with 🔌 get significantly better results when the MCP Server is active, as the AI queries the live spec in real time instead of relying on potentially outdated training data.

🔌

Recommended setup for best results:

1. MCP Server (primary): Configure the Localpayment MCP Server in your AI tool. The AI will automatically call list-endpoints, get-endpoint, search, and fetch to answer with verified, live data.
2. LLMs.txt (fallback): If you're using a chat interface without MCP, paste https://docs.localpayment.com/llms.txt at the start of your session to give the AI a full map of the documentation before asking questions.
3. Plain text articles: For specific topics, append .md to any doc URL (e.g. https://docs.localpayment.com/docs/virtual-accounts-overview.md) and paste the content directly in your prompt.

Using these resources prevents hallucinations and ensures the AI generates code against the actual, current Localpayment API.

Authentication & Token Management

Authentication is required before every Localpayment API call. These prompts cover the full token lifecycle.

📖

If you're starting from zero, the Make your first test payment guide walks through the complete flow step by step — token → payment methods discovery → create payment → webhook → status check — with real curl examples for each call.

🔌 Show me the complete authentication flow for the Localpayment API. How do 
I generate an access token (POST /api/token/), how long does it last, and 
when and how do I refresh it (POST /api/token/refresh/)? Include curl examples 
for both calls and show me the correct way to store and use the token in 
subsequent requests using environment variables.

🔌 My Localpayment API requests are returning 401 Unauthorized. Walk me through 
diagnosing the issue: is my token expired, was it generated incorrectly, or is 
there something wrong with how I'm passing it in the Authorization header? Show 
me how to refresh the token and retry the failed request.

🔌 I'm building a long-running service that makes Localpayment API calls 
continuously. Show me the correct pattern for managing token lifecycle: when 
to proactively refresh before expiry, how to handle 401 responses mid-operation, 
and how to avoid token rotation race conditions in a multi-threaded environment.

Virtual Accounts

🔑

Authentication is always required first. Every Localpayment API call needs a valid Bearer token. Before running any of the prompts below, make sure your integration handles token generation (POST /api/token/) and refresh (POST /api/token/refresh/). See the Authentication guide for details.

The "Full happy path" prompts below include authentication as step 1.

Complete Integration — Happy Path

Use these prompts to build a full Virtual Account integration from creation to reconciliation.

Using the Localpayment API, help me create a CVU virtual account for an 
individual beneficiary in Argentina. Show me the full request with all 
required fields, a complete curl example, and the expected successful 
response. Also explain what the account number returned represents and 
how to share it with the payer.

I have an active CVU virtual account in Localpayment's Stage environment 
with externalId [YOUR_EXTERNAL_ID]. Show me how to simulate an incoming 
payment to this account using the simulate endpoint. Include the curl 
request and explain what webhook payload I should expect to receive.

I received the following webhook payload from Localpayment after a payment 
to a CVU virtual account in Argentina. Explain each field, identify which 
fields I should use to reconcile this payment with my internal records, 
and tell me what the beneficiary.bank.account.number field represents:

[PASTE YOUR WEBHOOK PAYLOAD HERE]

Walk me through the COMPLETE integration flow for CVU virtual accounts 
in Argentina using the Localpayment API. Cover ALL necessary steps:

1. Authentication: generate an access token (POST /api/token/) and 
   explain when and how to refresh it (POST /api/token/refresh/)
2. (Optional) Discover available payment methods for Argentina 
   (GET /api/resources/payment-methods)
3. Create a CVU virtual account (POST /api/virtual-account) for an 
   individual beneficiary — show all required fields and the expected 
   response
4. Verify the account is active: check status 
   (GET /api/virtual-account/{externalId})
5. Share the CVU with the payer and explain what they need to do
6. Simulate an incoming payment in Stage (POST /api/simulate/va)
7. Receive and parse the webhook: identify the key reconciliation fields 
   (especially beneficiary.bank.account.number and tracking object)

Include curl examples for each step. Use Stage environment. Use 
environment variables for all credentials.

Virtual Account Operations

🔌 I need to temporarily disable a virtual account in Localpayment and 
re-enable it later. Show me the API calls for both operations, the required 
parameters, and what status changes I should expect in the webhook.

🔌 I want to delete a virtual account in Localpayment. Explain the 
consequences (is it reversible?), the API call required, and what happens 
to future payments sent to that account after deletion.

🔌 Show me how to create a CVU alias for a virtual account in Argentina. 
Include the format rules, the API request, the asynchronous activation 
flow (INPROGRESS status), and how to verify that the alias is active.

🔌 I need to check the current status of a virtual account including its 
assigned aliases. Show me the Get Virtual Account Status endpoint, 
the full response structure, and how to interpret each status code.

Building Integrations by Country

Start a new country integration

🔌 I want to start accepting payments in [COUNTRY] using the Localpayment API. 
What payment methods are available there? Walk me through the recommended 
integration path, required beneficiary fields, currency, and any 
country-specific considerations I should be aware of.

🔌 I already have a Localpayment integration working for Mexico (SPEI). 
I need to add support for Colombia (Bre-B). What changes do I need to make 
to my existing integration? Are the request structures different? What 
are the key differences in the webhook payload?

Cards

🔌 Help me implement a one-time card payment using the Localpayment API. 
Show me the full request structure, required fields, how to handle the 
response, and what webhook I should expect when the payment is confirmed.

🔌 I want to implement 3D Secure authentication for card payments in 
Localpayment. Explain the flow, the additional fields required in the 
request, and how to handle the redirect and the final webhook notification.

🔌 Show me how to implement card tokenization in Localpayment. I want 
to save a customer's card for future payments without storing the raw 
card data. Include the tokenization request, how to use the token in 
a subsequent payment, and any expiration considerations.

APMs (Alternative Payment Methods)

🔌 I want to implement Pix payments (not virtual accounts) in Brazil 
using the Localpayment APM endpoint. Show me the request structure, 
required fields, and the webhook flow when the payment is completed.

🔌 I want to implement PSE payments in Colombia using the Localpayment API. 
Explain the flow, required fields, and how the redirect to the bank portal 
works. Include the webhook payload for a successful payment.

Debugging Error Codes

I received the following error response from the Localpayment API. 
Explain what it means, what caused it, and how to fix it:

[PASTE YOUR ERROR RESPONSE HERE]

🔌 What does error code [ERROR_CODE] mean in the Localpayment API? 
When does it occur, and what is the recommended fix?

Common error debugging prompts:

🔌 I'm getting error 500 "External ID already used - Duplication" from 
the Localpayment API. Explain why this happens and the correct strategy 
for handling external IDs to avoid duplication in my integration.

🔌 I'm getting error 771 "Your Client Payin Settings have not been 
configured". What does this mean and what steps should I take to resolve it?

🔌 I'm getting error 776 "The alias is already in use" when trying to 
create a CVU alias in Argentina. Explain the alias uniqueness rule and 
how to choose a valid, unique alias.

🔌 I'm getting error 778 "The alias cannot be changed now; you must wait 
24 hours after the last update." Explain the alias change restriction and 
what my options are.

🔌 I'm receiving status 101 OnHold on a payin. What does this status mean, 
when does it occur, and what action (if any) should I take?

Webhooks & Reconciliation

Explain the complete webhook notification flow for Localpayment virtual 
account payments. What fields should I use to match an incoming webhook 
to a specific virtual account and transaction in my system?

I received the following webhook payload and I'm not sure how to reconcile 
it with my internal records. Which fields are the authoritative identifiers, 
and what does each key field mean?

[PASTE YOUR WEBHOOK PAYLOAD HERE]

🔌 What is the difference between externalId and internalId in Localpayment 
webhook payloads? Which one should I use for idempotency checks, and 
which one for support queries?

🔌 Explain the tracking object in Localpayment webhook payloads. What are 
tracking.id, tracking.reference, and tracking.concept? In which countries 
or payment methods is each field most useful for reconciliation?

🔌 My server is receiving duplicate webhook notifications from Localpayment. 
Explain Localpayment's retry mechanism and the correct way to implement 
idempotency in my webhook handler to avoid processing the same payment twice.

Testing & QA

🔌 Generate a comprehensive test suite for my Localpayment virtual account 
integration in [COUNTRY]. Include test cases for: successful payment, 
insufficient funds, invalid beneficiary, duplicate external ID, webhook 
delivery failure, and account status transitions.

🔌 I want to validate that my Localpayment integration covers all required 
fields for [COUNTRY]. Review the API spec and tell me if my request 
payload is missing any required parameters or contains any invalid values:

[PASTE YOUR REQUEST PAYLOAD HERE]

🔌 What are the Stage environment limitations I should be aware of when 
testing my Localpayment integration? Are there features that only work 
in Production?

🔌 Generate a Postman collection for the main Localpayment virtual account 
endpoints: create, get status, enable/disable, delete, and simulate payment. 
Use Stage as the base URL and include example request bodies for Argentina.

Explore the API with MCP Tools

These prompts are designed to work directly with the MCP tools available in the Localpayment server. Use them when you want to navigate the API programmatically rather than asking specific integration questions.

Full API map:

🔌 Using the Localpayment MCP tools, list all available API endpoints organized 
by product area. For each group, briefly explain what it does and give me the 
most important endpoint in that group. I want a complete map of the API.

Discover endpoints for a feature:

🔌 Using search-endpoints, find all API operations related to [TOPIC — e.g. 
"refunds", "subscriptions", "FX", "webhooks"]. For each result, show me the 
HTTP method, path, and a one-line description.

Deep-read a documentation guide:

🔌 Search the Localpayment documentation for "[TOPIC]" and fetch the most 
relevant article. Read the full content and summarize: what the feature does, 
the key parameters, and any important caveats or country-specific notes.

Compare endpoint schemas:

🔌 Use get-endpoint to retrieve the full schema for [ENDPOINT 1] and 
[ENDPOINT 2]. Compare their request structures, required fields, and response 
formats. Highlight the key differences between the two.

Pre-integration checklist:

🔌 I'm about to integrate [FEATURE] for [COUNTRY] using the Localpayment API. 
Before I start coding, use the MCP tools to: 1) find the relevant endpoints, 
2) identify all required fields and validation rules, 3) check for any 
country-specific requirements or restrictions, and 4) list what webhook events 
I should expect. Give me a pre-integration checklist.

Validate a request before sending:

🔌 Before I send this API request to Localpayment, use get-endpoint to read 
the live schema and validate my payload. Tell me if any required fields are 
missing, if any values are in the wrong format, and if there are any 
restrictions I might be violating:

[PASTE YOUR REQUEST PAYLOAD HERE]