Mcp Izipay

io.github.codesparPublished by GitHub account codesparv0.2.0-alpha.3Updated Oct 24, 2026

MCP server for Izipay — Peru enterprise acquirer (Niubiz): authorize/capture/refund, cuotas

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

MCP server for Izipay (Niubiz), Peru's enterprise card acquirer, letting an assistant authorize, capture, refund and reconcile card payments.

What you can do
  • Authorize, capture, void, refund and look up card charges, including by merchant order number
  • Tokenize cards and delete stored card tokens
  • Create and query cuotas installment plans and available installment options
  • List transactions and retrieve daily settlement batches over a date range
  • Create and fetch hosted payment links, and start Yape or Plin payments
  • Complete 3-D Secure challenges and create or cancel recurring subscriptions
When to use it
Useful for Peruvian merchants with a direct Izipay/Niubiz acquirer contract who want an assistant to handle payment operations, reconciliation lookups, installment planning or subscription management from chat. Not aimed at small self-serve setups; the README positions it for enterprise volume.
Requirements
Runs locally as an npm package (Node.js) over stdio, or optionally over HTTP with MCP_HTTP and MCP_PORT. Requires IZIPAY_USERNAME, IZIPAY_PASSWORD and IZIPAY_MERCHANT_CODE from an acquirer contract; IZIPAY_ENV selects sandbox or production (defaults to production) and IZIPAY_BASE_URL can override the host. Network access to the Izipay API is needed.
Before you install
The package is an alpha release and its endpoint paths are described as best-effort guesses that should be validated against your integration kit before going live. It handles real money: charges, captures, refunds, subscriptions and payment links move funds. It needs merchant credentials including IZIPAY_PASSWORD, and IZIPAY_ENV defaults to production, so a misconfigured run can hit live systems. Card tokenization and 3-D Secure handling touch sensitive payment data.

Installation

In SourceWeft

  1. Open Mcp Izipay in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@codespar/mcp-izipay

MCP server for Izipay — Peru's enterprise acquirer.

Izipay is the merchant-facing brand of Niubiz (Visa + Peruvian banks joint venture), the largest card acquirer in Peru with 20%+ share. Niubiz/Izipay is the default for enterprise merchants with serious volume and a direct acquirer contract.

Positioning vs Culqi

@codespar/mcp-culqi@codespar/mcp-izipay
SegmentPeru SMBPeru enterprise
TypePSP (Stripe-analog)Acquirer (Niubiz)
OnboardingSelf-serveCommercial contract
CustomersD2C, SaaS, startupsRetail chains, airlines, utilities, banks

Peruvian merchants with serious volume typically have an Izipay acquirer contract before they adopt a PSP — different customers, different contracts, different commercial terms. The two servers complement each other.

Status: alpha

This is 0.1.0-alpha.1. Izipay's developer portal at developers.izipay.pe is contract-gated — the public homepage advertises the API but the full REST reference is only available to contracted merchants. The endpoint paths in this server are best-effort inferences from Izipay's public SDK repositories (github.com/izipay-pe) and common Niubiz/Izipay REST conventions. Every endpoint below should be validated against your integration kit before going live, and corrections are welcome via PR.

Best-guess endpoints (unverified)

ToolMethodPath
auth (internal)POST/auth/login
create_chargePOST/v1/charges
capture_chargePOST/v1/charges/{id}/capture
cancel_chargePOST/v1/charges/{id}/cancel
refund_chargePOST/v1/charges/{id}/refund
get_chargeGET/v1/charges/{id}
tokenize_cardPOST/v1/tokens
delete_tokenDELETE/v1/tokens/{id}
create_installment_planPOST/v1/installments
list_transactionsGET/v1/transactions
get_settlementGET/v1/settlements/{date}

Tools (20)

ToolPurpose
create_chargeAuthorize a card payment.
capture_chargeCapture a previously authorized charge (when capture=false was used in create_charge).
cancel_chargeVoid an authorized-but-uncaptured charge.
refund_chargeRefund a captured charge.
get_chargeRetrieve a charge by Izipay charge id.
tokenize_cardTokenize a card for PCI-safe reuse.
delete_tokenDelete a stored card token.
create_installment_planCreate a Peruvian cuotas (installment) plan on a charge.
list_transactionsList transactions for reconciliation.
get_settlementGet the daily settlement batch (liquidación) for a given date.
get_charge_by_orderRetrieve a charge by the merchant-side orderNumber (order_id passed to create_charge).
list_installment_optionsQuery available cuota programs for a given card BIN and amount.
list_settlementsList settlement batches across a date range.
create_payment_linkCreate a hosted payment link (pay-by-link).
get_payment_linkRetrieve a payment link by id.
pay_yapeInitiate a Yape direct payment.
pay_plinInitiate a Plin direct payment.
authenticate_3dsComplete a 3-D Secure challenge.
create_subscriptionStart a recurring card charge (subscription).
cancel_subscriptionCancel an active subscription.

Install

bash
npm install @codespar/mcp-izipay@alpha

Environment

bash
IZIPAY_USERNAME="..."       # merchant usernameIZIPAY_PASSWORD="..."       # merchant password (secret)IZIPAY_MERCHANT_CODE="..."  # codigoComercioIZIPAY_ENV="production"     # or "sandbox"IZIPAY_BASE_URL="..."       # Optional override

Defaults:

  • IZIPAY_ENV=production → https://api.izipay.pe
  • IZIPAY_ENV=sandbox → https://sandbox-api.izipay.pe

Authentication

JWT Bearer. On the first API call the server POSTs { username, password, merchantCode } to /auth/login, caches the returned JWT in memory, and attaches it as Authorization: Bearer <jwt> on every subsequent request. The cached JWT is refreshed 60s before expiry. Transparent to callers.

Run

bash
# stdio (default)npx @codespar/mcp-izipay
# HTTPMCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-izipay

Enterprise

Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.

License

MIT

Source: packages/payments/izipay/README.md at commit d0a519a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0-alpha.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts