A month ago, a small program debugging micro letter to pay. In fact, not the first time transfer payments, because before the company is back in full with a good tune parameters like me so I do not think there is anything difficult. But this is starting from zero, because it is only the development of small procedures, the landing is a small application development platform, so jump pit, a long time impossible to escape. Now there is time to look at these records pit, forget to protect yourself and dance the next time when the pit do.
The origin of the pit: background debug tool returns with signature of the same, but the signature error has been reported . Ultimately the development process is not the correct document flow from the micro-channel transfer payments, so it appears the following series of questions.
The first thing the following two steps:
1. Make sure the program is small and the opening of the payment has been successfully bound merchant number (in the background micro-channel pay a small program modules follow the prompts)
2. The merchant number is already bound to any authorization (login number of small business program go to Products - APPID authorization management, authorization management page request authorization to go to the payment module select number of public consent to)
If the number is public, then, when you call micro-channel payment platform and secondly to set up a public number directory payment authorization, as follows:
