General and special cases
This chapter covers general and special cases, that do not apply to one payment method, but also do not apply in any case, for example special behaviors in case of certain acquirers and special features, accross multiple payment methods, that need a special integration. This chapter covers these cases.

Partial approvals

A partial approval is best explained with an example:
A customer comes to your shop and orders goods worth 100 Euros.
He/she enters the card details, and Saferpay authorizes the card. During authorization, the card holder's bank checks the solvency of the card holder and concludes that only a maximum of 80 Euros can be authorized.
Usually, such a transaction would be declined. However, if the merchant requests a partial approval, the card can be authorized for 80 Euros.
This sort of authorization type is best suited for goods that are sold in bulk, like for example screws, certain food items, or petrol at a gas station.
Not all Issuers may support this feature. If partial approvals are not supported, either the full amount will be authorized, or the transaction will be declined.

Requirements

  • Partial approvals can only be requested with SpecVersion 1.20, or higher.
  • Partial approvals are only available for Visa/VPay, Mastercard and Maestro.

Integration

A partial approval can only be requested when using the Authorize Direct Request. In the request, the parameter Payment.Options.AllowPartialAuthorization must be set to true.
Please make sure that you have read the PSD2 chapter, since an Authorize Direct request is classified as a Merchant Initiated Transaction (MIT)!
Request
Response
1
{
2
"RequestHeader": {
3
"SpecVersion": "1.20",
4
"CustomerId": "242225",
5
"RequestId": "8cf6d15a041ba515d90ee191257d9f77",
6
"RetryIndicator": 0,
7
"ClientInfo": {
8
"ShopInfo": "My Shop",
9
"OsInfo": "Windows Server 2013"
10
}
11
},
12
"TerminalId": "17869305",
13
"Payment": {
14
"Amount": {
15
"Value": "10000",
16
"CurrencyCode": "EUR"
17
},
18
"OrderId": "Order_2",
19
"Description": "Test Order #2",
20
"Options": {
21
"AllowPartialAuthorization": true
22
}
23
},
24
"Payer": {
25
"IpAddress": "192.168.178.55",
26
"LanguageCode": "en"
27
},
28
"PaymentMeans": {
29
"Alias": {
30
"Id": "77b828c0975498e986e1663489ceacdc"
31
}
32
}
33
}
Copied!
1
{
2
"ResponseHeader": {
3
"SpecVersion": "1.20",
4
"RequestId": "8cf6d15a041ba515d90ee191257d9f77"
5
},
6
"Transaction": {
7
"Type": "PAYMENT",
8
"Status": "AUTHORIZED",
9
"Id": "69W8jSbjbhA2vASMbxUUAl3Q4OKA",
10
"Date": "2020-11-04T12:29:07.646+01:00",
11
"Amount": {
12
"Value": "5000",
13
"CurrencyCode": "EUR"
14
},
15
"OrderId": "Order_2",
16
"AcquirerName": "VISA Saferpay Test",
17
"AcquirerReference": "05718468252",
18
"SixTransactionReference": "0:0:3:69W8jSbjbhA2vASMbxUUAl3Q4OKA",
19
"ApprovalCode": "715453"
20
},
21
"PaymentMeans": {
22
"Brand": {
23
"PaymentMethod": "VISA",
24
"Name": "VISA"
25
},
26
"DisplayText": "xxxx xxxx xxxx 0013",
27
"Card": {
28
"MaskedNumber": "xxxxxxxxxxxx0013",
29
"ExpYear": 2022,
30
"ExpMonth": 2,
31
"HolderName": "test",
32
"CountryCode": "DE",
33
"HashValue": "E1DB6CE1CC017DCB651E7256650023698E58E158"
34
}
35
},
36
"Payer": {
37
"IpAddress": "192.168.178.55"
38
}
39
}
Copied!
The merchant must make sure that his inventory is adjusted accordingly, since less will be payed than initially requested.

Test cards

Test cards are included in the respective chapters for the given payment methods.

Scheme tokens

Saferpay also supports the direct insertion of decrypted Scheme-tokens, provided by any external provider (For example Apple Pay). This way, it is possible to provide a more seamless and integrated solution. However in this case, the integration is realized via the Transaction Interface. The overall transaction-flow will stay the same. The only thing you must take care of is, that you provide the necessary data, within the PaymentMeans.SchemeToken container, through the Initialization request.
1
{
2
"RequestHeader": {
3
"SpecVersion": "[current Spec-Version]",
4
"CustomerId": "[your customer id]",
5
"RequestId": "[unique request id]",
6
"RetryIndicator": 0
7
},
8
"TerminalId": "[your terminal id]",
9
"Payment": {
10
"Amount": {
11
"Value": "100",
12
"CurrencyCode": "CHF"
13
}
14
},
15
"PaymentMeans": {
16
"SchemeToken": {
17
"Number": [DECRYPTED TOKEN NUMBER],
18
"ExpMonth": "03",
19
"ExpYear: "2021",
20
"AuthValue": "AAABBIIFmAAAAAAAAAAAAAAAAAA="
21
}
22
},
23
"Payer": {
24
"LanguageCode": "en"
25
},
26
"ReturnUrls": {
27
"Success": "[your shop payment success url]",
28
"Fail": "[your shop payment fail url]"
29
},
30
"Styling": {
31
"CssUrl": "[your shop css url]"
32
}
33
}
34
Copied!

Special Cases

Though we at SIX/Worldline do offer the possibility to process credit cards, it sometimes is necessary to involve third parties in order to process credit cards in certain countries and regions. This chapter will cover the special characteristics you need to consider, if you want to use Saferpay with these processors.

Credit Cards

Chase Paymentech

Chase Paymentech is a US credit card processor with office in Dallas, Texas. SIX Payment Services offers the possibility to process credit cards over this processor, directly in the US.
Please take note to the following restrictions and characteristics.
  • OrderId: Due to technical restrictions, the OrderId will not be forwarded to Chase to be shown on your reconciliation files from chase. Saferpay will instead fill it with a unique, increasing, numeric value, to meet Chase Paymentechs requirements. Therefore, a later identification through the OrderId will not be possible.