Payment, email payment
Record to prevent the second time from being committed.
After the official example is integrated into the project
Scheme is the AppID of the application you created.
And the appid in the configuration file should be replaced.
At this time, the prerequisites must be completed and the account application should be completed.
PayActivity is the payment class. When you enter the payment class, the official examples are all carried out in the app. You have to change them here.
The above is a comment on the service number access in the demo, which is directly written to the dead. It was originally returned by calling the background interface. Each field in the document has a descriptive effect. Note that the field should not be randomly added, otherwise, the sign will be inconsistent. As for this data, we will not use the official one. We need a service data with the background, so that we can directly initiate the payment. After the payment is successful, the order will be completed.
Special attention should be paid to this issue.
The package path here cannot be changed. It can only be under the root directory of the application package, and the class name cannot be changed. Otherwise, it cannot be called. Many people say that the official example returns-1, this is because your data is officially used and not changed to your own,
There is nothing to say about other details. The official examples are all well written.