Paysafecard

Overview

Key information

Payment type

Voucher

Integration

Async, Checkout, Payment Link

Countries

AR, AT, AU, BE, BG, CA, CH, CY, CZ, DE, DK, ES, FI, FR, GB, GR, HR, HU, IE, IT, LT, LU, LV, MT, MX, NL, NO, PL, PT, RO, SE, SI, SK, TR, US

Languages¹

cs, de, en, es, fr, it, nl, pl, sv

Processing currencies

EUR, GBP, USD, AUD, CAD, CHF, DKK, HUF, NOK, PLN, RON, SEK

Settlement currencies²

EUR, GBP, USD, AUD, CAD, CHF, DKK, HKD, JPY, NOK, NZD, PLN, SEK

¹ See Integration notes - languages for further information
² Please contact Payvision Sales to confirm any settlement currency exceptions

Supported features

  • Dynamic Descriptor³
  • Sandbox
  • Fraud⁴
  • Device Optimization
  • Timeout⁵: 1800 seconds
  • Transaction amount range: defined by the consumer's payment institution. Payvision can put a MAX amount based on risk analysis.

🚧

PLEASE NOTE:

Features described are supported by the platform but individual connectors (acquirer/bank) may only support a subset of these features. You can check the connector sheets for full details.

³ Dynamic Descriptor service is only supported by a few acquiring banks. Please contact Payvision Sales if you require further information.
⁴ Fraud: account takeover fraud is the only possibility. Fraud Scrubbing (ACEProtect): Basic rule-based fraud prevention rules can be enabled.
⁵ Session timeout is the time when the consumer is redirected to his bank and the session expires at the bank

Available workflows

Workflow

Supported

Comments

Authorize → incremental authorize

🗵 No

Authorize → cancel

🗵 No

Authorize → partial cancel

🗵 No

Authorize → capture

🗵 No

Authorize → partial capture

🗵 No

Authorize → partial capture → partial capture

🗵 No

Authorize → capture → refund

🗵 No

Authorize → capture → partial refund → partial refund

🗵 No

Authorize → capture → recurring

🗵 No

Credit

🗹 Yes

Blind credits supported

Payment

🗹 Yes

Payment → refund

🗵 No

Payment → partial refund → partial refund

🗵 No

Payment → recurring

🗵 No

Integration notes

Required parameters

Payments

The minimum required parameters for payments are:

Parameter

Example value

header.businessId

{your_business_id}

action

payment

transaction.storeId

{your_store_id}

transaction.brandId

8010

transaction.amount

1.00

transaction.currencyCode

EUR

transaction.trackingCode

{your_tracking_code}

transaction.returnUrl

{your_return_url}

Credits

The minimum required parameters for credits are:

Parameter

Example value

header.businessId

{your_business_id}

transaction.storeId

{your_store_id}

transaction.brandId

8010

transaction.amount

1.00

transaction.currencyCode

EUR

transaction.trackingCode

{your_tracking_code}

customer.birthDate

1979-12-20

customer.email

[email protected]

customer.givenName

Jane

customer.familyName

Jones

customer.customerId

{your_customer_id}

Parameter lengths

Parameter

Length

Comments

transaction.descriptor

32 characters max.

ASCII code >= 32 && code < 127.
A few characters of the descriptor are consumed by Payvision's platform during formatting.
Not visible on customer's statement - only visible on merchant's statement.

customer.givenName

40 characters max.

customer.familyName

40 characters max.

customer.customerId

50 characters max.

Languages

The language and locale of the payment panel are determined by Paysafecard according to the following rules:
1. Has the customer already visited the payment panel? Take the locale from the set cookie.
2. Take the locale from the IP address of the customer (paysafecard uses a GeoIP service check).
3. Take the value from the locale parameter.
4. Take the value from the language parameter.
5. Take the locale from the browser header.

Contact us

Have a question? Contact us.

Updated 2 months ago

Paysafecard


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.


Top