Overview

Paysafe's Alternate Payments API can be used to take payments using a number of alternate payment methods popular in countries around the world. This API currently supports the payment methods in the table below.

You can enable only one alternate payments method per account associated with your merchant account. Each of these accounts must have an associated settlement currency. If you need to use the same alternate payments method with multiple settlement currencies (where available) then you will need a separate account configured for each currency/payment method combination.

Supported Alternate Payments
Payment Brand Payment Type Refunds Supported Sectors Supported Countries Currencies Redirect Manual Settlement
Boku Mobile
(Carrier Billing)
No

Retail

Digital Goods

UK, Sweden, Switzerland, Norway

GBP, SEK, CHF, NOK

Yes No
Giropay Real-Time Bank Transfer No All* Germany EUR Yes No
Interac Real-Time Bank Transfer No

Retail

Digital Goods

Canada CAD Yes Yes
Klarna
(Sofort)
Real-Time Bank Transfer Yes

Retail

Digital Goods

Germany, Austria, Belgium, Czech Republic, France, Hungary, Italy, Netherlands, Poland, Spain, Slovakia, Switzerland and UK EUR Yes No
NETELLER Real-Time Bank Transfer Yes All* Most Countries Most major currencies, including EUR, USD, GBP, and HKD Yes No
Paysafe
Pay Later
Credit (Invoice) Yes

Retail

Digital Goods

Germany, Austria, Switzerland, Netherlands, United Kingdom

EUR, GBP, CHF

No Yes
paysafecard Prepaid Voucher No All* Multiple Countries Multiple Currencies Yes Yes
Paysafecash Prepaid Voucher Yes

Retail

Digital Goods

Austria, Bulgaria, Croatia, Finland, Hungary, Italy, Latvia, Portugal, Romania, Spain, Slovenia, Multiple Currencies Yes Yes
Rapid Transfer Real-Time Bank Transfer No

Retail

Digitial Goods

Austria, France, Germany, Hungary, Italy, Spain, UK, Poland, Portugal EUR, GBP, HUF, PLN Yes No
Skrill Real-Time Bank Transfer Yes All* Most Countries Most major currencies, including EUR, USD, GBP, and HKD Yes No

Automatic Settlement Payment Flow

The standard payment flow (automatic settlement) is summarized in the following diagram.

Standard Alternate Payments Flow

  1. The customer is ready to check out and selects an alternate payments method.
  2. The merchant sends a Payment request using the Paysafe Alternate Payments API.
  3. If the request is successful, Paysafe returns a response that includes a payment ID and a payment redirect URL hosted by the payment provider.
  4. The merchant redirects the customer's browser to the payment provider URL.
  5. The customer logs in and authorizes the payment.
  6. Once payment authorization is complete (or fails), the customer is redirected back to the return URL provided by the merchant in the payment request.
  7. Paysafe receives updates from the payment provider on the status of the request.
  8. The merchant should use webhooks for notification of status changes.
  9. Once payment is complete, the merchant receives the funds and they can notify the customer.

Some payment methods do not require a redirect. In this case, no redirect link is returned.

Manual Settlement Payment Flow

Some payment methods offer manual settlement, which allows the merchant to authorize a payment and then settle at a later date/time, typically on shipment of goods. This behavior is controlled using the settleWithAuth parameter.

When settling paysafecard payment authorizations, the maximum delay between the initial payment authorization and the subsequent settlement is 1 minute.

The manual settlement payment flow is summarized in the following diagram.

Manual Settlement Alternate Payments Flow

  1. The customer is ready to check out and selects a two-step alternate payments method (e.g., paysafecard).
  2. The merchant sends a Payment request using the Paysafe Alternate Payments API, with the settleWithAuth parameter set to false.
  3. If the request is successful, Paysafe returns a response that includes a payment ID and a payment redirect URL hosted by the payment provider.
  4. The merchant redirects the customer's browser to the payment provider URL.
  5. The customer logs in and authorizes the payment request, which will not be settled at this point.
  6. Once payment request is completed (or fails), the customer is redirected back to the return URL provided by the merchant in the payment request.
  7. Paysafe receives updates from the payment provider on the status of the request.
  8. The merchant can use webhooks to receive notification of status changes.
  9. If the merchant is ready to ship the goods or provide the digital content, they send a Settlement request for the payment.
  10. Paysafe returns a response to the Settlement request.
  11. When the Settlement is complete, the merchant receives the funds and they can ship the goods and notify the customer.

Multiple partial settlements are supported with a cumulative value equal to the initial authorization. The amount remaining to settle, if any, is shown in the response to each Settlement request.

Did you find this page useful?