Demo Applications

Explore BlinkPay's capabilities through our live demo applications and reference implementations.

Live Payment Demos

ACME Payments Demo (Sandbox)

Live Demo: acme-sandbox.blinkpay.co.nz

A full-featured e-commerce checkout demo showcasing:

Gateway Flow - Complete payment experience
Multiple Payment Amounts - Test various transaction sizes
Real-time Status Updates - See consent and payment state changes
Error Handling - Examples of timeout, rejection scenarios

How to Use:

Select a product and amount
Click "Pay with BlinkPay"
Choose bank "PNZ" (sandbox bank)
Login with username user01, password password
Approve payment
Return to see payment confirmation

Sandbox Testing

This demo uses the BlinkPay sandbox environment. No real money is transferred, and you can test freely without consequences.

Account Information Demo

ACME Loans Demo

Live Demo: acme-loans-dev.blinkpay.co.nz

Demonstrates Blink Data (account information access):

Account Aggregation - Connect multiple bank accounts
Balance Display - View current and available balances
Transaction History - Access historical transactions
Account Details - See account metadata

How to Use:

Click "Connect Your Bank"
Select bank "PNZ"
Login with username user01, password password
Approve data access
View aggregated account information

Blink Payments only. An Astro shop that takes Blink PayNow at a Snipcart checkout through Snipcart's custom payment gateway. Netlify Functions on the server hold the client credentials and use the Node.js SDK to create a quick payment through the gateway flow, then check its outcome when the customer returns. It is a reference implementation, not a supported plugin; there are no plugins for platforms such as Shopify.

Repository: github.com/BlinkPay/BlinkPay-Snipcart-Demo

Mobile Demo Application

Flutter Demo App

A reference implementation for mobile integration on iOS and Android, useful whatever framework you build in. It is a demo app, not an SDK.

Repository: github.com/BlinkPay/BlinkPay-Flutter-Demo

The app makes Blink Payments single and enduring consents through the Gateway flow. A small backend proxy (Dart Shelf, in server/) holds the client credentials and obtains access tokens, so the secret never reaches the app. The app opens the Gateway with flutter_custom_tabs (Chrome Custom Tabs on Android, SFSafariViewController on iOS) and the customer comes back through the custom-scheme return link blinkpaydemo://callback, received with app_links. The README's deep linking setup covers the platform configuration.

The demo takes shortcuts a production app should not: the app sets the amount and payment reference (your backend must), the app and backend share a fixed demo key instead of your own user authentication, and the consent ID is held only in memory rather than stored on your server. See Mobile Integration.

Testing Credentials

The ACME demos authorise with PNZ, BlinkPay's test bank, using these credentials. No real bank account is involved.

Mock Bank (PNZ)

Bank Name: PNZ (the Gateway tile is labelled PNZ) Username: user01Password: passwordDecoupled auto-approve number: +64-259531933 (in the Gateway, choose Send to PNZ app)

Test Scenarios:

Scenario	Steps	Result
Successful payment (Blink Payments)	Select PNZ → Internet banking website → Login with user01 → Approve	Consent `Authorised`, then the payment completes
Successful data access (Blink Data)	Start a bank connection → select PNZ → Internet banking website → Login with user01 → choose one or more accounts → Approve	Consent `Authorised`; the demo shows the accounts, balances and transactions shared
Decoupled Approval	Select PNZ → Send to PNZ app → enter `+64-259531933`	Consent approved automatically
Decline	Start authorisation → choose Cancel on the PNZ login page, before logging in	Consent `Rejected`; no payment is made and no account data is shared
Timeout	Start authorisation → don't complete it (or use any other mobile number for decoupled) → wait out the bank's window (up to 10 minutes)	Consent `Rejected`