Home > Net >  Consult a great god, sweep WeChat code payment mode 2 is not set the callback url.
Consult a great god, sweep WeChat code payment mode 2 is not set the callback url.

Time:09-19

WeChat scan code payment mode 2 is not set up the callback url, direct ajax order query whether it is ok to pay for success, why WeChat after payment, receiving callback url page until WeChat result notification of payment?

CodePudding user response:

Should still want to have a callback url,
Then the url to the action, to do the order payment status query,
Because the there is a time delay of payment, you can't direct payment, go to check the order is due to avoid delay problems,

So through WeChat callback url, you again to order query,
And I remember WeChat officials have said, in your payment
Even if he callback url, you give your code is a success, but still suggest you to continue to check the order status,

As for you you can't get a pay as a result, the url that I feel might be
1 url path problem
2 May also be a pay management configuration domain problems

CodePudding user response:

I used to do is to direct mobile payment,
But feeling sweep code payment and the general process of the mobile payment should be no difference is too much,

CodePudding user response:

But the official documentation written inside, pay mode 2 does not rely on setting the callback URL, this is what meaning, ah

CodePudding user response:

reference moulovemy1988 reply: 3/f
but wrote in the inside of the official document, pay mode 2 does not rely on setting the callback URL, this is what meaning, ah

It is probably don't need it, maybe is you sweep code after the payment, the information displayed on your mobile phone is WeChat callback WeChat interface display,

CodePudding user response:

refer to 4th floor are nu month god reply:
Quote: refer to the third floor moulovemy1988 response:

But the official documentation written inside, pay mode 2 does not rely on setting the callback URL, this is what meaning, ah

It is probably don't need it, maybe is you sweep code after the payment, the information displayed on your mobile phone is WeChat callback WeChat interface display,


Is that they will take care of the callback, contact with ajax direct WeChat order number state, if the state is paid successfully, directly it is ok to write your own business logic,
A ah, a great god done h5 payment, not the h5 pay wap sites, mobile phone WeChat end to pay after the success, is also no callback, don't know is what reason,

CodePudding user response:

Impression of the business is judged by page order training in rotation and then judge for themselves,,,

CodePudding user response:

Mode 2 and mode, the different means is
Three times a background pattern and WeChat interaction: first to generate a regular qr code, the user after scanning, WeChat pay callback URL , the background for the second time a formal and WeChat interaction, submit orders, after the WeChat asynchronous notification is completed, the background query order information and update your database.
Mode 2 background only twice and WeChat interaction, the first generation of qr code contains the order information directly, users to directly interact with the WeChat after scanning, has been completed, WeChat asynchronous notification background.

Background correction notice is important, mode 2 is the way to generate orders, no pattern a security, judge the success of a process is still the same

CodePudding user response:

Normal process normally does not need to contact the ajax direct order, payment is completed, the interface will automatically jump back to the specified page, you are in the page design two buttons, one is called payment is complete, click on the back page before he pay, this time is enough to the background of the click callback processing, paid return to also see the normal state. One is called payment appear problem, after click, can prompt customer service call or something.

CodePudding user response:

refer to 7th floor HZTLTGG response:
mode 2 and mode, the different means is
Three times a background pattern and WeChat interaction: first to generate a regular qr code, the user after scanning, WeChat pay callback URL , the background for the second time a formal and WeChat interaction, submit orders, after the WeChat asynchronous notification is completed, the background query order information and update your database.
Mode 2 background only twice and WeChat interaction, the first generation of qr code contains the order information directly, users to directly interact with the WeChat after scanning, has been completed, WeChat asynchronous notification background.

Background correction notice is important, mode 2 is the way to generate orders, no pattern a security, judge the success of a process is still the same


Model 2 WeChat asynchronous notification background is what meaning, please talk about the details of some great spirit, mainly after the success of the payment, does not automatically jump to set the page up of receiving messages,

CodePudding user response:

Is WeChat will call yourselves the background of a link, you determine the success of the visit is WeChat to pay, to update your business state

As to not receive messages automatically jump to set up the page, that there is something wrong with the formulation, automatically jump is a front page, does not receive messages ah, just prompt the user has to pay to complete, and is not as the basis of pay is completed, I doubt you put after receiving the url of the configuration to the front end, specific how to configure the practice of I also know you

CodePudding user response:

And is not used as the basis for formal pay complete,

CodePudding user response:

See if you submit orders callback address written right, notify_url this parameter, directly in the browser open the notify_url, see can access, receiving less than the callback is what meaning, did you add the log on page callback? Is what is wrong, or you don't said WeChat callback requests are sent, if you don't write wrong, notify_url can also access, might have some network problems,

CodePudding user response:

To clear up two address
One is the notify_url, this is the address of the callback background processing orders, complete the payment after WeChat backstage at the place where you notice, you want to be in this address corresponding method processing orders,
One is the redirect_url, this is a front end complete pay later automatically jump address, display is given priority to, don't put business related things

CodePudding user response:

references to the tenth floor HZTLTGG response:
is WeChat will call yourselves the background of a link, you determine the success of the visit is WeChat to pay, to update your business state

As to not receive messages automatically jump to set up the page, that there is something wrong with the formulation, automatically jump is a front page, does not receive messages ah, just prompt the user has to pay to complete, and is not as the basis of pay is completed, I doubt you brought after receiving the url of the configuration to the front, I also know you is how specific configuration


Is this meaning ah, use sweep pattern and secondly, WeChat isn't will give me the payment message to set the notify_url page, then my signature verification, amount than what of, no problem, I will reply WeChat, don't back to adjust again, then write your own business logic?

CodePudding user response:

refer to 12 floor ying1234 reply:
see you submit orders callback address written right, notify_url this parameter, directly in the browser open the notify_url, see can access, receiving less than the callback is what meaning, did you add the log on page callback? Is what is wrong, or you don't said WeChat callback requests are sent, if you don't write wrong, notify_url can also access, might have some network problems,

Listen to a lot of people say WeChat interface is not stable, is it true that the great god

CodePudding user response:

refer to 12 floor ying1234 reply:
see you submit orders callback address written right, notify_url this parameter, directly in the browser open the notify_url, see can access, receiving less than the callback is what meaning, did you add the log on page callback? Is what is wrong, or you don't said WeChat callback requests are sent, if you don't write wrong, notify_url can also access, might have some network problems,

How to view the WeChat log, a great god

CodePudding user response:

Good job, I novice,

CodePudding user response:

The
reference 13 floor HZTLTGG reply:
clear two address
One is the notify_url, this is the address of the callback background processing orders, complete the payment after WeChat backstage at the place where you notice, you want to be in this address corresponding method processing orders,
Is a redirect_url, this is a front end complete pay later automatically jump address, display is given priority to, don't put business related things

Thanks for a great god, PC scan code and h5 payment has been successful, and the question is, if appear incorrect validation signature or amount than, need tell WeChat?

CodePudding user response:

refer to the 18th floor moulovemy1988 response:
Quote: refer to the 13th floor HZTLTGG response:

To clear up two address
One is the notify_url, this is the address of the callback background processing orders, complete the payment after WeChat backstage at the place where you notice, you want to be in this address corresponding method processing orders,
Is a redirect_url, this is a front end complete pay later automatically jump address, display is given priority to, don't put business related things

Thanks for a great god, PC scan code and h5 payment has been successful, and the question is, if appear incorrect validation signature or amount than, need tell WeChat? nullnullnullnullnullnullnullnullnullnullnull
  • Related