diff --git a/index.html b/index.html index c9d8959..d72af5c 100644 --- a/index.html +++ b/index.html @@ -226,8 +226,7 @@
This page describes the Saferpay JSON application programming interface.
Our API is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which can be understood by off-the-shelf HTTP clients. JSON will be returned in all responses from the API, including errors.
Test accounts:
Request your personal test account
-View shared test account data
UTF-8
must be used for text encoding (there are restrictions on allowed characters for specific fields though).
Content-Type
and Accept
headers should be set to application/json
for server-to-server calls. Redirects use the standard browser types.
HTTP Headers:
Content-Type: application/json; charset=utf-8
Accept: application/json
The Saferpay JSON Api uses unified and standardized formats. The following abbreviations for format information are used in this page:
Name | @@ -15070,6 +15069,7 @@
---|
1.43
for SpecVersionDCC
Information to the response of OmniChannel/AcquireTransactionBLIK
as valid value for the field PaymentMethods
MerchantFundDistributor
container with ForeignRetailer
subcontainer. This affects the following requests:
+
+