Method for preventing false subscription of value added service of IPTV (Internet Protocol Television)

Abstract

The invention relates to the technical field of IPTV (Internet Protocol Television) value-added services, in particular to a method for preventing false ordering of an IPTV value-added service, which comprises an operator, an SP (Service Provider), a cashier desk, a payment plug-in, a user data interface and the IPTV, a user browses the value-added service provided by the SP through an IPTV set top box and initiatively initiates an ordering request based on the own demand, and when the SP receives the ordering request of the user, the SP sends the ordering request to the IPTV. A payment plug-in is called, the payment plug-in is a unique cashier entrance, real equipment of a user is recognized through technologies such as equipment fingerprints, the authenticity of a request source is ensured, the payment plug-in carries a cached unique equipment identifier, a background interface of a cashier is accessed, and the background of the cashier executes multiple verifications; according to the method, false violation ordering behaviors are accurately recognized and intercepted in time, violation ordering is blocked before ordering is completed, economic losses of users are avoided, bad debt losses of operators are reduced, the operators can intercept malicious violation ordering in advance, trust of the users to the operators can be increased, and user stickiness can be increased.

Description

Technical Field

[0001] This invention relates to the field of IPTV value-added services technology, and in particular to a method for preventing fraudulent subscriptions to IPTV value-added services. Background Technology

[0002] In the IPTV service ecosystem, operators collaborate with numerous service providers (SPs) to offer users a wide range of value-added services. When subscribing to these services, users can choose to pay with their phone bill. Upon receiving the subscription request, the SP opens the operator's payment gateway via a URL to complete the subscription. However, some unscrupulous SPs, in an effort to increase their own subscription volume, will use illegal methods to simulate genuine user activity and maliciously subscribe to unwanted services. Users are only notified when the illegal subscription is completed or they receive a notification of deduction, resulting in direct financial loss. This is primarily due to the easily accessible URLs used by the payment gateway, which can be exploited by unscrupulous operators. Attackers aim to exploit vulnerabilities to carry out precise fraud, with the risk directly linked to economic losses. While adding verification steps such as SMS verification codes or image verification codes in ordering scenarios can, to some extent, prevent unauthorized orders by simulating users and improve the authenticity of the operation, it significantly alters the current ordering process. Due to the complexity of remote control input, verification code methods increase the complexity of user operations and ordering time, leading to the loss of ordering users. Furthermore, since SMS verification codes or image verification codes can still be forged, intercepting SMS messages and cracking image verification codes through technical means can bypass security protections, making it impossible for the cashier to identify and prevent unauthorized orders in a timely and effective manner, resulting in user complaints. Summary of the Invention

[0003] In view of the shortcomings of the prior art described above, the purpose of this invention is to provide a method for preventing fraudulent subscriptions of value-added services in IPTV, which solves the problem of how to prevent the risk of illegal subscriptions in SP value-added service scenarios in the prior art.

[0004] To achieve the above and other related objectives, the present invention provides the following technical solution: A method for preventing fraudulent subscriptions to value-added services on IPTV, comprising operators, service providers (SPs), cashiers, payment plugins, user data interfaces, and IPTV, specifically including the following steps: a. The user browses the value-added services provided by the SP through IPTV and initiates a subscription request; b. After receiving the user's order request, the SP calls the payment plugin, which is the only cashier entry point; c. The payment plugin parses the SP request parameters and obtains user information and ordered business information. At the same time, it collects device hardware information such as IMEI and MAC address, software environment such as system version, installed application list, network characteristic IP address, generates a unique device identifier, caches the generated unique device identifier, and simultaneously encrypts and reports it to the user data interface, carrying the cached unique device identifier, as well as the user information and ordered business information in the order request, and accesses the cashier backend interface. d. The user data interface receives user data reports, parses request parameters, and obtains plaintext information; e. The backend of the cashier performs multiple verifications; f. If the verification passes, the user is redirected to the payment page. After confirmation, the order is completed and the SP value-added content is returned. If the verification fails, the order request is intercepted, the callback address is returned, and an exception is displayed.

