JavaScript is required to view this page
SDKs & Client Libraries

SDKs & Client Libraries

BlinkPay provides official SDKs for multiple languages and platforms. All SDKs are open source and actively maintained.

Available SDKs

SDKRepository
Javagithub.com/BlinkPay/Blink-Payments-API-Client-Java
Node.jsgithub.com/BlinkPay/Blink-Payments-API-Client-Node
.NETgithub.com/BlinkPay/Blink-Payments-API-Client-DotNet
PHPgithub.com/BlinkPay/Blink-Payments-API-Client-PHP

Installation instructions and package names are available in each repository.

E-commerce Plugins

If your store runs on WooCommerce, the BlinkPay NZ for WooCommerce plugin adds Blink PayNow to your checkout without any API integration work.

There are no plugins for other platforms, such as Shopify; use the gateway flow, or an SDK on your server.

Reference Implementations

Snipcart Demo

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

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.

Flutter Demo

Reference Implementation Only

The Flutter Demo is a reference implementation for mobile integration, not a supported SDK package.

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

The demo is a reference for mobile integration in any framework. It uses the Gateway flow with single and enduring consents (not quick payments), and a small backend proxy (Dart Shelf, in server/) that holds the client credentials and obtains access tokens, so no secret is ever in the app. The app opens the Gateway with flutter_custom_tabs (Chrome Custom Tabs on Android, SFSafariViewController on iOS) and receives the customer back through the custom-scheme return link blinkpaydemo://callback, handled with app_links. It runs on iOS and Android; see the deep linking setup in its README.

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