Open Platform
  • 中文
  • EN
取消
en
  • 中文
  • EN
中文
EN
取消
  • Third-party Platform

    • # Introduction to Basic Concepts

    In order to help developers master the development of third-party platforms faster and provide services for merchants based on third-party platforms more efficiently, this article will introduce common terms.

    # I. Different types of ID

    ID Name Introductions
    AppID - AppID is the account ID for different types of products and is the unique identifier for the account.
    - For example, AppID of Official Account message template, AppID of Mini Program, AppID of open platform, AppID of third-party platform, AppID of mobile application, AppID of website application, AppID of Mini Store, etc.
    openid - OpenID is the identity ID of WeChat users on different types of products.
    - WeChat users to access the Official Account message template, Small programs, mobile applications, website applications, small stores, etc. will have a unique openid, but the same WeChat user visits different products to generate openid is also different.
    - For example, for different Official Account message template, the same user has different openidSimilarly, for different Mini Programs, the openid of the same user is also different
    Unions - Unionid is the identity ID of WeChat users' products under the same open platform.
    - If the developer has multiple mobile applications, website applications, and public accounts (that is, official accounts and applets), UnionID can be used to distinguish the uniqueness of users, because as long as the mobile applications and website applications under the same WeChat open platform account And public account, the user's UnionID is unique. That is, the same user has the same UnionID for different applications under the same WeChat open platform.

    Operating in Service Merchant Generation Official Account message template In the scene of Mini programs, the relationship between the open platform account of the merchant and the third-party platform account of the service provider is usually confused. In order to avoid this situation, developers can refer to the following figure to clarify the relationship.

    Distinguish between several concepts

    # 1. the merchant's open platform account VS Open platform account of service provider

    • To be the merchant's Official Account message template、 Mini Program bound to the merchant's open platform account, in order to achieve for the merchant will Official Account message template And the user identity of the Mini Program.
    • Not the merchants. Official Account message template And the Mini Program is bound to the service provider's open platform account to open the identity. In other words, the service provider can not achieve all the merchants Official Account message template And the user identity of the Mini Program. The service provider can only help merchants to bind under the merchant's open platform account. Official Account message template And the user identity of the Mini Program.
    • If the merchant does not have an open platform account, you can first guide the merchant to the WeChat open platform for registration, and then send the merchant's own Official Account message template Small programs are bound to open platforms.
    • In addition, the service provider can also call the interface to create an open platform account for the merchant. Official Account message template And Mini programs.

    # 2. "Binding" VS "Authorization"

    • "Binding" refers to the transfer of the merchant's Official Account message template Or Mini Program account is bound to the open platform of the merchant
    • "Authorization" means that the merchant will place its Official Account message template Or Mini Program scan code authorized to the service provider's third-party platform account
    • For some group enterprises, the application for a third-party platform is to serve the official accounts and Mini Program within the group. For the same company's official account and Mini Program need to have identity access, that is, the need to hang the official account and Mini Program under the same open platform account.
    • However, due to the complexity of the group company's business, it will apply for multiple third-party platform accounts (that is, there will be multiple open platform accounts). In this case, the developer only needs to convert all the Official Account message template And Mini Program tied to an open platform account, multi-application open platform account does not need to bind any more. Official Account message template And Mini programs, just used to create third-party platform accounts can be. The approximate structure is as follows:

    # II. Authorization and Development Mini Programs

    Name of the Mini Program Introductions
    Authorized Small Program (also known as Merchant Little Program) - Merchants can have Mini programs, service providers can also have Mini programs, in order to communicate efficiently, usually the Mini Program of the main business is called the business Mini Program.
    - When a business authorizes its Mini Program to a service provider, it is called an authorized Mini Program.
    - However, merchants can Official Account message template And Mini programs are authorized to service providers, collectively referred to as authorized accounts, refers to the accounts that have been authorized to service providers (including Official Account message template And Small Program Account)
    - The opposite of the authorized account is the service provider account, usually using a third-party platform account to refer to the service provider account.
    Developing a Small Program (aka Template Mini Program) - Merchant Mini Programs are usually eventually released online, becoming a usable application for C-end users.
    - The development of Mini programs is only used by service providers for the preparation of Mini Program code and debugging of Mini programs, which are usually not released online.
    - Because the code of a Mini Program can be copied in batches in countless business Mini programs, the master Mini Program code is also known as the Mini Program template code, and the Mini Program account used to develop the master Mini Program code is the "development Mini Program" account, also known as the "template Mini Program" account.
    - "Development Mini Program" is actually an ordinary Mini Program account, only need to bind the ordinary Mini Program to the third-party platform account is "development Mini Program."

    Pay attention to distinguish several concepts

    # 3, the account is bound to the open platform account VS Connect your account to a third-party platform account

    operation Introductions
    Connect your account to an open platform account - This is usually the behavior of the merchant side, the purpose is to connect the user identity of the application under the same open platform.
    Connect your account to a third-party platform account - This is usually the behavior of the service provider, the purpose is to use the "development of Mini programs" to provide Mini Program services for merchants.
    • The logical relationship is as follows:
    • Screenshot of the operation is as follows:

    # 4、3rdMiniProgramAppid VS extAppid

    Mini Program appid type Introductions
    3rdMiniProgramAppid - Refers to the appid for "developing Mini programs"
    extAppid - Refers to the appid that is licensed to a third-party platform merchant Mini Program.
    - When the service provider wants to personalize the development and debugging of a small business program in the Mini Program template code, it can be completed through this parameter.Third Party Platform Development Instructions

    # 3) Different types of tokens

    Token Name Introductions
    access_Token - Is the use of Official Account message template、 Mini Program, web application or mobile application Appid and secret Generated.
    - use access_Token Calling the official interface refers to the use of merchant identity to call the interface, often used in self-research mode.
    - Official Account message template、 Interfaces for Mini Programs, web applications, and mobile applications all support the use of access_Token Call.
    component_access_Token - Using a third-party platform account. Appid and secret as well as component_verify_ticket Generated.
    - use component_access_Token Calling an official interface refers to the use of vendor identity to call an interface that is only open to the vendor.
    - Some of the interfaces of third-party platforms support the use of component_access_Token Call.
    authorizer_access_Token - Is in the case of authorization from the merchant, the use of component_access_Token And authorized account numbers. authorizer_appid Generated.
    - use authorizer_access_Token Calling the official interface refers to the service provider calling the interface on behalf of the merchant (the service provider acts as a merchant), which is often used in third-party development mode.
    - Official Account message template、 The interface of the Mini Program and some interfaces of the third party platform support the use of authorizer_access_Token Call.
    - Web application, mobile application interface does not support the use of authorizer_access_Token Call.
    • In the case of security protection, in order to reduce the cost of maintaining tokens for developers, the official interface also supports the use of "cloud call" to avoid token calls, details can be found.Cloud Call & WeChat Token。
    • The steps for token generation can be viewedIntroduction to Token Generation。

    # IV. Introduction to Authorized Operations

    Complete a complete authorization, the need for the cooperation of service providers and businesses, the relevant process is as follows, the operation screenshot can be viewedAuthorization and Disauthorization。