title: Pitfalls in the process of using TePass!
date: 2022-05-24 13:40:00
toc: false
index_img: http://api.btstu.cn/sjbz/?lx=m_dongman&cid=1
category:
- Tips
tags: - Configuration
- Support
- Format
There are many pitfalls when configuring TePass. Let's record them one by one below:
- When Alipay sends a callback notification, signature verification is required. Many people don't pay attention to the documentation and use the Alipay public key instead of the merchant application's public key.
- Website issues, such as using CDN. In this case, you need to find the callback URL of your own website and exclude it from the CDN settings (this URL should not be executed by the CDN).
- The website is blacklisted by Alipay, so it will definitely not receive notifications.
- There is a problem with the version of the merchant's private and public key generation. At least version 1.4 or above is required.
- The callback address is filled in incorrectly, or no callback address is filled in on the Alipay open platform.
- There may be issues with the data format in the Alipay callback notification. Pay attention to escape characters and handle them yourself.
- Confirm whether the page is HTTP or HTTPS. If it is HTTPS, you need to install an SSL certificate. The certificate requirements are as follows: "Issued by a reputable certificate authority, self-signed certificates are not supported."
Note: The notify_url page can only return "success". There should be no HTML code on the asynchronous notification page.