【问题标题】:How to specify a payee with paypal orders api?如何使用 paypal orders api 指定收款人?
【发布时间】:2021-03-16 16:06:53
【问题描述】:

这是我正在关注的教程:What is the best way to enable a website users send money to each other?

问题出在我的发帖请求上。 让我们把它分解成碎片。

  1. 标题
headers: {
  "Authorization": `Bearer ${accessToken}`,
  "Content-Type": "application/json"
}

我也通过 paypal api 获得访问令牌,即https://api.sandbox.paypal.com/v1/oauth2/token

  1. 身体
body: {
  intent: 'CAPTURE',
  purchase_units: [{
    amount: {
      currency_code: 'USD',
      value: '2.00'
    },
    payee: {
      email_address: "myanothersandboxaccount@gmail.com"
    }
  }]
}

但是,它不起作用,因为我收到一个错误

{
  name: 'INVALID_REQUEST',
  message: 'Request is not well-formed, syntactically incorrect, or violates schema.',
  debug_id: '2884e1b5eccee',
  details: [
    {
      field: '/',
      location: 'body',
      issue: 'INVALID_SYNTAX',
      description: 'MALFORMED_REQUEST_JSON'
    }
  ],
  links: [
    {
      href: 'https://developer.paypal.com/docs/api/orders/v2/#error-INVALID_SYNTAX',
      rel: 'information_link',
      encType: 'application/json'
    }
  ]
}

卷曲请求

curl -v -X POST https://api.sandbox.paypal.com/v2/checkout/orders \
-H "Content-Type: application/json" \
-H "Authorization: Bearer A23AALAej8Yg-4iKJBcWckiv5-ZlhYWlkmBsPuWaVngJcMigU7P-6f8P02vnOpIo8QlOJ-P3hd3K86vKo_lpSlu0-bZBj98eg" \
-d '{
  "intent": "CAPTURE",
  "purchase_units": [
    {
      "amount": {
        "currency_code": "USD",
        "value": "100.00"
      },
      "payee": {
        "email": "myanothersandboxaccount@gmail.com"
      }
    }
  ]
}'

卷曲响应

Note: Unnecessary use of -X or --request, POST is already inferred.
*   Trying 173.0.82.78...
* TCP_NODELAY set
* Connected to api.sandbox.paypal.com (173.0.82.78) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Request CERT (13):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: C=US; ST=California; L=San Jose; O=PayPal, Inc.; OU=PayPal Production; CN=api.sandbox.paypal.com
*  start date: Jul 27 00:00:00 2020 GMT
*  expire date: Aug  1 12:00:00 2022 GMT
*  subjectAltName: host "api.sandbox.paypal.com" matched cert's "api.sandbox.paypal.com"
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
*  SSL certificate verify ok.
> POST /v2/checkout/orders HTTP/1.1
> Host: api.sandbox.paypal.com
> User-Agent: curl/7.64.1
> Accept: */*
> Content-Type: application/json
> Authorization: Bearer A23AALAej8Yg-4iKJBcWckiv5-ZlhYWlkmBsPuWaVngJcMigU7P-6f8P02vnOpIo8QlOJ-P3hd3K86vKo_lpSlu0-bZBj98eg
> Content-Length: 212
> 
* upload completely sent off: 212 out of 212 bytes
< HTTP/1.1 201 Created
< Cache-Control: max-age=0, no-cache, no-store, must-revalidate
< Content-Length: 501
< Content-Type: application/json
< Date: Sat, 05 Dec 2020 10:30:13 GMT
< Paypal-Debug-Id: 6bd069526af1c
< 
* Connection #0 to host api.sandbox.paypal.com left intact
{"id":"674004650C383744Y","status":"CREATED","links":[{"href":"https://api.sandbox.paypal.com/v2/checkout/orders/674004650C383744Y","rel":"self","method":"GET"},{"href":"https://www.sandbox.paypal.com/checkoutnow?token=674004650C383744Y","rel":"approve","method":"GET"},{"href":"https://api.sandbox.paypal.com/v2/checkout/orders/674004650C383744Y","rel":"update","method":"PATCH"},{"href":"https://api.sandbox.paypal.com/v2/checkout/orders/674004650C383744Y/capture","rel":"capture","method":"POST"}]}* Closing connection 0

而且,使用 curl 我得到了成功的响应。我可以从我的贝宝沙盒仪表板中看到一切顺利。

会是什么?

【问题讨论】:

  • 你的身体是正确的,你应该能够用命令行 curl 或邮递员来验证。所以你需要显示完整的 API 响应(没有“...”)并且可能还记录您的请求,以便您查看实际传输的内容,因为有问题,但我们无法从您问题中的信息中判断出什么问题。
  • 感谢您的反馈。刚刚用完整的 api 响应更新了问题

标签: node.js paypal


【解决方案1】:

我使用 node-fetch 调用 paypal api 来创建订单。用 axios 试过,效果很好。

【讨论】:

    【解决方案2】:

    该错误基本上意味着 PayPal 无法将其接收到的正文对象解析为 JSON,因此似乎传输/接收不正确。

    您应该首先使用命令行 curl 进行测试,以验证功能和 JSON 的正确性,这应该可以工作。

    然后,要获取有关您发送的实际问题的更多详细信息,您需要记录发送的实际数据(不是您的代码,代码执行时发送的实际数据)

    一种方法是不要将您的请求发送到 https://api-m.paypal.com ,而是将其发送到通过 https://requestbin.com/ 提供的请求 bin 服务

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 2013-08-29
      • 2021-01-19
      • 2014-06-08
      • 2020-03-10
      • 2014-06-25
      • 2021-12-01
      • 2021-06-22
      • 2016-05-23
      相关资源
      最近更新 更多