Customer Portal SSO
Open the portal from your app
Your backend submits a signed request, receives a short-lived URL and redirects the customer. Confirm credentials, enablement, phone format and outlet context first.
Read the SSO guide
DevHub
Pixalink Developer HubLoyalty API and integration guides to connect Pixalink to your customer experience.
Bring loyalty into the systems your business already uses. Find the right integration guide, understand the required access and plan how information moves between your application and Pixalink.
Customer Portal SSO
Payments & Refunds API
POS and e-commerce guides
Customer Portal SSO
Signed request
Short-lived portal URL issued
Payments API
Read-only payments and linked refunds
Quick answer
Does Pixalink have a loyalty API?
Yes, for documented jobs. Customer Portal SSO lets your backend sign customers into their loyalty portal with a short-lived URL. A read-only Payments & Refunds API supports reconciliation with an organisation-scoped bearer token. POS, e-commerce and accounting connections each have a setup guide; other access is assessed per use case.
Pixalink Sdn Bhd, Malaysia · Updated 8 November 2026
Developer Hub at a glance
SSO
Signed request, short-lived portal URL, redirect
Payments API
Read-only payments and linked refunds, filtered and paginated
Connections
AutoCount, Bukku, Eats365, Shopify, StoreHub, WooCommerce, Zeoniq and partners
Access
Credentials and enablement confirmed with Pixalink
Choose your integration
Start with a specific job.
Each guide explains what it does, what access it needs and how to test it.
Payments API
Reconcile payments and refunds
A read-only API to retrieve payment records and linked refunds, with filtering, pagination and an organisation-scoped bearer token.
Read the API guide
Integrations
Connect a business system
Guides for AutoCount, Eats365, Shopify, WooCommerce and more, each with its own scope and setup.
AutoCount
Eats365
Shopify
WooCommerce
StoreHub
Loyverse
Browse connections
Customer Portal SSO
How the SSO handoff works.
Your app keeps its own login. Pixalink takes the customer straight into their loyalty portal.
1. Your app
Customer is signed in to your app
2. Signed request
Your backend calls the SSO endpoint
3. Short-lived URL
Pixalink returns a one-time portal link
4. Customer portal
The customer lands in their loyalty portal
Check before you build
API credentials issued for your organisation
SSO enabled for your account
Customer phone numbers in the expected format
The outlet context the customer should land in
A test customer to try the flow end to end
# 1. Your backend (customer already signed in) POST signed SSO request → Pixalink # 2. Pixalink responds { "url": "short-lived portal URL" } # 3. Your app redirect customer → url
Illustrative outline only. Endpoint, fields and signing are in the guide.
Loyalty program integration
POS, e-commerce and accounting connections.
Each connection syncs a defined set of data. Open its guides to see the scope and setup.
Accounting
AutoCount
Customer sync, invoices, points and vouchers
Accounting
Bukku
Link Pixalink to your Bukku company
POS
Eats365
Vouchers, member pricing, QR ordering and credits
E-commerce
Shopify
Memberships, customer sync and points from your store
POS
StoreHub
Points, transactions and troubleshooting
E-commerce
WooCommerce
Connect your online store to your loyalty programme
POS
Zeoniq
Loyalty, vouchers and member pricing
Partners
Loyverse and more
See every POS, payment and technology connection
Workflow
From use case to live connection.
What should happen, for whom, and when.
Credentials, permissions and enablement.
Follow the guide in a test context.
Confirm data flows with your Pixalink contact.
Does Pixalink have a loyalty API?
Yes, for documented jobs: Customer Portal SSO to sign customers in from your app, and a read-only Payments & Refunds API for reconciliation. POS, e-commerce and accounting connections have their own setup guides.
Is there a public API for everything?
No. Use the documented guides. Other access needs an assessment of your use case first.
How is the payments API secured?
With an organisation-scoped bearer token that has payment permissions.
Does SSO create native app screens?
No. It hands signed-in customers into the Pixalink customer portal without a second login.
Which POS systems are supported?
See the connection guides and the Partners page; each connection has its own scope.
How do we get credentials?
Share your use case with your Pixalink contact. Credentials and enablement are confirmed before you build and test.
Ready when you are
Planning a connection?
Share your systems and use case, and we’ll help you scope it.
