BlinkPay

BlinkPay - New Zealand Payment Service Integration Documents

This MCP server will help you to connect your e-commerce website or app to BlinkPay Payment Services.

MCP connector

Server URL: https://merchants.blinkpay.co.nz/mcp
Login: None
Protocol: MCP 2025-11-25
Instructions: BlinkPay documentation for Blink Payments (one-off and recurring payments, api "debit") and Blink Data (account data, api "data"), New Zealand open banking.
For a new integration, load the full documentation for the product first: call with api "debit" or "data" and part 1, 2 and so on until the last part. Then use for follow-up questions. lists every page and reads one. Each product's Essentials page (/docs/debit/essentials, /docs/data/essentials) comes first and has the key facts on one page.
gives the exact schema of one API operation; pass sections "request" or "responses" to get only the part you need. The whole specifications are at https://merchants.blinkpay.co.nz/docs/debit/openapi.yaml and https://merchants.blinkpay.co.nz/docs/data/openapi.yaml.
Backend: use an official SDK where one exists for your language (/docs/debit/sdks/overview). Never put client credentials in a mobile app or browser; they belong on your server.
Mobile apps in any framework, including React Native, Swift and Kotlin: read the Flutter reference implementation, https://github.com/BlinkPay/BlinkPay-Flutter-Demo, for the gateway flow, the in-app browser (SFSafariViewController or Chrome Custom Tabs) and return handling, even when building in another language.
Postman collections for both APIs: /docs/shared/reference/postman.
Without MCP: https://merchants.blinkpay.co.nz/docs/llms.txt lists every page, https://merchants.blinkpay.co.nz/docs/debit/llms-full.txt and https://merchants.blinkpay.co.nz/docs/data/llms-full.txt hold each product's full documentation, and any page URL with .md appended is its markdown source.

Tools

Reads data5

Skills

None in the store listings or on the server

MCP connector

Server URL

https://merchants.blinkpay.co.nz/mcp

None

Protocol

MCP 2025-11-25

Instructions

BlinkPay documentation for Blink Payments (one-off and recurring payments, api "debit") and Blink Data (account data, api "data"), New Zealand open banking.

For a new integration, load the full documentation for the product first: call with api "debit" or "data" and part 1, 2 and so on until the last part. Then use for follow-up questions. lists every page and reads one. Each product's Essentials page (/docs/debit/essentials, /docs/data/essentials) comes first and has the key facts on one page.

gives the exact schema of one API operation; pass sections "request" or "responses" to get only the part you need. The whole specifications are at https://merchants.blinkpay.co.nz/docs/debit/openapi.yaml and https://merchants.blinkpay.co.nz/docs/data/openapi.yaml.

Backend: use an official SDK where one exists for your language (/docs/debit/sdks/overview). Never put client credentials in a mobile app or browser; they belong on your server.

Mobile apps in any framework, including React Native, Swift and Kotlin: read the Flutter reference implementation, https://github.com/BlinkPay/BlinkPay-Flutter-Demo, for the gateway flow, the in-app browser (SFSafariViewController or Chrome Custom Tabs) and return handling, even when building in another language.

Postman collections for both APIs: /docs/shared/reference/postman.

Without MCP: https://merchants.blinkpay.co.nz/docs/llms.txt lists every page, https://merchants.blinkpay.co.nz/docs/debit/llms-full.txt and https://merchants.blinkpay.co.nz/docs/data/llms-full.txt hold each product's full documentation, and any page URL with .md appended is its markdown source.