Development: Specific steps and code will not say, there are many similar articles on the Internet you can look at, the specific is divided into two big do not go: (1) to Apple backstage to register the bank card information, Add in-Purchase items (2) is the code in the integration of in-purchase I would like to say today is mainly in the above two steps in the content of the things you need to pay attention to first in the first step of the time to register the bank card information is basically not too much of a problem here can be casually search online A tutorial Follow the steps to go, There are several points to note when adding an in-purchase item: (a) Describe the purchase in the time not to use the number of yuan to describe to give an example: if you want to add a one-yuan in the purchase of products, the general product will be such a sub-description of the content in the back of the purchase do not write RMB will be rejected The reason to be rejected is that you need to use the virtual currency instead, such as 1.00 of the Apple coin what this can be named according to your product and there is a place where some users may be a little confused is to fill in the Product ID I checked the documents on the Internet. There is no explanation for what this product ID is for how do I name him? This Product ID is the ID of the item you want to pay in the code to the Apple background of the time to tell the name of the project to distinguish between the general naming of the items you want to pay is your project bundle ID Plus the amount on it. (b) Many users are just beginning to integrate in the purchase of the time will be very confused, follow the step by step is the payment is not successful do not know why, here you have to pay attention to the first integration within the purchase as long as your app is not online at this time can only use sandbox test account to test, Using normal Apple account is no way to pay, many users will worry about online after the normal use of Apple account payment will be problems, this you can rest assured that as long as the test account in the test environment has gone through the environment will not be the problem, Here I say the point to add a sandbox account needs to be noted here Click Add Add when you need a mailbox Note This mailbox do not register as an Apple account This will not be used as a sandbox test account The rest of the information can be easily filled in the above is the Apple backstage need to pay attention to some things next I want to talk about the code should pay attention to what is of course the focus of this article: 1th: If you have followed the online tutorial step-by-step implementation, you will find that there will be a step to the Apple server verification process a lot of online processes are affixed to the foreground verification code, Here to remind you that this verification is best to do later to verify our front-end side only need to get back to us the results can be, (explain the next step of verification that the mobile phone this way to pay the process has been completed, the Apple side will give you a voucher to do the verification, To verify that your payment operation isNo, it's done), so here's the pit, join us when we pay the money in the background to verify that the stage of our own server problem or suddenly broke the network, then we have no way to know whether or not to pay the success, so we have to do is, When we get this credential, we should be in the sandbox, when the verification is successful we then delete the certificate in the sandbox, so as to avoid the payment after the success of the server's problems and the top-up is not successful. 2nd: In your app must not be able to withdraw functionality and only on the iOS device and in your top-up interface to have a corresponding description of the specific copy of the text such as: 3rd: Your entire project can not exist in addition to the application of the registration method, For example, a page has a link to open the content of the app Web site is the registration page, this is not allowed, the occurrence will be refused, Apple will think you this way is to guide users to use other means of payment to bypass Apple payment, The whole project can not have the prompt language prompts the user to be able to pay in the Android such as the prompt copy. 4th: Apple payment can not exist restrictions such as the company wants to achieve product login success can be paid, so click Buy not jump Apple Pay, there may be a jump login page and so on, this situation is not allowed, Apple would think it was a violation of their 5.1.1 audit rules. The solution to this problem is not to add any restrictions at the time of payment if there is a login this situation is recommended to add a tourist to pay just fine. 4th: If the project exists in the customer service phone and other buttons do not put on the first level of the page, you can choose to put on the level two page or the page after the test will be rejected. The above is I do in the purchase of all the pits encountered, there are many imperfect places also please forgive ~ ~
Apple's hard-to-shop audit trail
