main content:
This article is mainly on the NVP butt, in the most simple interface case, explain the docking NVP solution.
The main function of providing first docking instructions under paypal official document, as follows
1. Request API server endpoint descriptor
https://api-3t.sandbox.paypal.com/nvp sandbox or test server API for signature credentials.
https://api-3t.paypal.com/nvp PayPal API for real-time production server signing certificate.
https://api.sandbox.paypal.com/nvp certificate credentials for API sandbox or test server.
https://api.paypal.com/nvp for PayPal API certificate credentials in real-time production server.
2. To make the PayPal able to verify your request:
API specified user name associated with your account. USER = API-Username
Specifies the password associated with the API user name. PWD = API-Password
If you're using the API instead of the signature API certificate, specify the user name associated with the API API signature. SIGNATURE = API-Signature
If you call on behalf of a third party merchant API, you must use third-party merchants PayPal or merchant account ID (sometimes referred to as the payer ID) specified e-mail address on file. SUBJECT = Authorizing-Merchant-Email Or Authorizing-Merchant-Account-ID
https://developer.paypal.com/docs/classic/api/# ( NVP address the SOAP document )
Take the case of a request postman tool request is successful shots show the way out of it.
Request to select an address corresponding to the above sandbox environment Alternatively or like official
经过格式化后的数据
对接就算完成了。
本文采用的是paypal的对接 NVP模式中的签名模式，
文档地址中有说明有两种模式。
证书模式：证书吧相应的证书下载下来就好了（具体我没做研究）
签名模式：签名登陆正式环境上面有一个销售工具中可以设置API 用户，跟签名。然后拷贝下来请求就好了。这个跟之前的OAuth的请求加密不一样，这个不用把所有参数混合加密。这边只是把前面说明的那三个值拷贝下来直接做请求，就可以成功了。