Skip to content
Weavz
Menu
dLocal

dLocal MCP integration

Create, capture, cancel, refund, and monitor dLocal pay-in payments, payment methods, and signed notifications.

Sign in, add dLocal in Apps, then choose the account your AI can use.

9 tools
1 trigger
Use withChatGPTClaudeClaude CodeCursorCodexMCP clientsSetup guide

Tools

Name
create_payment

Create a dLocal pay-in payment. Use redirect/APM/tokenized methods; do not submit raw card data through this action.

get_payment

Retrieve a dLocal pay-in payment by payment ID.

get_payment_status

Retrieve the current dLocal status for a pay-in payment.

search_payment_methods

List dLocal pay-in payment methods available for a country.

capture_authorization

Capture a dLocal authorization, either fully or partially.

cancel_payment

Cancel a pending payment or uncaptured authorization.

make_refund

Create a dLocal refund for an existing payment.

get_refund

Retrieve a dLocal refund by refund ID.

get_refund_status

Retrieve the status of a dLocal refund.

Triggers

Name
payment_notification_received

Receive dLocal pay-in notifications and verify the V2-HMAC-SHA256 signature when enabled.

Quick Start

TypeScript
import { WeavzClient } from '@weavz-io/sdk'

const weavz = new WeavzClient({ apiKey: 'wvz_...' })

const result = await weavz.actions.execute('dlocal', 'create_payment', {
  workspaceId: '550e8400-e29b-41d4-a716-446655440000',
  integrationAlias: 'dlocal',
  input: { /* ... */ },
})

Related Integrations

Works well with

Frequently Asked Questions

Is there a dLocal MCP server through Weavz?

Yes. Add the dLocal integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 9 dLocal actions.

What can an AI agent do with dLocal?

Available actions include Create Payment, Get Payment, Get Payment Status, Search Payment Methods, Capture Authorization, and more. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.

How do I connect dLocal to Claude or ChatGPT?

Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add dLocal, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.

Can I use dLocal through an API or SDK?

Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.

What authentication does dLocal require?

The catalog lists custom credentials for dLocal. Use Hosted Connect to authorize the intended account. Required permissions, provider app access and available connection methods depend on the integration.

How do I review sensitive dLocal actions?

Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.

What limits or costs apply to dLocal?

Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.

What dLocal triggers are available?

The catalog lists 1 triggers, including Payment Notification Received. Configure the trigger and your event handler before using incoming events to start work.

Connect dLocal in minutes

Get 20,000 free action executions every month. No credit card required.