PayPal API混淆-用于ExpressCheckout的哪一个 [英] PayPal API Confusion - Which one to use for ExpressCheckout

问题描述

我正在查看PayPal提供的各种集成，而我只是想提供PayPal作为付款方式，因此我打算使用Express Checkout.话虽这么说，但似乎可以通过多种方式进行整合:

I'm looking at the various integrations PayPal offer and as I just want to offer PayPal as a payment options, I'm going with Express Checkout. That being said, there are numerous ways this can be integrated it seems:

1. 名称值对
2. 经典API(SDK)
3. 稳定的API.

我遇到的问题是.NET SDK是经典API集的一部分，而该API集显然已被弃用(来源: https://github.com/paypal/merchant-sdk-dotnet ). RESTful API没有提及ExpressCheckout，因此我假设 NVP是可行的方法.

The issue I have is that the .NET SDK is part of the classic API set which is apparently being deprecated (source: https://github.com/paypal/merchant-sdk-dotnet). The RESTful API doesn't mention anything about ExpressCheckout so I am assuming NVP is the way to go.

有人可以说出最好的解决方法吗，因为如果事情被弃用，我宁愿不必重写它.

Can someone clarify the best route to go down as I'd rather not have to rewrite it if things are being deprecated.

有关信息:我正在将ASP.NET MVC与C#一起使用.

For info: I'm using ASP.NET MVC with C#.

推荐答案

首先，只有两个API:

First off, there are only two APIs:

1. 经典API
   • 请求和响应有效载荷的格式为NVP and SOAP.
   • Express Checkout的官方PayPal SDK支持随用于.NET的PayPal Merchant SDK (( GitHub | NuGet )

1. Classic API
   • Request and response payloads are formatted as NVP and SOAP.
   • Official PayPal SDK support for Express Checkout available with the PayPal Merchant SDK for .NET (GitHub | NuGet)

• 请求和响应有效载荷的格式为JSON
• PayPal .NET SDK 提供了官方的PayPal SDK支持( GitHub | NuGet )

• Request and response payloads are formatted as JSON
• Official PayPal SDK support available with the PayPal .NET SDK (GitHub | NuGet)

通过 PayPal名称/值对API (NVP API)，您可以通过简单地将HTTP请求发送到PayPal并使用名称/值对指定请求参数来利用PayPal API的功能. NVP API是PayPal SOAP API的轻型替代方案，并提供对与SOAP API相同功能集的访问.

The PayPal Name-Value Pair API (NVP API) enables you to leverage the functionality of the PayPal API by simply sending an HTTP request to PayPal and specifying request parameters using name-value pairs. The NVP API is a lightweight alternative to the PayPal SOAP API and provides access to the same set of functionality as the SOAP API.

关于Classic API与REST API的几点注意事项:

A few points to consider with respect to Classic API vs. REST API:

• 经典API不会很快被弃用.您可以使用经典API.
• 此外，REST API不支持在经典API中工作的许多变量/参数.
REST API可用于信用卡和PayPal付款(快速结帐架构).

• Classic API is not going to be deprecated any time soon. You can use Classic API.
• Moreover REST API does not support many variables/parameters that work in Classic API.
• REST API can be used for both credit card and PayPal payments (express checkout architecture).

由于您使用的是.NET SDK，因此可以继续使用，因为它使用的是Classic API + NVP.

Since you are using .NET SDK, you can continue using it as it uses Classic API+NVP.

这篇关于PayPal API混淆-用于ExpressCheckout的哪一个的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！