Announcement: Tencent Cloud Mini Program Platform Renamed to Tencent Cloud Super App as a Service on January 2, 2025
Console Updates
Android SDK Updates
iOS SDK Updates
Flutter SDK Updates
IDE Updates
Base Library Updates
Direct Purchases of Mini Game Items (Passthrough Mode)
Overview
After the mini program team has bound a merchant, if the mini game 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 game 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:
1. Mini Game virtual payment currently only supports direct in-game item purchases.
2. Direct in-game item purchase refers to a virtual payment method in mini games where players can directly purchase in-game virtual items (such as skins, coins, equipment, etc.) using the virtual payment feature.
Feature modules and directions
1. Enable virtual payment feature
Roles and permissions
Capability | Role | Mini program administrator |
Enable payment-Request permission | ✓ |
Mini Program administrator: Has access to Enable payment module, with the permission to apply for payment feature.
1.1 Select the mini game that needs payment enabled and click Request permission.
1.2 Enter the request message, and click Confirm to submit the request for superapp approval.
Once approved, the virtual payment feature is available and you still need to refer to the direction below for item delivery notification configuration and item adding.
2. Basic configuration
Roles and permissions
Capability | Role | Super admin | Platform admin | Mini program administrator | Mini program senior developer | Mini program developer | Mini program operator |
Delivery notification configuration-view | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ |
Delivery notification configuration-Configure/modify | - | - | ✓ | ✓ | - | - |
Delivery notification configuration-Request certificates and keys | - | - | ✓ | ✓ | - | - |
No-review permission for virtual items-view | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ |
No-review permission for virtual items-Request | - | - | ✓ | ✓ | - | - |
Super admin/Platform admin: Has read-only access to Basic configurations module, and has viewing permissions for Delivery notification configuration and No-review permission for virtual items.
Mini program administrator/Mini program senior developer: Has access to Basic configurations module, viewing permissions for Delivery notification configuration and No-review permission for virtual items, permissions to configure, modify, apply for certificates and keys in Delivery notification configuration, and permission to request no-review permission for virtual items.
Mini program developer/Mini program operator: Has access to Basic configurations module, with viewing permissions for Delivery notification configuration and No-review permission for virtual items.
2.1 Delivery notification configuration
Developers must complete the delivery notification configuration in Virtual payment - Basic configurations to receive mini game item delivery notifications.
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 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 notification configuration is completed, enable notification 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 items releases.”. 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
Capability | Role | Super admin | Platform admin | Mini program administrator | Mini program senior developer | Mini program developer | Mini program operator |
Virtual item list-view | Read-only | Read-only | ✓ | ✓ | ✓ | ✓ |
Virtual item-Download templates | - | - | ✓ | ✓ | ✓ | - |
Virtual item-Add/import/edit virtual items | - | - | ✓ | ✓ | ✓ | - |
Virtual item-Request release | - | - | ✓ | ✓ | - | - |
Virtual item-delete/remove virtual items | - | - | ✓ | - | - | - |
Super admin/Platform admin: Has read-only access to Virtual item management module, with permission to view Virtual item list.
Mini program administrator: Has access to Virtual item management module, with permissions to view Virtual item list, download templates, add/import/edit virtual items, submit release requests, and delete/remove virtual items.
Mini program senior developer: Has access to Virtual item management module, with permissions to view Virtual item list, download templates, add/import/edit virtual items, and submit release requests.
Mini program developer: Has access to Virtual item management module, with permissions to view Virtual item list, download templates, and add/import/edit virtual items.
Mini program operator: Has access to Virtual item management module, with permission to view Virtual item list.
3.1 Add virtual items
In 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
Capability | Role | Super admin | Platform admin | Mini program administrator | Mini program senior developer | Mini program developer | Mini program operator |
Order record-view list/details | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Order record-Export order info | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Super admin/Platform admin/Mini program administrator/Mini program senior developer/Mini program developer/Mini program operator: Has permission for Order record module, has view permissions for Order record - list and details, and has permission to export order info.
When a player purchases a game item in a mini game and completes the payment, the game 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 7 days), with a maximum range of the last 12 months. Refund orders can be searched using the order number or refund number. Exporting detailed data is supported.
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback