Payment Management
Last updated: 2025-11-13 15:42:17
Overview
Starting from version 2.2.2, we have enabled payment-related capabilities. If your superapp supports payment capabilities and can provide them to mini program or mini game merchants released on your superapp, you can enable the payment feature via Superapp management - Payment management - Payment configuration. Once the payment feature is enabled, the mini program team can submit a request to the superapp to bind a merchant.
Prerequisites
Before enabling the payment feature, you need to ensure that your superapp meets the following requirements:
The superapp has implemented or integrated a third-party payment channel.
The payment channel supports merchant management.
Enable the payment feature
On the Superapp management - Payment management - Payment configuration page, enable the payment feature.
Payment configuration
Roles and permissions
Capability | Role | Super admin | Platform admin | Superapp administrator | Superapp senior developer | Superapp developer | Superapp operator | Review staff |
Payment configuration-Enable/Disable payment feature and set payment currency | Read-only | Read-only | ✓ | - | - | - | - |
Payment configuration-Add/Edit merchant | Read-only | Read-only | ✓ | ✓ | - | - | - |
Search/view the merchant list | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ | ✓ |
Super admin/Platform admin: Has read-only access to Payment configuration module.
Superapp administrator: Has access to Payment configuration module, with permissions to enable/disable payment feature, set payment currencies, add/edit merchant, and search/view the merchant list.
Superapp senior developer: Has access to Payment configuration module, with permissions to add/edit merchant and search/view the merchant list.
Superapp developer/Superapp operator/Review staff: Has access to Payment configuration module, with permissions to search/view the merchant list.
Enable payment feature
When enabling the payment feature, it is required to set the currency supported by the superapp.
Payment signature verification method description:
Responsibilities of the superapp | Passthrough mode |
1. Signature verification | The superapp verifies the signature of the payment request to ensure the integrity and authenticity of the request. |
2. Key management | The superapp provides the public and private keys and certificates required for signing and verification, ensuring their security. These keys and certificates are delivered offline to the mini game developers and do not go through SAS. |
3. Payment information verification | The superapp verifies the order details and business parameters in the payment request to ensure that the payment operation can be executed normally. |
Note:
When you enable the payment feature, you need to select the payment currency supported by the superapp. Currently, you can only set one currency, and it cannot be changed after it has been saved.
Merchant binding approval
Roles and permissions
Capability | Role | Super admin | Platform admin | Superapp administrator | Superapp senior developer | Superapp developer | Superapp operator | Review staff |
Pending list-view list/details | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ | ✓ |
Pending list-Approve | - | - | ✓ | ✓ | - | - | ✓ |
Approved list-view list/details | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ | ✓ |
Bound list-view list/details | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ | ✓ |
Bound list-unbind merchant IDs | - | - | ✓ | ✓ | - | - | - |
Super admin/Platform admin: Has read-only access to Merchant binding approval module and cannot approve or unbind merchant IDs.
Superapp administrator/Superapp senior developer: Has access to Merchant binding approval module, can view the list and details of Pending, Approved, and Bound merchant IDs, and has the authority to approve requests to bind merchant and unbind merchant IDs.
Superapp developer/Superapp operator: Has access to Merchant binding approval module, can view the list and details of Pending, Approved, and Bound merchant IDs, but cannot approve requests to bind merchant or unbind merchant IDs.
Review staff: Has access to Merchant binding approval module, can view the list and details of Pending, Approved, and Bound merchant IDs, has the authority to approve requests to bind merchant, but cannot unbind merchant numbers.
After the payment feature is enabled in the superapp and a merchant is added, the mini program team can request to bind the merchant. The merchant binding request is displayed under the Merchant binding approval list. The superapp team admin or approvers can click Approve to approve the request.
Note:
Please ensure that the merchant ID belongs to the merchant associated with the mini program team. This is critical for payment transaction security, so proceed with caution.
Unbind
The superapp can unbind the merchant from the mini program team.
Payment feature approval
Roles and permissions
Capability | Role | Super admin | Platform admin | Superapp administrator | Superapp senior developer | Superapp developer | Superapp operator | Review staff |
Payment feature approval-Pending-view list/details | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ | ✓ |
Payment feature approval-Pending-Approve | - | - | ✓ | - | - | - | ✓ |
Payment feature approval-Approved-view list/details | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ | ✓ |
Payment feature approval-Enabled-view list | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ | ✓ |
Payment feature approval-Enabled-Disable payment feature | - | - | ✓ | - | - | - | - |
Super admin/Platform admin: Has read-only access to Payment feature approval module and cannot approve or disable the payment feature.
Superapp administrator: Has access to Payment feature approval module, can view the 'Pending/Approved/Enabled' lists and details in Payment feature approval, and has permission to approve and disable the payment feature.
Superapp senior developer/Superapp developer/Superapp operator: Has access to Payment feature approval module, can view the 'Pending/Approved/Enabled' lists and details in Payment feature approval, but cannot approve or disable the payment feature.
Review staff: Has access to Payment feature approval module, can view the 'Pending/Approved/Enabled' lists and details in Payment feature approval, has permission to approve the payment feature, but cannot disable the payment feature.
Pending
Since the payment feature involves financial transactions for superapp users, not all mini programs or mini games can freely integrate it. If a mini program or mini game needs to use this feature, it must submit a request to the superapp for approval.
The superapp will check the mini program or mini game information and determine whether to approve or reject the request.
Approved
The approved or rejected requests can be found in the Approved list.
Enabled
The mini programs and mini games with the payment feature enabled can be found in the Enabled list. If abnormal transaction data or violations are detected in a mini program or mini game, the mini program team admin or approvers can disable its payment feature by clicking Disable in the Operation column.
Virtual item approval
Roles and permissions
Capability | Role | Super admin | Platform admin | Superapp administrator | Superapp senior developer | Superapp developer | Superapp operator | Review staff |
Virtual item approval-Pending-view list/details | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ | ✓ |
Virtual item approval-Pending-Approve | - | - | ✓ | ✓ | - | - | ✓ |
Virtual item approval-Approved-view list/details | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ | ✓ |
Virtual item approval-Released-view list/details | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ | ✓ |
Virtual item approval-Released-Remove | - | - | ✓ | ✓ | - | - | - |
Super admin/Platform admin: Has read-only access to Virtual item approval module and cannot approve or remove virtual items.
Superapp administrator/Superapp senior developer: Has access to Virtual item approval module, can view the Pending/Approved/Released lists and details, and has the permissions to approve and remove virtual items.
Superapp developer/Superapp operator: Has access to Virtual item approval module, can view the Pending/Approved/Released lists and details, but cannot approve or remove virtual items.
Review staff: Has access to Virtual item approval module, can view the Pending/Approved/Released lists and details, has the permission to approve virtual items, but cannot remove them.
Pending
The virtual item release requests submitted by mini games are displayed in the Pending list. The mini program team admin or approvers can approve the requests.
They will check the virtual item details to see if it contains illegal information and if the price is reasonable.
Approved
The approved and rejected requests can be found in the Approved list. Click Details to view the details of the request and approval.
Released
The released virtual items for mini games are displayed in the Released list. The superapp team admin or approvers can remove the virtual items.
Management of virtual item releases with approval exemption
Generally, virtual items for mini games need to be approved by the superapp before they can be released for use. Mini game developers can request “Approval exemption for virtual items releases” from the superapp admin. Once the request is approved, the virtual items can be released without the approval of the superapp.
The request can be approved by the superapp team admin or approvers.
Note:
After the request is approved, the virtual items can be released without the approval of the superapp, which means there are no restrictions on releasing virtual items for mini games. Please use this feature with caution and regularly review whether the mini game content remains secure and compliant.
Roles and permissions
Capability | Role | Super admin | Platform admin | Superapp administrator | Superapp senior developer | Superapp developer | Superapp operator | Review staff |
No-review permission management-Pending-view list/details | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ | ✓ |
No-review permission management-Pending-Approve | - | - | ✓ | ✓ | - | - | ✓ |
No-review permission management-Approved-view list/details | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ | ✓ |
No-review permission management-Approved-Disable | - | - | ✓ | ✓ | - | - | ✓ |
Super admin/Platform admin: Has read-only access to No-review permission management module, cannot approve requests for Approval exemption for virtual items releases, and cannot disable virtual item release exemption permissions.
Superapp administrator/Superapp senior developer/Review staff: Has access to No-review permission management module, has permissions to view the Pending/Approved lists and details, can approve virtual item release exemption requests, and can disable virtual item release exemption permissions.
Superapp developer/Superapp operator: Has access to No-review permission management module, has permissions to view the Pending/Approved lists and details, cannot approve virtual item release exemption requests, and cannot disable virtual item release exemption permissions.
View order record
For mini programs or mini games with the payment feature enabled, payment orders generated by superapp users within the mini program or mini game can be found in Order record.
Roles and permissions
Capability | Role | Super admin | Platform admin | Superapp administrator | Superapp senior developer | Superapp developer | Superapp operator |
Order record-view list/details | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ |
Order record-export | - | - | ✓ | ✓ | ✓ | ✓ |
Super Admin/Platform Admin/Superapp administrator/Superapp senior developer/Superapp Developer/Superapp operator: Have permissions for Order record module, with permission to view the order record list and details, as well as the permission to export order info.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback