Mini Program Virtual Payment
Last updated:2025-12-22 15:33:11
Overview
After the mini program team has bound a merchant, if the mini program within the team uses virtual payment, the mini program team admin must submit a request to the superapp to enable the payment feature for the mini program in the Commercialization - Virtual payment section in the console. Only after the superapp approves the request can the mini program call the payment capabilities provided by the superapp.
Note:
Mini program virtual payment currently only supports direct in-game item purchases.
Direct in-game item purchase refers to the behavior in mini programs where players use virtual payment to directly buy virtual items, such as memberships, e-books, online music, and digital products.
Feature modules and directions
1. Enable virtual payment feature
Roles and permissions
Feature | Role | Mini program team admin |
Enable payment - Request to enable the payment feature | ✓ |
Mini program team admin: Has access to the “Enable payment feature” module, including the permissions to request to enable the payment feature.
1.1 Select the mini program that needs payment enabled and click Request permission.
1.2 Enter the request message, and click Confirm to submit the request for superapp approval.
After approval, the virtual payment feature will be available for use.
You also need to refer to the process below for configuring delivery push and adding virtual items.
2. Basic configurations
Roles and permissions
Feature | Role | Super admin | Platform admin | Mini program team admin | Senior mini program developer | Mini program developer | Mini program operator |
Delivery push configuration - View | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ |
Delivery push configuration - Configure and modify | - | - | ✓ | ✓ | - | - |
Delivery push configuration - Request certificates and keys | - | - | ✓ | ✓ | - | - |
Approval exemption for virtual items - View | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ |
Approval exemption for virtual items - Request | - | - | ✓ | ✓ | - | - |
Super admin/platform admin: Has read-only access to the basic configurations module, including the permissions to view delivery push configuration and virtual item approval exemption.
Mini program team admin/senior mini program developer: Has access to the basic configurations module, including the permissions to view delivery push configuration and virtual item approval exemption, configure and modify delivery push configuration, as well as request for certificates, keys, and virtual item approval exemption.
Senior mini program developer/mini program operator: Has access to the basic configurations module, including the permissions to view delivery push configuration and virtual item approval exemption.
2.1 Delivery push configuration
Developers must complete the delivery push configuration in Virtual payment - Basic configurations to receive item delivery event notifications from the mini program.
Click Configure, and enter the URLs. When you click Confirm, you will request a certificate and key from the superapp for API security verification.
Parameter description:
URL: The API URL that developers use to receive item delivery notifications. The URL must start with http:// or https://, which supports port 80 and port 443 respectively.
Test URL: A URL for developers to test delivery event notifications.
Request certificate and key: The first save will request a certificate and key from the superapp, which will be emailed to the account's linked email.
After the delivery push configuration is completed, enable item delivery push on the Virtual item management page.
2.2 Request exemption from item release approval
Game items need to be approved by the superapp before they can be released for use. Developers can request the “Approval exemption for virtual item release”. Once the request is approved, the game items can be released without the approval of the superapp.
Note:
Developers need to confirm that game items comply with the superapp's operating specifications. If necessary, the superapp may proactively revoke the approval exemption and remove the game items.
3. Virtual item management
Roles and permissions
Feature | Role | Super admin | Platform admin | Mini program team admin | Senior mini program developer | Mini program developer | Mini program operator |
Virtual items - View | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ |
Virtual items - Download template | - | - | ✓ | ✓ | ✓ | - |
Virtual items - Add, import, and edit virtual items | - | - | ✓ | ✓ | ✓ | - |
Virtual items - Submit release requests | - | - | ✓ | ✓ | - | - |
Virtual items - Delete and remove virtual items | - | - | ✓ | - | - | - |
Super admin/platform admin: Has read-only access to the virtual item management module, including the permissions to view the virtual items.
Mini program team admin: Has access to the virtual item management module, including the permissions to view the virtual items, download templates, add/import/edit virtual items, submit release requests, and delete/remove virtual items.
Senior mini program developer: Has access to the virtual item management module, including the permissions to view the virtual items, download templates, add/import/edit virtual items, and submit release requests.
Mini program developer: Has access to the virtual item management module, including the permissions to view the virtual items, download templates, and add/import/edit virtual items.
Mini program operator: Has access to the virtual item management module, including the permissions to view the virtual items.
3.1 Add virtual items
Go to Virtual payment - Virtual item management, click Add virtual item to add a virtual item.
Enter the virtual item ID, name, price, and image, and click Save.
3.2 Batch import virtual items
You can also download the template, fill in the Excel sheet, and batch import virtual items in the Import virtual items section.
3.3 Virtual item release
Once game items are created, they can be released either individually or in batch. After being released, the information of the game items can be used when the developer calls the virtual payment API.
4. Order record
Roles and permissions
Feature | Role | Super admin | Platform admin | Mini program team admin | Senior mini program developer | Mini program developer | Mini program operator |
Order record - View order list and details | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Order record - Export | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Super admin/platform admin/mini program team admin/senior mini program developer/mini program developer/mini program operator: Has access to the order record module, including the permissions to view the list and details of order records, and export order records.
When a player purchases a virtual item in a mini program and completes the payment, the virtual item purchase order can be checked in Virtual payment - Order record.
5. After-sales record
End users can request refunds for virtual payment orders. After the refund order is generated, it can be queried in Commercialization - Virtual payment - After-sales record. Order data can be queried by the refund initiation date (defaulting to the past seven days), with a maximum range of the last 12 months. Refund orders can be searched by order number or refund number, and detailed data can be exported.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback