Payment pages
Activate and customize hosted payment pages.
Payment pages are hosted by MultiSafepay and are the easiest way to integrate all payment methods.
They are completely secure, fully mobile responsive, and can be styled to fit the look and feel of your site.
How it works
A customer selects a payment method at checkout, and is redirected to a secure page to complete payment with a URL starting with payv2.multisafepay.com
.
If you specify a payment method gateway, the page is tailored for that payment method. For example, for Visa, the page includes fields for the customer to enter their credit card details.
If you don't specify a gateway, all payment methods enabled in your account appear on the payment page.
Activation
You can activate payment pages yourself in your dashboard.
How to activate payment pages
- Sign in to your MultiSafepay dashboard .
- Go to Settings > Website settings.
- Click the relevant site.
- Select the Use new payment pages checkbox.
Note: If the Use new payment pages checkbox is not visible, email [email protected]
Integration
See Recipes – Create a payment page.
Known errors
A cross-site request forgery (CSRF) warning appears on payment pages when you use an HTML form to send customers to https://payv2.multisafepay.com
with a create order request.
https://api.multisafepay.com
acceptsPOST
andGET
requests.https://payv2.multisafepay.com
only acceptsGET
requests.
User guide
Deprecated version
The deprecated version of the payment page (URL: pay.multisafepay.com
) is still fully supported, but we strongly recommend upgrading to the current version.
Unsupported payment methods
We cannot guarantee that the deprecated version will support any new payment methods we add to our platform.
It does not support the following methods:
Method type | Unsupported methods |
---|---|
BNPL | AfterPay, Betaal per Maand, in3, Klarna |
Wallets | Alipay, Apple Pay, WeChat Pay |
Banking | Bancontact QR, Belfius, CBC/KBC, EPS, iDEAL QR, Request to Pay, Sofort, Trustly |
Prepaid cards | PaySafecard |
Google Analytics tracking
You can track the behavior of customers on payment pages through Google Analytics tracking. When the customer is redirected to the payment page, the UA-code is generated and appears in the HTML.
iframes
An inline frame (iframe) is an HTML document embedded inside another HTML document on a site.
Although MultiSafepay doesn't prohibit embedding payment pages as an <iframe>
, we do not recommend it. This is because:
- Some payment methods may not work for privacy and security reasons.
- Some banks use scripts that can't run within
<iframe>
elements. - Modern browsers can block them due to stricter security checks.
Instead, we recommend using payment components to embed payments into your site.
Localization
Payment pages are supported in 19 languages.
Supported languages
Payment pages support the following languages:
Supported languages | Supported languages |
---|---|
Arabic | Japanese |
Czech | Mandarin |
Danish | Norwegian |
Dutch | Polish |
English | Portuguese |
Finnish | Russian |
French | Spanish |
German | Swedish |
Hebrew | Turkish |
Italian |
You can also localize payment pages to automatically filter out payment methods that are not available in the customer's country, and to display local variants.
See API reference > Create order > customer
object > locale
parameter.
Locale codes per language and country
Code | Language & country |
---|---|
cs_CZ | Czech |
de_AT | German (Austria) |
de_DE | German (Germany) |
en_US | American English |
fi_FI | Finnish |
fr_BE | French (Belgium) |
fr_FR | French (France) |
it_IT | Italian |
nl_BE | Dutch (Belgium) |
nl_NL | Dutch (Netherlands) |
pl_PL | Polish |
es_ES | Spanish |
sv_SE | Swedish |
zh_CN | Chinese |
Locale example
{
"customer": {
"first_name": "John",
"last_name": "Doe",
"house_number": "39",
"address1": "Kraanspoor",
"address2": "",
"city": "Amsterdam",
"zip_code": "1033 SC",
"state": "Noord-Holland",
"country": "NL",
"locale": "nl_NL", // Set the language and country code
"phone": "0208500500",
"email": "[email protected]",
"gender": "M",
"birthday": "1980-12-31",
"user_agent": "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.111 Safari/537.36",
"referrer": "http://test.com",
"ip_address": "123.123.123.123",
"forwarded_ip": "",
"reference": ""
}
}
Payment links
You can manually generate a link to a payment page to send to a customer to complete payment.
Payment methods
If a customer's country is unclear or your integration doesn't let you provide the correct country code, consider displaying all your enabled payment methods on the payment page. This is not supported for the deprecated version.
How to display all payment methods
To display all payment methods on the payment page, follow these steps:
- Create an order to retrieve the payment link.
- Add
&methods=all
at the end of the payment link, e.g.https://testpayv2.multisafepay.com/connect/822LtiM8RjN313Yo5C46E2cjqmuL5qVfc7w/?lang=en_NL&methods=all
- Redirect the customer to the adapted link.
Note: This is not a standard option in our ready-made integrations.
Shopping cart
If you include a shopping_cart
object when you create an order, the cart details are displayed on the payment page by default. That is, all items in the customer's order, with the price and VAT for each.
How to hide the shopping cart
- To request to enable Advanced website templates for your MultiSafepay account, email [email protected]
- Sign in to your MultiSafepay dashboard .
- Go to Settings > New payment pages.
- Next to the relevant site, click Template.
- Under Configure page style, click Settings, and then select the Hide cart details checkbox.
Styling
We recommend styling payment pages to be consistent with the look and feel of your site.
In your dashboard
-
Sign in to your MultiSafepay dashboard .
-
Go to Settings > Website settings > Website.
-
Click the Template button.
-
Use the WYSIWYG editor to style the payment page template.
Choosing colors
In the left menu, a color chart appears when you click on the field of a page element. You can also enter a Hex color in the input field next to it.Selecting a logo or header image
In Settings > Payment page templates, upload files for logos or header backgrounds. They may take up to 5 minutes to process, and then automatically appear in the list in the editor.Setting a default template
If you have more than one template and want to set one as your default template, use the Set default option. You can also give this template a name, which is used as thetemplate_id
.Editing saved templates
Click Edit template (top-left corner).Duplicating styling to another template
Click Apply style from (top-right corner). Save the template to the relevant site. -
To save the finished template to the relevant site, click Submit website.
Via the API
You can dynamically style the payment page template for specific transaction requests via our API.
See API reference – Create order > Payment page/link > payment_options
object.
The items
parameter is an HTML string for displaying order items on the payment page, instead of including a shopping_cart
. The following HTML tags and elements are supported (all others are stripped out):
- b, br
- div (align)
- em
- font (color, face, size)
- h1, h2, h3, h4, h5, h6, hr
- i, img (width, height, alt, scale, border, align)
- li
- nobr
- ol
- p
- small, span, strong
- table (width, border, bordercolor, cellpadding, cellspacing), thead, tbody, tfoot, th (width, scope, colspan, align), td (height, width, align, valign, colspan, bgcolor), tr (bgcolor, valign)
- u, ul
Requirements for Visa
When customers select Visa as payment method, Visa requires us to display on the payment page the city and country where your webshop is located. This measure aims to increase reliability, transparency, and safety for customers.
Support
Email [email protected]
Updated 1 day ago