[0005] To implement the above technical solution, users browse value-added services provided by SPs through IPTV set-top boxes and proactively initiate subscription requests based on their own needs. When the SP receives a user's subscription request, it invokes the payment plugin, which serves as the unique payment gateway. Using technologies such as device fingerprinting, it identifies the user's actual device, ensuring the authenticity of the request source. The payment plugin parses the SP's request parameters and obtains user information and subscription details. Simultaneously, it collects device hardware information such as IMEI, MAC address, and set-top box serial number; software environment information such as system version, payment plugin version number, and installed application list; and network IP address characteristics. This generates a unique device identifier, which is then cached and encrypted before being reported to the user data interface. If a device is detected to be... In root mode, a device error message is returned directly, and the ordering process is terminated. This ensures the authenticity and integrity of the request source. The payment plugin carries a cached unique device identifier, as well as user information and ordering business information from the order request. It then accesses the cashier's backend interface, where the cashier performs multiple checks to accurately identify and promptly block fraudulent and irregular ordering behavior. By blocking irregular orders before they are completed, the system avoids financial losses for users and reduces bad debt losses for operators. The ability of operators to intercept malicious and irregular orders in advance increases user trust and user stickiness. This does not change the existing ordering page or the ordering operation steps that users are accustomed to, avoiding complex operations such as input and switching on the page and minimizing the impact on the user's ordering experience.

[0006] In one embodiment of the present invention, in step b, the operator's cashier only opens the standard encrypted interface that interfaces with the payment plugin, and closes all direct access methods that bypass the payment plugin and do not require plugin encryption verification, including but not limited to public URLs, unencrypted HTTP interfaces, API interfaces not bound to plugin signatures, and anonymous access interfaces, thereby cutting off unauthorized client access paths.

[0007] To achieve the above technical solution, the payment plugin serves as the sole entry point to the cashier, cutting off access paths for unauthorized clients and using technologies such as device fingerprinting to identify the user's real device and ensure the authenticity of the request source.

[0008] In one embodiment of the present invention, the payment plugin adds screenshots of user operation behavior and reports them through an encrypted interface, providing a basis for manual review by operations personnel.

[0009] In one embodiment of the present invention, after the payment plugin is loaded, an Observable sequence of periodic timed tasks is created after a 3-second delay. The current screen is captured every 5 seconds and reported to the data interface. The 3-second delay is used to avoid the peak period of plugin loading resource consumption.

[0010] In one embodiment of the present invention, in step d, after the request parameters are verified to be correct, the order information is saved, and the user information is stored in Redis. The expiration time is set to 15 minutes. The screenshot information is received and the signature is verified. If the signature verification fails, the process is returned directly. If the signature verification is successful, the screenshot is renamed to the current time accurate to milliseconds, cached in Redis, and the expiration time is set.

[0011] In one embodiment of the present invention, the primary key of the order information is the transactionID, a request parameter of the SP to launch the payment plugin; the key of the Redis cached user information is the request parameter transactionID + user account; and the key of the Redis cached image information is the transactionID, a request parameter of the SP to launch the payment plugin.

[0012] In one embodiment of the present invention, the multi-factor authentication of the cashier in step e specifically includes: parameter integrity authentication, encryption key validity authentication and obtaining the user's real account through decryption, user account status authentication, user online information authentication, blacklist authentication, user-reported data authentication, screenshot existence authentication, and order authentication.

[0013] To implement the above technical solution, necessary parameters cannot be empty. The encryption key is verified for validity, and the user's real account is obtained through decryption. During user account status verification, the system determines if the current account is active; users in abnormal states are prohibited from ordering, the order callback address is returned, and an abnormal user status message is displayed. User online information is verified to determine if the order is fraudulent. During blacklist verification, the operator's user blacklist interface is used to determine if the user is on the blacklist; blacklisted users are prohibited from ordering, the user is redirected to the order callback address, and an abnormal message is displayed. During user-reported data verification, the cached user-reported data is retrieved based on the request parameter `transactionID`, and device information, user information, and order information are verified. If the user-reported data is missing, or the device, user, and order information do not match, the system will take corrective action. The system automatically redirects the user to the order callback address and displays an error message. During screenshot existence verification, it retrieves the screenshot information reported by the payment plugin based on the request parameter `transactionID` to determine if the image exists and traces the user's activity. If the image does not exist, the user is redirected to the order callback address and an error message is displayed. During order authentication, the system verifies the legality of the value-added service, the match between the user account and the ordered content, and the compatibility of the payment method with the ordered service. The cashier backend performs verifications according to priority levels to accurately identify and promptly block fraudulent ordering behavior. Before the order is completed, it prevents illegal orders from being placed, avoiding economic losses for users and reducing bad debt losses for operators.

