(Continued)
# 8 Managing Member Cards
# 8.1 Fetching Member Information (Querying Loyalty Points
API Description
This API allows developers to query member information by card_id and code. The member information includes the information for activation, loyalty points, and the balance.
API Request Format
HTTP request method: POSTURL:https://api.weixin.qq.com/card/membercard/userinfo/get?access_token=TOKEN
Parameters
Parameter | Required | Description |
---|---|---|
POST data | Yes | JSON data |
access_token | Yes | Credential for calling the API |
POST Data
{
"card_id": "pbLatjtZ7v1BG_ZnTjbW85GYc_E8",
"code": "916679873278"
}
Parameter | Required | Description |
---|---|---|
cardid | Yes | cardid of a member card |
code | Yes | The code claimed by the queried user. |
Response Data
{
"errcode": 0,
"errmsg": "ok",
"openid": "obLatjjwDolFjRRd3doGIdwNqRXw",
"nickname": "Fourier",
"membership_number": "316510891298",
"bonus": 460,
"sex": "MALE",
"user_info": {
"common_field_list": [
{
"name": "USER_FORM_INFO_FLAG_MOBILE",
"value": "15521328888"
},
{
"name": "USER_FORM_INFO_FLAG_NAME",
"value": "Weixin"
}
],
"custom_field_list": []
},
"user_card_status": "NORMAL"
}
Parameter | Description |
---|---|
errcode | Error code. 0 indicates a successful request. |
errmsg | Error message |
openid | User's unique identifier in this Official Account |
nickname | User alias |
bonus | Loyalty points |
balance | Balance |
sex | User gender |
user_info | Member information |
custom_field_list | The list of member information items set by developer, such as Level. |
name | Member information item name |
value | Member information item value, such as Level. |
user_card_status | Current status of member card. NORMAL: Normal; EXPIRE: Expired; GIFTING: Transferring to another user; GIFT_SUCC: Transferred successfully; GIFT_TIMEOUT: Transfer timed out; DELETE: Deleted; UNAVAILABLE: Unavailable. |
# 8.2 Updating Member Card Information
API Description
This API allows you to change the information and attributes of member cards.
API Request Format
HTTP request method: POSTURL:https://api.weixin.qq.com/card/update?access_token=TOKEN
Parameters
Parameter | Required | Description |
---|---|---|
POST data | Yes | JSON data |
access_token | Yes | Credential for calling the API |
POST Data
{
"card_id": "ph_gmt7cUVrlRk8swPwx7aDyF-pg",
"member_card": {
"background_pic_url": "https://mmbiz.qlogo.cn/mmbiz/0?wx_fmt=jpeg",
"base_info": {
"logo_url": "http:\/\/www.supadmin.cn\/uploads\/allimg\/120216\/1_120216214725_1.jpg",
"color": "Color010",
"notice": "Present this coupon to the waiter at the time of use",
"service_phone": "020-88888888",
"description": "Using with other coupons is not allowed.\nAsk the merchant for an invoice for the group purchase during check-out.\nAvailable for in-store dining only.\nTakeout is offered for leftovers after dining only.\nThis coupon is for 2 persons. You may have to pay a 5-CNY sauce fee for each extra person.\nDo not bring your own drink.",
"location_id_list": [
123,
12321,
345345
]
},
"bonus_cleared": "aaaaaaaaaaaaaa",
"bonus_rules": "aaaaaaaaaaaaaa",
"prerogative": "",
"auto_activate": true,
//You can also enter wx_activate"activate_url":"."
}
}
The following fields can be modified:
base_info:
Parameter | Review Required | Type | Sample Value | Description |
---|---|---|---|---|
title | Yes | string(27) | Weixin member card | The title of the member card, with a maximum of nine Chinese characters. |
logo_url | No | string (128) | http://mmbiz .qpic.cn/ | The merchant's logo on the coupon. The recommended resolution is 300*300 pixels. |
notice | No | string (48) | Present the QR code for coupon redemption | Coupon usage tip, with a maximum length of 16 Chinese characters (32 English characters). |
description | Yes | string (3072) | It cannot be used with other coupons. | Coupon usage instructions |
service_phone | No | string (24) | 40012234 | Customer service phone number |
color | No | string (3072) | Color010 | Coupon color |
location_id_list | No | string (3072) | 1234,2314 | The list of applicable stores that can be updated |
use_all_locations | No | bool | true | Supports all stores. After it is specified, applicable stores are updated with the merchant's stores. |
center_title | No | string (18) | Use Now | The name of the redirection button centered on the member card, acting as a guide to the button usage |
center_sub_title | No | string (24) | Use in Store | The wording for explaining the button centered on the member card. |
center_url | No | string (128) | www.qq.com | The URL to be redirected to from the button centered on the member card. |
custom_url_name | No | string (16) | Use Now | The name of the custom redirect link |
custom_url | No | string (128) | www.qq.com | Custom redirect URL |
custom_url_sub_title | No | string (18) | More Surprises | Words shown to the right of the entry button |
promotion_url_name | No | string (16) | Product Overview | Title of the custom entry button to the promotional page |
promotion_url | No | string (128) | www.qq.com | URL of the external redirect link |
promotion_url_sub_title | No | string (18) | Big Offers! | Words shown to the right of the entry button to the promotional page |
code_type | No | string (16) | CODE_TYPE_TEXT | Code type. CODE_TYPE_TEXT: text; CODE_TYPE_BARCODE: barcode; CODE_TYPE_QRCODE: QR code; CODE_TYPE_ONLY_QRCODE: QR code without numeric code; CODE_TYPE_ONLY_BARCODE: barcode without numeric code; CODE_TYPE_NONE: No QR code and barcode. |
pay_info | No | string (128) | -- | The structural body of the payment feature. For details, see the structure of swipe_card. |
swipe_card | No | string (128) | -- | The structural body of the Quick Pay feature. It includes the is_swipe_card field. |
is_swipe_card | No | bool | true | Specifies whether to display the WeChat Pay interface when the member card is used. |
is_pay_and_qrcode | No | bool | true | Specifies whether the central button on the member card supports both WeChat Pay and the QR code of the member card. |
get_limit | No | int | 1 | The Maximum number of coupons that each user can claim |
can_share | No | bool | false | Indicates whether the coupon claiming page is sharable |
can_give_friend | No | bool | false | Indicates whether the coupon/card can be gifted |
date_info | No | JSON structure | See the example above. | The date of the use. It is the information about the validity period. To modify the validity period, you can extend the effective date range only. |
type | No | int | 1 | The type of the validity period. Only timestamps whose type is 1 can be modified. It cannot be set to 2. |
begin_timestamp | No | unsigned int | 14300000 | The beginning service time. It is applicable only to a fixed date range. It is measured in seconds. |
end_timestamp | No | unsigned int | 15300000 | The ending service time. It is applicable only to a fixed date range. It can be extended only. |
Member card-dedicated fields
Note that the following modifiable fields are not contained in the structure of base_info.
Parameter | Review Required | Type | Description |
---|---|---|---|
background_pic_url | No | string (128) | A custom background picture on the member card. |
supply_bonus | Yes | bool | Indicates whether loyalty points are supported. It can be changed from false to true only. It is false by default. |
bonus_cleared | No | string (3072) | Rules for clearing loyalty points |
bonus_url | No | string (128) | The URL that is redirected to from the loyalty points information item |
balance_url | No | string (128) | The URL that is redirected to from the balance information item |
supply_balance | Yes | bool | Indicates whether top-up is supported. It can be changed from false to true only. It is false by default. This field is available only when the top-up feature is activated. For details, see Obtaining Privileges. |
balance_rules | No | string (3072) | Top-up rules |
prerogative | No | string (3072) | Describes privileges of the member card. |
wx_activate | No | bool | Specifies whether to enable quick activation. Quick activation is supported when it is set to true. For details, see Quick Activation. This field and the activate_url field are mutually exclusive. |
auto_activate | No | bool | Specifies whether to enable automatic activation. When it is set to true, the system automatically activates a member card claimed by a user. For details, see Automatic Activation. |
activate_url | No | string(128) | The activation URL. |
custom_field1 | No | JSON structure | A custom member information item. It is displayed after the member card is activated. |
custom_field2 | No | JSON structure | A custom member information item. It is displayed after the member card is activated. |
custom_field3 | No | JSON structure | A custom member information item. It is displayed after the member card is activated. |
name_type | No | string (24) | The name of a member information item. FIELD_NAME_TYPE_LEVEL: Level; FIELD_NAME_TYPE_COUPON: Coupon; FIELD_NAME_TYPE_STAMP: Stamp; FIELD_NAME_TYPE_DISCOUNT: Discount; FIELD_NAME_TYPE_ACHIEVEMEN: Achievement; FIELD_NAME_TYPE_MILEAGE: Mileage. |
url | No | string (128) | The external redirect URL of an item |
custom_cell1 | No | JSON structure | A custom member information item. It is displayed after the member card is activated. |
bonus_rule | No | JSON structure | The structural body of the loyalty points rules. It is used for Weixin Checkout. |
cost_money_unit | No | int | The purchase amount (accurate to cent) |
increase_bonus | No | int | The loyalty points increased based on the preceding purchase amount |
max_increase_bonus | No | int | The upper limit of loyalty points that a user can obtain per time. |
init_increase_bonus | No | int | The initial loyalty points obtained after activation. |
cost_bonus_unit | No | int | Indicates the loyalty points must be used in an increment of 5. |
reduce_money | No | int | Indicates XX CNY can be redeemed (accurate to cent) |
least_money_to_use_bonus | No | int | A redemption criterion. It specifies the minimum amount (accurate to cent) that is required for redeeming loyalty points. |
max_reduce_bonus | No | int | A redemption criterion. It specifies the maximum number of loyalty points that can be redeemed per purchase. |
discount | Yes | int | The discount offered for this member card. |
Response Data
Example:
{
"errcode":0,
"errmsg":"ok",
"send_check": true
}
Parameter | Description |
---|---|
errcode | Error code. 0 indicates a successful request. |
errmsg | Error message |
send_check | Specifies whether this update needs to be reviewed. The value true indicates review is required, and the value false indicates review is not required. |
Notes
1. When some fields of a voucher are modified, the code will be resubmitted for review. For the specific fields, see the field description. After the voucher is updated, you can call the "View Voucher Details" API to check the update results.
2. Enter the to-be-updated fields only. If fields that cannot be modified, such as brandname, are entered when the API is called, the update will fail.
3. If you update the coupon information by calling this API, call the Homepage to verify whether the update is successful.
# 8.3 Setting Track and Recommendation
Feature description
This feature allows developers to configure coupons or external redirect URLs at the bottom of messages for loyalty points, balance changes, and member card activation. The following figure shows the specific form, which may be a URL or a coupon.
8.3.1 Setting Track and Recommendation
API Description
This API allows developers to gift coupons to users when the users activate member cards and make payments (which can be determined based on changes in the loyalty points and balance).
API details
API Request Format
HTTP request method: POSTURL:https://api.weixin.qq.com/card/update?access_token=TOKEN
Parameters
Parameter | Required | Description |
---|---|---|
access_token | Yes | Credential for calling the API |
POST data | Yes | JSON data |
Configuring a coupon by using a message
{
"card_id": "pbLatjkoa7luhR3zIBjtQiaYtnz4",
"member_card": {
"activate_msg_operation": {
//If the coupon is gifted based on a loyalty points or balance change message, enter modify_msg_operation instead.
"url_cell": {
"card_id_list": [
"pbLatjhcI6XUxJWA0Au3Gaq5eFPs"
],
"end_time": 1492724561,
"text": "Congrats! You are gifted a 50 CNY coupon.",
"url": "www.qq.com"
}
}
}
}
Fields
Field | Required | Description |
---|---|---|
card_id | Yes | Coupon ID |
member_card | Yes | The structural body of the member card. See the example. |
modify_msg_operation | No | A type of recommendation. It represents a coupon gifted based on a loyalty points or balance change message. |
activate_msg_operation | No | A type of recommendation. It represents a coupon gifted based on a member card activation message. |
url_cell | No | The structural body of the recommendation text. See the example. |
card_id_list | Yes | The list of card IDs for the gifted coupons. Common coupons cannot be used with friend-shared coupons. It supports a maximum of 10 card_id values. |
end_time | No | The expiration time of the recommendation. |
text | No | Text content. |
url | No | The redirect URL. This field and the card_id_list field are mutually exclusive. If this field is specified, after tapping details about a template message, the user is redirected to the specified URL to claim the coupon. |
app_brand_id | No | The AppID of the Mini Program to be redirected to. This field and the card_id_list field are mutually exclusive. If this field is specified, after tapping details about a template message, the user is redirected to the Mini Program to claim the coupon. |
app_brand_pass | No | The path to the Mini Program to be redirected to. This field and the card_id_list field are mutually exclusive. If this field is specified, after tapping details about a template message, the user is redirected to the Mini Program to claim the coupon. |
Response Data
{
"errcode":0,
"errmsg":"ok"
}
Fields
Field | Description |
---|---|
Error code | Error code. 0: normal; 43008: the merchant has not activated the permission for WeChat Pay. |
errmsg | Error message |
Notes
Coupons gifted based on loyalty points or balance change messages and coupons gifted based on member card activation messages can be set for a same member card. You need to set them separately.
If you specify the url field after specifying card_id_list, the setting of card_id_list fails to take effect.
If you have specified url, you must allow users to claim the coupon via the specified URL. Otherwise, the merchant is punished for malicious promotion.
# 8.4 Issuing Cards After Payment
8.4.1 Setting Card Issuance After Payment
A merchant who has enabled WeChat Pay can set the system to automatically send a coupon claiming message to a user who pay money to the merchant via WeChat Pay. The user can claim a member card or a coupon by tapping the message.
Currently, this feature is available only when the entity of the merchant ID that has enabled WeChat Pay is the same as the entity of the Official Account that provides the member card. Otherwise, an error occurs. To check whether the corporate entities are the same, log in to
Weixin Official Accounts Platform and choose Account Info to view Entity Info, and go to the homepage of WeChat Pay Merchant Platform to view the entity.
API Description
This API allows merchants to set rules for issuing coupons after payment. Merchants can issue member cards by time ranges and amount ranges.
API Request Format
HTTP request method: POSTURL:https://api.weixin.qq.com/card/paygiftcard/add?access_token=TOKEN
Parameters
Parameter | Required | Description |
---|---|---|
POST data | Yes | JSON data |
access_token | Yes | Credential for calling the API |
POST data for setting Become Member Upon Payment
{
"rule_info": {
"type": "RULE_TYPE_PAY_MEMBER_CARD",
"base_info": {
"mchid_list": [
"123",
"456"
],
"begin_time": 1480317217,
"end_time": 1580317217
},
"member_rule": {
"card_id": "abcdefg",
"least_cost": 2,
"max_cost": 20000,
"jump_url": "www.qq.com"
}
}
}
Fields
Field | Required | Description |
---|---|---|
rule_info | Yes | The structural body of a post-payment promotion rule |
rule_info is in the JSON structure. It contains the following fields:
Field | Required | Description |
---|---|---|
type | Yes | A type of the promotion rule. To enable the Become Member Upon Payment feature, enter RULE_TYPE_PAY_MEMBER_CARD. |
base_info | Yes | The structural body of a promotion rule |
member_rule | No | The structural body of the Become Member Upon Payment feature |
base_info is in the JSON structure. It contains the following fields:
Field | Required | Description |
---|---|---|
mchid_list | Yes | A list of merchant IDs. It is a data array. We recommend that you apply for a maximum of 100 merchant IDs at a time. |
begin_time | Yes | The start time of the rule |
end_time | Yes | The end time of the rule |
member_rule is in the JSON structure. The current settings are specified when the Become Member Upon Payment feature is enabled. It contains the following fields:
Field | Required | Description |
---|---|---|
card_id | Yes | The card ID of the member card to be gifted |
least_cost | Yes | The minimum amount per purchase for gifting a member card (accurate to cent) |
max_cost | Yes | The maximum amount per purchase for gifting a member card (accurate to cent) |
jump_url | No | A merchant-defined web page URL for claiming a member card. If this field is specified, when the Become Member Upon Payment message is tapped, the user can be redirected to the merchant-defined web page to claim the member card. |
app_brand_id | No | The AppID of a merchant-defined Mini Program for claiming a member card. After this field is specified, if the Become Member Upon Payment message is tapped, the user can be redirected to the merchant-defined Mini Program to claim the member card. |
app_brand_pass | No | The path to a merchant-defined Mini Program for claiming a member card. After this field is specified, if the Become Member Upon Payment message is tapped, the user can be redirected to the merchant-defined Mini Program to claim the member card. |
Response Data
Example:
{
"errcode": 0,
"errmsg": "ok",
"rule_id": 1231243,
"fail_mchid_list": [
{
"mchid": "111",
"errcode": 23112,
"errmsg": "err",
"occupy_rule_id": 12332123,
"occupy_appid": "appid"
}
]
"succ_mchid_list": [
"123",
"456"
]
}
Parameter | Description |
---|---|
errcode | Error code. 0 indicates a successful request. |
errmsg | Error message |
rule_id | The ID of the rule that is set at this time. It is used for subsequent modification and deletion. |
succ_list | The mchid list that is set successfully. |
fail_list | The mchid list that failed to be set. |
mchid | The merchant ID that receives the payment. |
occupy_appid | The AppID that is currently using the mchid. If a new rule is to be set for the merchant ID, the merchant needs to be unbound by using this AppID first. |
occupy_rule_id | The rule ID that is currently using the merchant ID. If a new rule is to be set for the merchant ID, the merchant needs to modify or delete the rule ID first. |
Notes
The member card claiming message is sent only once to a single new user. If a user received or claimed a member card before, the message will not be sent to the user repeatedly.
The entity corresponding to the AppID who provides the coupon or coupon with the card_id specified in the rule must be the same as the entity corresponding to the current mch_id. Otherwise, an error 72001 is reported.
To check whether the corporate entities are the same, log in to Weixin Official Accounts Platform and choose Account Info to view Entity Info, and go to the homepage of WeChat Pay Merchant Platform to view the entity.
Only membership coupons are supported. Otherwise, an error 72003 is reported.
When setting the Become Member Upon Payment feature, ensure that the AppID for calling the API must be the AppID for providing the member card. Otherwise, an error 72002 is reported.
Ensure that the merchant ID is currently not used by other AppIDs. Otherwise, an error 72004 is reported, and you need to delete the Become Member Upon Payment rule before calling the API.
A maximum of 10 merchant IDs are supported in the setting at a time. If more than 10 merchant IDs are required, call this API for multiple times.
Q&A
Q: I have a merchant ID and an Official Account. How can I know whether their entities are the same?
A: To check whether the corporate entities are the same, log in to the Weixin Official Accounts Platform and choose Account Info to view Entity Info, and go to the homepage of WeChat Pay Merchant Platform to view the entity.
Q: We are in the group-subsidiary relationship. We want to issue member cards created by the group's Official Account to users who pay money to the subsidiary's merchant ID. However, when we use the subsidiary's AppID to configure a rule for the subsidiary's merchant ID[TH1], an error 72002 is reported when we are setting the group's card_id. What can we do?
A: In this case, you can log in to Weixin Open Platform (https://open.weixin.qq.com/) to link Official Accounts of all subsidiaries to the group's third-party platform account. After that, cards can be issued from both the group's ID and subsidiaries' IDs, and members can be identified by all of them (in other words, the UnionID mechanism is applied).
Q: We are in the group-subsidiary relationship. We want to issue member cards created by the group's Official Account to users who pay money to the subsidiary's merchant ID. However, when we use the group's AppID to configure a rule for the subsidiary's merchant ID, an error 72001 is reported when we are setting the group's card ID. What can we do?
A: In this case, you can log in to Weixin Open Platform (https://open.weixin.qq.com/) to link Official Accounts of all subsidiaries to the group's third-party platform account. After that, cards can be issued from both the group's ID and subsidiaries' IDs, and members can be identified by all of them (in other words, the UnionID mechanism is applied).
8.4.2 Deleting rules for issuing coupons after payment
Deletes a previous "Become Member Upon Payment" rule.
API Description
This API allows merchants to delete a previous rule ID.
API Request Format
HTTP request method: POSTURL:https://api.weixin.qq.com/card/paygiftcard/delete?access_token=TOKEN
Parameters
Parameter | Required | Description |
---|---|---|
POST data | Yes | JSON data |
access_token | Yes | Credential for calling the API |
POST Data
{ "rule_id": 1233}
Fields
Field | Description |
---|---|
rule_id | The name of the "Become Member Upon Payment" rule |
Response Data
Example:
{
"errcode": 0,
"errmsg": "ok"
}
Parameter | Description |
---|---|
errcode | Error code. 0 indicates a successful request. |
errmsg | Error message |
8.4.3 Querying rules for issuing coupons after payment
API Description
This API is usd to query a "Become Member Upon Payment" rule.
API Request Format
HTTP request method: POSTURL:https://api.weixin.qq.com/card/paygiftcard/getbyid?access_token=TOKEN
Parameters
Parameter | Required | Description |
---|---|---|
POST data | Yes | JSON data |
access_token | Yes | Credential for calling the API |
POST Data
{ "rule_id": 11233}
Fields
Field | Description |
---|---|
rule_id | The ID of the rule to be queried. |
Response Data
Example:
{
"errcode": 0,
"errmsg": "ok",
"rule_info": {
"type": "RULE_TYPE_PAY_MEMBER_CARD",
"base_info": {
"mchid_list": [
"123",
"456"
],
"begin_time": 1480317217,
"end_time": 1580317217,
"status": "RULE_STATUS_OK",
"create_time": 1480317217,
"update_time": 1480317217
},
"member_rule": {
"card_id": "abcdefg",
"least_cost": 2,
"max_cost": 20000,
"jump_url": "www.qq.com"
}
}
}
8.4.4 Querying rules for issuing coupons after payment in batch
API Description
This API allows you to query a merchant's "Become Member Upon Payment" rules in batch.
API Request Format
HTTP request method: POSTURL:https://api.weixin.qq.com/card/paygiftcard/batchget?access_token=TOKEN
Parameters
Parameter | Required | Description |
---|---|---|
POST data | Yes | JSON data |
access_token | Yes | Credential for calling the API |
POST Data
{
"type": "RULE_TYPE_PAY_MEMBER_CARD",
"effective": true,
"offset": 0,
"count" : 1
}
Fields
Field | Description |
---|---|
type | Rule type. Enter RULE_TYPE_PAY_MEMBER_CARD. |
effective | Specifies whether to query effective rules only |
offset | Starting offset |
count | Number of batch queries |
Response Data
Example:
{
"errcode": 0,
"errmsg": "ok",
"total_count": 4,
"rule_list": [
{
"type": "RULE_TYPE_PAY_MEMBER_CARD",
"base_info": {
"mchid_list": [
"123",
"456"
],
"begin_time": 1480317217,
"end_time": 1580317217,
"status": "RULE_STATUS_OK",
"create_time": 1480317217,
"update_time": 1480317217
},
"member_rule": {
"card_id": "abcdefg",
"least_cost": 2,
"max_cost": 20000,
"jump_url": "www.qq.com"
}
}
]
}
Notes:
1. The preceding content describes the new API protocol for the Become Member Upon Payment feature. The old API is still available. For the old API protocol, visit the following link:
# 8.5 Setting a Member Card to Support WeChat Pay[TH2]
For member cards that are created via the API and support Quick Pay, users can tap Weixin Checkout to go to the Quick Pay screen for making payments, as shown below
8.5.1 Creating a member card to support WeChat Pay
A merchant can create a member card to support WeChat Pay. To do this, the merchant needs to add the following fields to the JSON of the "Create Member Card" API:
{
"card": {
"card_type": "MEMBER_CARD",
"member_card": {
"base_info": {
"pay_info":
{
"swipe_card":
{
"is_swipe_card":true
}
}
}
}
}
}
For details, see Creating Member Cards.
8.5.2 Updating a member card to support WeChat Pay
A merchant can update an existing member card to support WeChat Pay. To do this, the merchant needs to add the following fields to the JSON of the "Update Member Card" API:
{
"card_id": "ph_gmt7cUVrlRk8swPwx7aDyF-pg",
"member_card": {
"base_info": {
"pay_info":
{
"swipe_card":
{
"is_swipe_card":true
}
}
}
}
}
For details, see Managing Member Cards.
Notes
Before setting this feature, ensure that you have activated WeChat Pay. Otherwise, the API reports an error. (Activating WeChat Pay)
After the API is called to enable a member card to support WeChat Pay, when a user makes payment, you can get the users' OpenID by Querying OpenID via Authorization Code and the member identity of the OpenID by calling the "Get Coupons Received by User" API, and then set the price.
Using WeChat Pay from Member cards is supported as of Weixin 6.3.18. In Weixin earlier than 6.3.18, an upgrade notification is displayed when this feature is to be used.
# 8.6 Other Management APIs
8.6.1 Modifying Inventory
This API is used to increase/decrease the inventory of a coupon. For details, see Managing Coupons.
8.6.2 Querying Code
This API allows developers to view basic information of a member card, including the status of the member card and the OpenID of the user who receives the member card. For details, see Managing Coupons.
8.6.3 Getting Coupons Received by User
This API allows developers to get all coupons under the specified AppID in Cards & Offers. For details, see Managing Coupons.
8.6.4 Checking Coupon Details
This API allows developers to query details about the fields that are passed in when the card_id is created and the review status of the coupon. For details, see Managing Coupons.
8.6.5 Querying Coupons in Batch
This API allows developers to query the list of all coupons under the current AppID for coupon management. For details, see Managing Coupons.
8.6.6 Deleting Member Cards
This API allows developers to delete a card_id from the merchant list for coupon management. For details, see Managing Coupons.
8.6.7 Invalidating Member Cards
This API allows developers to invalidate a use's member card. It is used in scenarios such as refunds. For details, see Managing Coupons.
# 9 Collecting Member Card Data
This API allows developers to fetch data of a member card. For details, see Managing Coupons.
# 10 I Am a Third Party
A third party can develop member cards for the linked merchants. For details, see Third-Party Developer Mode.