Welcome to the MultiSafepay API reference.

To test using the API sandbox, you need to create a test account.

Request types

With our API, you can create transactions through direct and redirect requests.

Direct requests connect directly to the payment method, whereas redirect requests first send the customer to a payment page.

For redirect requests, if the gateway for a specific payment method is:

• Provided: The payment page is tailored for that payment method, e.g. for Visa, the page includes fields for the customer to enter their credit or debit card details.
• Not provided: The payment page displays all payment methods.

Then, if further customer action is:

• Required: The customer is redirected to complete payment, e.g. for iDEAL, they are redirected to their online banking environment.
• Not required: The transaction is completed automatically.

If you provide a redirect_url, after completing payment the customer is directed to your success/thank you page.

Flows

For more information about the direct and redirect flows for a specific payment method, see the respective payment method page.

Click to magnify.

Headers

When submitting requests via our API to prevent errors, always include the relevant headers.

• For POST and PATCH requests:

Example

curl -X POST '<URL here>'\
-H 'accept: application/json' \
-H 'content-type: application/json'

• For GET and DELETE requests:

Example

curl -X GET '<URL here>'\
-H 'accept: application/json' \

Wrappers and SDKs

We provide the following SDKs and wrappers to facilitate integrating via our API:

• Django wrapper
• Go wrapper
• Java wrapper
• Laravel wrapper
• .NET wrapper
• NodeJS wrapper
• PHP SDK
• Python wrapper

Deprecated XML API

Our XML API was superseded by the JSON API.

You can still use the XML endpoint to process transaction requests, but new payment methods, features, and tools are only supported by the JSON API.

💬

Support

Email [email protected]