[0014] In one embodiment of the present invention, the parameter integrity verification includes ensuring that the necessary parameters requested by the payment plugin from the cashier backend are not empty. Specifically, the request transaction ID, order callback address, user account, user token, SP information, value-added service information, and tariff information must all be valid.

[0015] In one embodiment of the present invention, the user online information verification obtains the user's online information through userToken. If the current user is not online or the login IP is different from the IP address of the current request information, it is determined to be a fake order, the order callback address is returned, and an abnormal information prompt is given.

[0016] To implement the above technical solution, the payment plugin adds screenshots of user operation behavior and reports them through an encrypted interface. The screenshot information reported by the payment plugin is obtained according to the request parameter transactionID, the existence of the image is determined, the user's trajectory is traced, and if the image does not exist, the user is redirected to the order callback address and an error message is displayed.

[0017] To implement the above technical solution, the cashier backend will also record the device information and user information of abnormal orders, providing data for order traceability. For verified order requests, the user will be redirected to the payment confirmation page. Once the user confirms the order information, the order process is completed, and the user will be returned to the SP value-added content to enjoy the value-added services.

[0018] As described above, the method for preventing fraudulent IPTV subscriptions in this invention has the following beneficial effects: the payment plugin serves as the sole entry point to the payment terminal. Through technologies such as device fingerprinting, it identifies the user's actual device, ensuring the authenticity of the request source. The payment plugin carries a cached unique device identifier, along with user information and subscription details from the subscription request, and accesses the payment terminal's backend interface. The payment terminal's backend performs multiple verifications, accurately identifying and promptly intercepting fraudulent subscriptions. Before the subscription is completed, it blocks unauthorized subscriptions, preventing financial losses for users and reducing bad debt losses for operators. Operators' ability to intercept malicious subscriptions in advance increases user trust and user stickiness. It does not alter the existing subscription page or the user's familiar subscription steps, avoiding complex operations such as input and switching on the page, thus minimizing the impact on the user's subscription experience. Attached Figure Description

[0019] Figure 1 The diagram shown is a sequence diagram of value-added service subscription and payment for the IPTV method for preventing fraudulent subscriptions in an embodiment of the present invention.

[0020] Figure 2 The diagram shown is a flowchart of the subscription data verification process for the IPTV method for preventing fraudulent subscriptions of value-added services disclosed in an embodiment of the present invention.

[0021] Figure 3 The diagram shown is a parameter verification flowchart of the method for preventing fraudulent subscriptions of value-added services for IPTV disclosed in an embodiment of the present invention.

[0022] Figure 4 The diagram shown is a flowchart of the cashier verification process for the IPTV method for preventing fraudulent subscriptions of value-added services disclosed in an embodiment of the present invention.

[0023] Figure 5 The flowchart shown is a user information verification process for the IPTV method for preventing fraudulent subscriptions to value-added services disclosed in an embodiment of the present invention.

[0024] Figure 6 The flowchart shown is a user trajectory verification flowchart of the method for preventing fraudulent subscriptions of value-added services for IPTV disclosed in an embodiment of the present invention. Detailed Implementation

[0025] The following specific embodiments illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification.

[0026] Please see Figures 1 to 6 This invention provides a method for preventing fraudulent subscriptions to value-added services on IPTV, comprising an operator, service provider, cashier, payment plugin, user data interface, and IPTV, specifically including the following steps: a. The user browses the value-added services provided by the SP through IPTV and initiates a subscription request; b. After receiving the user's order request, the SP calls the payment plugin, which is the only entry point to the cashier. c. The payment plugin parses the SP request parameters and obtains user information and ordered business information. At the same time, it collects device hardware information such as IMEI and MAC address, software environment such as system version, installed application list, network characteristic IP address, generates a unique device identifier, caches the generated unique device identifier, and encrypts and reports it to the user data interface, carrying the cached unique device identifier, as well as the user information and ordered business information in the order request, and accesses the cashier backend interface. d. The user data interface receives user data reports, parses request parameters, and obtains plaintext information; e. The back-end of the cashier performs multiple verifications; f. If the verification passes, the user is redirected to the payment page. After confirmation, the order is completed and the SP value-added content is returned. If the verification fails, the order request is intercepted, the callback address is returned, and an exception is displayed.

