diff --git a/content/payment-methods/3ds2.md b/content/payment-methods/3ds2.md index 4b49ff2b4..14dc71667 100644 --- a/content/payment-methods/3ds2.md +++ b/content/payment-methods/3ds2.md @@ -30,6 +30,8 @@ slug: '3ds2' When you collect cardholder data, you also need to collect other contextual information from the customer's device (fingerprint). This is only relevant for `direct` card orders and **not** for [payment components](/docs/payment-components) or [payment pages](/docs/payment-pages), where MultiSafepay collects the fingerprint on your behalf. +Note: Some details are required for successful completion of the payment, and to comply with scheme regulations. For exmaple, transactions created with payment method VISA must include the `email` parameter. + See also [Cardholder data](/docs/cardholder-data). # Exemptions diff --git a/content/payment-methods/card-payment-pricing-models.md b/content/payment-methods/card-payment-pricing-models.md deleted file mode 100644 index cb4beba37..000000000 --- a/content/payment-methods/card-payment-pricing-models.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: 'Card payment pricing models' -category: 6298bd782d1cf4006032e765 -order: 30 -hidden: false -parentDoc: 62a727569e389a012f577acd -excerpt: 'Distinction between Blended and Interchange ++ pricing' -slug: Card-payment-pricing-models ---- - -Banks and <> charge different fees to cover the operational costs of managing their network and processing card payments. - -There are three cost components that determine the final card pricing: - -- The **Interchange** fee that is paid to the issuing bank -- The **Scheme fee** charged by the scheme, like Visa or Mastercard -- The **<>** fee, in this case applied by MultiSafepay - -## Pricing models - -When you create a MultiSafepay account, we provide an offer based on the estimate of these costs. - -The actual cost for processing a card transaction vary considerably depending on a range of factors, including: - -- Issuer country -- Issuing bank -- Type of card, business or consumer -- Type of card funding, debit or credit -- Type of transaction, Point-of-Sale or Card-not-Present -- Merchant segment -- Monthly transaction volume - -We distinguish between two main card pricing models: **Blended** and **Interchange ++**. - -### Blended pricing - -In the Blended pricing model, a fixed percentage is charged based on an initial projection of the card volume and market. - -Taking into account the fluctuation of fees between the individual transactions, a **fixed percentage** is agreed and applied to all transactions of the respective card payment method. This means, the charged percentage is stable and predictable. Percentage and quantity of transactions are displayed in the monthly invoice. - -### Interchange ++ pricing - -The Interchange ++ pricing model breaks down the individual costs for the transactions processed during the month. - -Once a card transaction is completed, the agreed pre-charge is applied. At the end of the month, the pre-charged fees are contrasted to the actual costs of the transactions. The only fixed component is the Acquirer fee which covers the costs of transaction processing. Scheme fee and Interchange fee are disclosed and corrected in the monthly invoice, under the section **Interchange details**. The correction appears in one bundled fund or charge transaction. - -This type of calculation offers increased transparency. However, the actual cost of a card transaction is difficult to predict upfront but the increased transparency serves businesses of all sizes. - -### How to choose - -If your business does not heavily rely on card volume, and the volume is based pre-dominantly on consumer cards within the EEA, a blended rate provides clear pricing. -If your business mostly relies on cross-border and B2B sales, Interchange++ pricing gives you the highest level of transparency. - ---- - -[block:html] -{ - "html": "
\n

\n 💬\n

Support

\n

\n

Email sales@multisafepay.com

\n
\n" -} -[/block] diff --git a/content/payment-methods/card-payments.md b/content/payment-methods/card-payments.md index 74de827b9..6a0b4e267 100644 --- a/content/payment-methods/card-payments.md +++ b/content/payment-methods/card-payments.md @@ -104,6 +104,8 @@ The table below sets out the <> and < - Transactions expire after 1 hour. +- Note: Consider card-specific requirements for the [Create order request](/reference/createorder/), for example including `email` parameter for VISA payments. + #### Co-branded cards Co-branded cards are processed through the `VISA` <>. diff --git a/content/payment-methods/cardholder-data.md b/content/payment-methods/cardholder-data.md index dc5534875..dee9b9030 100755 --- a/content/payment-methods/cardholder-data.md +++ b/content/payment-methods/cardholder-data.md @@ -42,9 +42,10 @@ Set `type` to `direct`. When you collect cardholder data, you must also collect the contextual information about the customer's device (fingerprint) required for [3DS2](/docs/3ds2) authentication. The fingerprint can be created through JavaScript interfaces and methods in the customer's browser. - To learn how to create a fingerprint, see Recipe – Create a customer.browser object . +Note: Some details are required for successful completion of the payment, and to comply with scheme regulations. For exmaple, transactions created with payment method VISA must include the `email` parameter. + --- # User guide diff --git a/content/payment-methods/in3.md b/content/payment-methods/in3.md index c055e2045..035c25162 100644 --- a/content/payment-methods/in3.md +++ b/content/payment-methods/in3.md @@ -1,10 +1,10 @@ --- -title: 'in3' +title: 'iDeal in3' category: 6298bd782d1cf4006032e765 order: 2 hidden: false parentDoc: 62bd75142e264000a66d62b5 -slug: 'in3' +slug: 'ideal-in3' ---