Overview

Wonder SaaS Platform Integration enables SaaS platforms to connect their merchants' Wonder accounts through a simple, secure QR code authorization flow powered by BizConnect.

What is SaaS Platform Integration?

Traditionally, each merchant using your SaaS platform would need to create their own Wonder App ID and App Secret, then configure those credentials in your system — a manual, error-prone process.

With SaaS Platform Integration:

• You (SaaS Provider) register once: A single Wonder App represents your SaaS platform.
• Merchants authorize in one click: Merchants simply scan a QR code with their Wonder App to grant your platform fixed-permission access to their Wonder account.
• Merchants can revoke anytime: Authorization can be revoked from the Wonder App at any time.

This model is ideal for SaaS platforms serving many small-to-medium merchants who want to use your product with their existing Wonder account.

Key Features

Feature	Description
Fixed per-App scopes	Each SaaS App has a fixed set of permissions (scopes). All merchants who authorize see the same permission set on the confirmation screen.
QR code authorization	Merchants scan a QR code with their Wonder App and tap "Approve" — no credentials to copy-paste.
One-click revocation	Merchants can revoke authorization anytime from within the Wonder App; your platform is notified and sessions are invalidated.
Per-merchant isolation	Each merchant authorization is independent. Data is scoped to the merchant who authorized.
Token-based access	After authorization, your backend receives a user_grant token that can be used to call Wonder business APIs on behalf of the merchant.

How It Works (High Level)

+-----------------+         +-----------------+         +-----------------+
|  SaaS Platform  |         |     Wonder      |         |    Merchant     |
|  (Your System)  |         | BizConnect API  |         |  (Wonder App)   |
+---------+---------+       +---------+---------+       +---------+---------+
          |                           |                           |
          |  1. Get app token         |                           |
          |--------------------------->                           |
          |<--------------------------|                           |
          |                           |                           |
          |  2. Create QR code        |                           |
          |--------------------------->                           |
          |<--------------------------|                           |
          |                           |                           |
          |  3. Display QR code       |                           |
          |     to merchant           |                           |
          |                           |  4. Scan QR code          |
          |                           |<--------------------------|
          |                           |  5. Approve authorization |
          |                           |<--------------------------|
          |                           |                           |
          |  6. Poll for result       |                           |
          |--------------------------->                           |
          |<--------------------------|                           |
          | 7. Get user_grant token   |                           |
          |                           |                           |
          |  8. Call business APIs    |                           |
          |     with the token        |                           |
          |--------------------------->                           |
          |<--------------------------|                           |

Next Steps

1. Read the Authorization Flow guide to understand the QR code authorization process in detail.

Environments

Environment	Base URL	Purpose
UAT	https://api-stg.wonder.app	Integration and testing
Production	https://api.wonder.app	Live traffic

Both environments use separate credentials — your UAT client_id / client_secret will not work in production and vice versa.