[0027] Users browse value-added services provided by SPs through IPTV set-top boxes and proactively initiate subscription requests based on their own needs. When the SP receives a user's subscription request, it invokes the payment plugin, which serves as the sole payment gateway. Using technologies such as device fingerprinting, the plugin identifies the user's actual device, ensuring the authenticity of the request source. The payment plugin parses the SP's request parameters and obtains user information and subscription details. Simultaneously, it collects device hardware information such as IMEI, MAC address, and set-top box serial number; software environment information such as system version, payment plugin version number, and installed application list; and network IP address characteristics. This generates a unique device identifier, which is then cached and encrypted before being reported to the user data interface. If a device is detected to have a different identifier, the SP will take further action. In the OOT (Out of Thread) state, a device error message is returned directly, and the ordering process is terminated. This ensures the authenticity and integrity of the request source. The payment plugin carries a cached unique device identifier, as well as user information and ordering business information from the order request. It then accesses the cashier's backend interface, where the cashier's backend performs multiple checks to accurately identify and promptly block fraudulent ordering behavior. Before the order is completed, it blocks unauthorized orders, preventing financial losses for users and reducing bad debt losses for operators. The ability for operators to intercept malicious orders in advance increases user trust and user stickiness. This does not change the existing ordering page or the ordering operation steps that users are accustomed to, avoiding complex operations such as input and switching on the page and minimizing the impact on the user's ordering experience.

[0028] In step b, the operator's cashier only opens the standard encrypted interface that connects to the payment plugin, and closes all direct access methods that bypass the payment plugin and do not require plugin encryption verification, including but not limited to public URLs, unencrypted HTTP interfaces, API interfaces not bound to plugin signatures, and anonymous access interfaces, cutting off unauthorized client access paths.

[0029] The payment plugin serves as the sole entry point to the checkout, cutting off access paths for unauthorized clients and using technologies such as device fingerprinting to identify the user's real device and ensure the authenticity of the request source.

[0030] The payment plugin adds screenshots of user actions and reports them through an encrypted interface, providing a basis for manual review by operations staff.

[0031] After the payment plugin is loaded, a periodic timed task Observable sequence is created after a 3-second delay. Every 5 seconds, the current screen is captured and reported to the data interface. The 3-second delay is to avoid the peak period of plugin loading resource consumption.

[0032] In step d, after the request parameters are verified to be correct, the order information is saved, and the user information is stored in Redis with an expiration time of 15 minutes. The screenshot information is received and the signature is verified. If the signature verification fails, it is returned directly. If the signature verification is successful, the screenshot is renamed to the current time accurate to milliseconds, cached in Redis, and an expiration time is set.

[0033] The primary key for order information is the transactionID, a request parameter from the SP (Service Provider) payment plugin. The key for Redis cached user information is the transactionID plus the user account. The key for Redis cached image information is also the transactionID. The order data verification process is as follows: Query the cached order data based on the transactionID. Determine if the order data exists. If it does, check if it matches the device information in the request parameters. If it does, retrieve the cached user information and check if it matches the user information in the request parameters. If it does, retrieve the cached business information and check if it matches the business information in the request parameters. If it does, the order data verification is successful. If the order data does not exist or does not match the device information, user information, or business information in the request parameters, the order data verification fails.

[0034] The request parameter validation process is as follows: obtain the request parameters, determine if the request parameters exist, if they exist, decrypt the request parameters and convert them into a request object, determine if the request object exists, if it exists, perform non-empty request parameter validation, if the non-empty request parameter is present, the request parameter validation is successful, if the request parameter does not exist in the first place, the request parameter validation fails, if the request object does not exist, the request parameter validation fails, if the non-empty request parameter is absent, the request parameter validation fails.

[0035] The cashier's multi-factor authentication in step e specifically includes: parameter integrity verification, encryption key validity verification and obtaining the user's real account through decryption, user account status verification, user online information verification, blacklist verification, user-reported data verification, screenshot existence verification, and order authentication.

