Getting Started with BlinkPay

BlinkPay is New Zealand's first purpose-built open banking payment gateway, owned by Bank of New Zealand. We provide secure, direct account-to-account payment solutions and data access through our suite of APIs.

Using an AI coding assistant? Connect it to the BlinkPay MCP server, which has all of this documentation and the API schemas.

What is BlinkPay?

BlinkPay connects your business directly to New Zealand's major banks (ANZ, ASB, BNZ, Kiwibank, and Westpac), enabling:

• Instant Payment Initiation - Customers pay directly from their bank accounts
• Recurring Payments - Set up automated payment schedules with enduring consents
• Account Information Access - Retrieve customer account data with their consent
• No Screen Scraping - Direct bank integrations with two-way authentication
• Bank-Grade Security - ISO 27001:2022 certified with encrypted data

Our Products

Blink PayNow

One-off payment initiation for single transactions. Perfect for e-commerce checkouts, invoices, and one-time payments.

Learn more about Single Payments →

Blink AutoPay

Recurring payment capabilities with enduring consents. Ideal for subscriptions, instalments, and regular billing.

Learn more about Recurring Payments →

Blink Data

Account information API for accessing customer account data, balances, and transaction history with explicit consent.

Learn more about Blink Data →

Blink Gateway

Our hosted payment gateway that simplifies integration by handling bank selection and authentication flows for you.

Learn more about Gateway →

Quick Start

Ready to integrate? Here's how to get started:

1. Get API Credentials - Sign up at merchants.blinkpay.co.nz; your sandbox client ID is under Settings > API Settings, where Rotate Secret shows the secret once (see Getting API Credentials)
2. Choose Your Integration - Select between Gateway Flow (easiest), Redirect Flow, or Decoupled Flow
3. Authenticate - Obtain OAuth 2.0 access tokens using client credentials
4. Create Consents - Request payment or data access consent from customers
5. Process Payments - Initiate payments once consent is authorised

View the Quick Start Guide →

Integration Approaches

Gateway Flow (Recommended)

BlinkPay hosts the payment experience, handles bank selection, and manages authentication flows. Easiest integration with the best user experience.

Learn about Gateway Flow →

Redirect Flow

Browser-based flow where customers are redirected to their bank and back to your site after authorisation.

Learn about Redirect Flow →

Decoupled Flow

Customers authorise payments on a different device or at a different time using their banking app.

Learn about Decoupled Flow →

Developer Resources

• API Documentation - Complete API reference with interactive docs
• Client SDKs - Java, Node.js, .NET and PHP SDKs, plus a Flutter demo app as a mobile reference implementation (not an SDK)
• Postman Collection - Pre-configured API requests for testing
• Demo Applications - See BlinkPay in action with working examples

Sandbox Environment

Test your integration in our sandbox environment before going live:

• Sandbox Base URL: https://sandbox.debit.blinkpay.co.nz
• Mock Bank: Test with the "PNZ" bank using username user01 and password password; see Sandbox Test Values for the decoupled number and how to produce declines and revocations
• No Real Money: Safe testing environment with simulated banking responses

Bank Coverage

BlinkPay connects to all major New Zealand banks:

• ANZ New Zealand
• ASB Bank
• Bank of New Zealand (BNZ)
• Kiwibank
• Westpac New Zealand

Each bank supports different authentication flows and features. View detailed bank coverage →

Security & Compliance

• ISO 27001:2022 Certified - International information security management standard
• No Screen Scraping - Direct bank APIs only, no credential storage
• Encrypted Data - All data encrypted in transit and at rest
• Two-Way Authentication - Strong customer authentication required
• Open Banking Standards - Built on New Zealand's open banking framework

Learn more about our security approach →

Integration Standards

Before you go live, read Credential and Integration Security for how to store credentials and handle payment outcomes safely, and, if you use the redirect or decoupled flow directly rather than the Gateway, Consent Experience for Direct Flows for what your consent screens must show.

Support

View all support resources →

Next Steps