Skip to main content
I

Izipay

@codespar/mcp-izipay · v0.2.0-alpha.3

🇵🇪 PeruPaymentsAuth · API Keybeta20 tools5 env varsprerelease

Peru enterprise acquirer (Niubiz-backed — Visa + local banks). Complements Culqi (Peru SMB) for serious-volume Peruvian merchants. Alpha on npm — all endpoint paths best-guess since developers.izipay.pe is contract-gated.

Get started · freeView docs

MIT · runs locally with your own credentials

Limitations

  • v0.2.0-alpha.3 is a prerelease; npm has no stable release of this package.
Package
@codespar/mcp-izipay
Version
0.2.0-alpha.3 · prerelease
npm dist-tag
latest
Category
Payments
Auth
API Key
Country
🇵🇪 Peru
License
MIT
Transport
stdio · streamable-http

Quickstart

Install, set the credentials, make the first call.

Pick your client. The server runs locally over stdio, with your own credentials.

Add the server to your clientOne config entry. No build step, no SDK required.
Set the environment variables5 variables read by this server's code, listed below.
Restart and make the first callThe agent can call any of the 20 tools. Try create_charge first.
terminal
# Claude Code claude mcp add izipay -e IZIPAY_BASE_URL=… -e IZIPAY_ENV=… -e IZIPAY_MERCHANT_CODE=… -e IZIPAY_PASSWORD=… -e IZIPAY_USERNAME=… -- npx -y @codespar/mcp-izipay@0.2.0-alpha.3 # then: /mcp to confirm the server is connected
Environment variables5 variables
IZIPAY_BASE_URLIzipay API base URL. Defaults per IZIPAY_ENV. Override if your contract issues a custom host.optional
IZIPAY_ENVEnvironment: sandbox or production. Defaults to production.optional
IZIPAY_MERCHANT_CODEIzipay merchant code (codigoComercio)required
IZIPAY_PASSWORDIzipay merchant password used to obtain JWTrequiredsecret
IZIPAY_USERNAMEIzipay merchant username issued with your acquirer contractrequired

Names read from the package code (@codespar/mcp-izipay@0.2.0-alpha.3). Descriptions and flags come from its manifest. Self-hosted, you hold the credentials.

First call democreate_charge

"Authorize a card payment. Supports 3-D Secure"

tools/callcreate_chargeresult returned

Tools

What your agent can call.

20 tools, as the package's tools/list returns them.

create_charge

Authorize a card payment. Supports 3-D Secure (3DS) challenge flow when required by issuer/brand. Set capture=true for authorize+capture atomically; capture=false to authorize only and capture later via capture_charge.

capture_charge

Capture a previously authorized charge (when capture=false was used in create_charge).

cancel_charge

Void an authorized-but-uncaptured charge. Does not work on captured charges — use refund_charge for those.

refund_charge

Refund a captured charge. Pass amount for a partial refund; omit for a full refund.

get_charge

Retrieve a charge by Izipay charge id.

tokenize_card

Tokenize a card for PCI-safe reuse. Returns a token_id to pass into create_charge.card.token_id.

delete_token

Delete a stored card token.

create_installment_plan

Create a Peruvian cuotas (installment) plan on a charge. Enables splitting a card payment into N monthly installments, with or without interest, per the issuer's cuota program.

list_transactions

List transactions for reconciliation. Filter by date range and status.

get_settlement

Get the daily settlement batch (liquidación) for a given date. Returns gross, fees, net, and line items that settled to the merchant's bank account.

get_charge_by_order

Retrieve a charge by the merchant-side orderNumber (order_id passed to create_charge). Use when you have the merchant reference but not the Izipay charge id.

list_installment_options

Query available cuota programs for a given card BIN and amount. Returns the list of issuer-offered installment plans (number of cuotas, with/without interest) that can be attached via create_installment_plan.

Names and descriptions come from the package's tools/list (@codespar/mcp-izipay@0.2.0-alpha.3). A kind (read, write, delete) is shown only when the package annotates its tools or each tool was verified one by one; neither exists for this server yet.

Compatibility

MCP is a protocol. Any client that speaks it can mount this server.

The CodeSpar runtime does not route this server. Mount it in your client over stdio · streamable-http.

Protocol

Any MCP client

stdio · streamable-http

Questions

Before you install.

How do I install the Izipay MCP server?

Run npx -y @codespar/mcp-izipay@0.2.0-alpha.3 and add the config block above to your MCP client: Claude Code, Cursor, Claude Desktop, VS Code, or any MCP-compatible client. No build step, no SDK required.

What can my agent do with Izipay?

Izipay exposes 20 tools for payments. Your agent calls them directly; the full list is above.

How does Izipay authenticate, and how are credentials stored?

Izipay uses API Key. Self-hosted, you hold the credentials: the server reads them from its environment variables.

How does Izipay handle upstream API changes?

Every server is versioned independently on npm. The command on this page pins 0.2.0-alpha.3, the version whose tools are listed here; your agent keeps running it until you change the version.

Is Izipay open source? How do I report a bug?

Yes. Izipay is MIT-licensed and published on npm as @codespar/mcp-izipay, source on GitHub (link in the Details panel). Report issues on the package repository; security issues go to security@codespar.dev, and we respond within 24 hours.

Start in seconds.

Add the config above, set the variables, and your agent calls the tools.

Start in seconds demo
Add the server to your client with the config above.
Set the environment variables listed above.
Ask your agent for the first call.
Izipay — MCP server · 20 tools | CodeSpar