[0036] Required parameters cannot be empty. Verify the validity of the encrypted key and obtain the user's real account through decryption. When verifying the user account status, determine if the current account is normal; users in abnormal states are prohibited from ordering, the order callback address is returned, and an abnormal user status message is displayed. Verify the user's online information to determine if it's a fraudulent order. During blacklist verification, use the operator's provided user blacklist interface to determine if the user is on the blacklist; blacklisted users are prohibited from ordering, the user is redirected to the order callback address, and an error message is displayed. When verifying user-reported data, retrieve cached user-reported data based on the request parameter `transactionID`, and verify device information, user information, and order information. If the user-reported data does not exist, or the device, user, and order information do not match, the user is redirected to the order callback address, and an error message is displayed. When verifying the existence of screenshots... The system retrieves screenshots reported by the payment plugin based on the request parameter `transactionID`, determines if the image exists, and traces the user's activity. If the image does not exist, the user is redirected to the order callback address, and an error message is displayed. During order authentication, the system verifies the legality of the value-added service, the match between the user account and the ordered content, and the compatibility of the payment method with the ordered service. The cashier backend performs verification according to priority, accurately identifying and promptly blocking fraudulent and illegal ordering behavior. Before the order is completed, illegal orders are blocked, preventing economic losses for users and reducing bad debt losses for operators. Multiple information verifications, through multi-dimensional cross-verification of user identity, business parameters, and user behavior analysis, form a full-link protection network, effectively preventing various illegal ordering risks in SP value-added service scenarios.

[0037] The parameter integrity check includes ensuring that the necessary parameters requested by the payment plugin from the cashier backend are not empty. Specifically, the request transaction ID, order callback address, user account, user token, SP information, value-added service information, and pricing information must all be valid.

[0038] During user online information verification, the system obtains the encrypted key of the request object, retrieves and decrypts the encrypted user account. After successful decryption of the user account, it obtains and decrypts the userToken. After successful decryption of the userToken, it queries the user information. If the user exists and is legitimate, the user verification is successful. If the user account decryption fails, the user verification fails. If the userToken decryption fails, the user verification fails. If the user does not exist, the user verification fails. The system retrieves the user's online information through the userToken. If the current user is offline or the login IP is different from the IP address in the current request information, it is determined to be a fake order. The system returns the order callback address and displays an error message.

[0039] The payment plugin adds screenshots of user actions and reports them via an encrypted interface. The screenshot information reported by the payment plugin is retrieved based on the request parameter `transactionID`. The existence of the image is checked, and the user's trajectory is traced. If the image does not exist, the user is redirected to the order callback address, and an error message is displayed. The user trajectory verification process is as follows: The online information is queried based on the request parameter `userToken` to determine if the user is online. If so, the login IP of the online record is obtained, and it is checked whether the request IP matches the login IP. The cached screenshot information is queried based on the request parameter `transactionID`. If the screenshot exists, the trajectory verification is successful. If the user is offline, the request IP does not match the login IP, or the screenshot does not exist, the user trajectory verification fails.

[0040] The POS backend also records device and user information for abnormal orders, providing data for order tracing. Verified order requests will redirect to the payment confirmation page. Once the user confirms the order information, the order process is complete, and the user is returned to the SP value-added content to enjoy the value-added services. This reduces the complexity of the user's ordering process, avoids excessive switching and input operations through the remote control, solves the pain points of multiple switching and cumbersome input, and improves the order conversion rate.

[0041] The overall verification process at the checkout is as follows: The system receives the order request from the payment plugin and verifies the request parameters, user information, user activity, and order data. If all verifications are successful, the system proceeds to order authentication. Upon successful authentication, the user is redirected to the order confirmation page. After confirming the order, the user completes the order process and is returned with the SP (Service Provider) value-added services, allowing the user to continue enjoying these services. If any verification fails or authentication fails, the order process is terminated, and the user and device information for the abnormal order are recorded. The system then redirects to an order error message page displaying the error information.

[0042] This invention's payment plugin serves as the sole entry point to the payment gateway. Utilizing technologies such as device fingerprinting, it identifies the user's actual device, ensuring the authenticity of the request source. The payment plugin carries a cached unique device identifier, along with user and order information from the order request, accessing the payment gateway's backend interface. The payment gateway's backend performs multiple verifications to accurately identify and promptly block fraudulent and unauthorized ordering activities. By preventing unauthorized orders from being completed, it avoids financial losses for users and reduces bad debt losses for operators. Operators' ability to proactively block malicious orders increases user trust and loyalty. It does not alter the existing ordering page or the user's familiar ordering process, avoiding complex operations such as input and switching on the page, thus minimizing the impact on the user's ordering experience.

