I create a public account, a mall, and a payment website. The mall is developed on a third-party development platform, and the website is developed by myself. The two domain names are different, however, jssdk payment is available, but oauth2.0 authorization can only set one. What should I do with a public account, a mall, and a payment website? The mall is made on a third-party development platform, my website is developed by myself. The two domain names are different, but both of them have jssdk payment. But what should I do if I can only set one authorization for oauth2.0?
Reply content:
I create a public account, a mall, and a payment website. The mall is developed on a third-party development platform, and the website is developed by myself. The two domain names are different, however, jssdk payment is available, but oauth2.0 authorization can only be set. How can this problem be solved?
Call the payment interface.