Question 1

Which is better, Account and Transaction API Specification - UK or Ping++ (Ping++聚合支付)?

Accepted Answer

If you need a Finance API that's easy to integrate, go with Ping++ (Ping++聚合支付). Account and Transaction API Specification - UK uses apiKey while Ping++ (Ping++聚合支付) uses no authentication.

Question 2

What is the main difference between Account and Transaction API Specification - UK and Ping++ (Ping++聚合支付)?

Accepted Answer

Account and Transaction API Specification - UK: ## Functionality at a glance

The NBG "UK OPB - Account and Transaction v3.1.5" API follows the [UK Open Banking Specification
    v3.1.5](https://openbankinguk.github.io/read-write-api-site3/v3.... Ping++ (Ping++聚合支付): Chinese payment aggregator — unifies Alipay, WeChat Pay, UnionPay, Apple Pay into one API. 7 language SDKs. They differ in authentication (apiKey vs no authentication), HTTPS support (yes vs yes), and CORS (unknown vs unknown).

Question 3

Which Finance API is easier to integrate?

Accepted Answer

Ping++ (Ping++聚合支付) is easier to integrate because it requires no authentication.

Feature	Account and Transaction API Specification - UK	Ping++ (Ping++聚合支付)
Authentication	apiKey	None
HTTPS	Yes	Yes
CORS	Unknown	Unknown

Account and Transaction API Specification - UK vs Ping++ (Ping++聚合支付)

Account and Transaction API Specification - UK

Ping++ (Ping++聚合支付)

When to use which?