[0043] The above embodiments are merely illustrative of the principles and effects of the present invention and are not intended to limit the invention. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in the present invention should still be covered by the claims of the present invention.

Claims

1. A method for preventing fraudulent subscriptions to value-added services in IPTV, characterized in that, This includes operators, service providers (SPs), cash registers, payment plugins, user data interfaces, and IPTV, specifically involving the following steps: a. The user browses the value-added services provided by the SP through IPTV and initiates a subscription request; b. After receiving the user's order request, the SP calls the payment plugin, which is the only cashier entry point; c. The payment plugin parses the SP request parameters and obtains user information and ordered business information. At the same time, it collects device hardware information such as IMEI and MAC address, software environment such as system version, installed application list, network characteristic IP address, generates a unique device identifier, caches the generated unique device identifier, and simultaneously encrypts and reports it to the user data interface, carrying the cached unique device identifier, as well as the user information and ordered business information in the order request, and accesses the cashier backend interface. d. The user data interface receives user data reports, parses request parameters, and obtains plaintext information; e. The backend of the cashier performs multiple verifications; f. If the verification passes, the user is redirected to the payment page. After confirmation, the user completes the order and the SP value-added content is returned. If the verification fails, the order request is intercepted, the callback address is returned, and an exception is displayed.

2. The method for preventing fraudulent subscriptions to value-added services in IPTV according to claim 1, characterized in that, In step b, the operator's cashier only opens the standard encrypted interface that connects to the payment plugin, and closes all direct access methods that bypass the payment plugin and do not require plugin encryption verification, including but not limited to public URLs, unencrypted HTTP interfaces, API interfaces not bound to plugin signatures, and anonymous access interfaces, cutting off unauthorized client access paths.

3. The method for preventing fraudulent subscriptions to value-added services in IPTV according to claim 2, characterized in that, The payment plugin adds screenshots of user actions and reports them through an encrypted interface, providing a basis for manual review by operations personnel.

4. The method for preventing fraudulent subscriptions to value-added services in IPTV according to claim 3, characterized in that, After the payment plugin is loaded, a periodic timed task Observable sequence is created after a 3-second delay. Every 5 seconds, the current screen is captured and reported to the data interface. The 3-second delay is used to avoid the peak period of plugin loading resource consumption.

5. The method for preventing fraudulent subscriptions to value-added services in IPTV according to claim 1, characterized in that, In step d, after the request parameters are verified to be correct, the order information is saved, and the user information is stored in Redis with an expiration time of 15 minutes. The screenshot information is received and the signature is verified. If the signature verification fails, it is returned directly. If the signature verification is successful, the screenshot is renamed to the current time accurate to milliseconds, cached in Redis, and an expiration time is set.

6. The method for preventing fraudulent subscriptions to value-added services in IPTV according to claim 5, characterized in that, The primary key of the order information is the transactionID, a request parameter of the SP to launch the payment plugin. The key for the user information cached in Redis is the transactionID + the user account. The key for the image information cached in Redis is the transactionID, a request parameter of the SP to launch the payment plugin.

7. The method for preventing fraudulent subscriptions to value-added services in IPTV according to claim 1, characterized in that, The multi-factor authentication at the cashier in step e specifically includes: parameter integrity verification, encryption key validity verification and obtaining the user's real account through decryption, user account status verification, user online information verification, blacklist verification, user-reported data verification, screenshot existence verification, and order authentication.

8. The method for preventing fraudulent subscriptions to value-added services in IPTV according to claim 7, characterized in that, The parameter integrity verification includes ensuring that the necessary parameters requested by the payment plugin from the cashier backend are not empty. Specifically, the request transaction ID, order callback address, user account, user token, SP information, value-added service information, and tariff information must all be valid.

9. The method for preventing fraudulent subscriptions to value-added services in IPTV according to claim 7, characterized in that, The user online information verification obtains the user's online information through userToken. If the current user is not online or the login IP is different from the IP address of the current request information, it is judged as a fake order, the order callback address is returned, and an error message is displayed.

10. The method for preventing fraudulent subscriptions to value-added services in IPTV according to claim 1, characterized in that, The payment plugin adds screenshots of user actions and reports them through an encrypted interface. The screenshot information reported by the payment plugin is obtained based on the request parameter transactionID, the existence of the image is determined, the user's trajectory is traced, and if the image does not exist, the user is redirected to the order callback address and an error message is displayed.

Images