Wallet order

post

https://testapi.multisafepay.com/v1/json/orders

Create an order to collect a payment from a customer using Wallet payment methods.

Supported wallet payment methods

The following brands are supported:

GOOGLEPAY APPLEPAY PAYPAL AMAZONPAY WECHATPAY ALIPAYPLUS

How to test

Under Authentication > Query, enter a website API key from your TEST account.
Enter dummy data manually under Body params, or go to the sandbox and click Examples and select a pre-filled example.
Click Try it!

❗️ Never use a live API key!

💬 For support, email [email protected]

Payment management via API

Features

📘
NEW
Apple Pay is no longer limited to Safari on iOS devices. You can now use Apple Pay in other supported browsers and on supported desktop devices.
Activate Apple Pay for your test account and create a redirect order to test this new functionality. For more information, see Apple Pay. An Apple device is still required to test the payment
Apple Pay is not supported on Android devices.

Body Params

Wallet order

type

string

enum

redirect: Redirects the customer to a payment page, where they can select a payment method and complete payment.
direct: Redirects the customer to an authentication or success page, depending on the payment method.

If not set, redirect is used.

For more information, see Direct vs redirect.

Allowed:

gateway

string

enum

required

The unique identifier for the payment method (gateway). See Gateway IDs.

If unset for redirect orders, the payment page displays all available payment methods.

order_id

string

required

length ≤ 50

Your unique (client-defined) identifier for the order.

currency

string

required

length between 3 and 3

The currency of the payment.

Format: ISO-4217 currency code.

amount

integer

required

≥ 0

The payment amount in the currency's smallest unit:

Decimal currencies: Value for 10 EUR = 1000 (1000 cents)
Zero-decimal currencies: Value for 10 JPY = 10

Discounts

To discount:

An entire order, enter a reduced amount.
Specific items in the order, in the shopping_cart, reduce the unit_price of the relevant items.

description

string

required

length ≤ 200

A description of the customer's order.

Appears on payment pages and customer bank statements (if supported by the bank).

payment_options

object

Contains:

URLs to your success page and cancel page. Make sure your URL only contains specific set of ASCII characters (alphanumeric, -, _, ., :, /).
Your webhook endpoint
Settings for displaying available gift cards

customer

object

required

The customer’s personal information.

Not required for Apple Pay, Google Pay, and WeChat Pay direct orders.

gateway_info

object

Information specific to the payment method (gateway).

Required for: Apple Pay and Google Pay direct orders.

delivery

object

The customer's shipping address.

checkout_options

object

Settings for the shopping cart, including taxes and validation.

capture

string

enum

For manual capture orders.

Supported wallets:

Allowed:

shopping_cart

object

The array of items in the customer's shopping cart, including the shipping costs, and the tax class (as defined in checkout_options).

To learn how to calculate the order amount from the shopping_cart, see Rounding rule.

Discounts

See Recipe – Discount an order.

invoice

string

length ≤ 50

Your unique identifier for the invoice, which appears in your PayPal communications.

Required for: PayPal.

items

string

Displays additional information on payment pages and in payment confirmation emails to customers using HTML, e.g. display order items instead of including a shopping_cart.

For information about supported HTML tags and elements, see Payment pages - Styling.

second_chance

object

For Second Chance.

custom_info

object

Additional information about the order.

days_active

integer

1 to 365

Defaults to 30

For redirect orders, sets the number of days the payment page and its link remain valid.

This parameter only controls the expiry of the payment page. It does not set or affect the expiry time of an initiated transaction. For more information about transaction expiry, see Transaction expiration.

The lifetime begins when the order is created or the payment link is generated. A session_id is returned in the payment page URL.

If Second Chance is enabled, we recommend a minimum lifetime of 48 hours. Second Chance emails the customer 2 payment reminders: 1 hour and 24 hours after the order is created. If the lifetime is less than 24 hours, the link in the second email is no longer active when the customer receives it.

See seconds_active below. If seconds_active is also set, seconds_active is used. If neither is set, the default is used.

seconds_active

string

1 to 31536000

Defaults to 2592000

For redirect orders, sets the number of seconds the payment page and its link remain valid.

See days_active above. If days_active is also set, seconds_active is used. If neither is set, the default is used.

var1

string

length ≤ 500

Variable for storing additional data.

var2

string

length ≤ 500

Variable for storing additional data.

var3

string

length ≤ 500

Variable for storing additional data, including split payments metadata.

plugin

object

Information about your integration (useful for debugging).

Responses

Supported wallet payment methods

How to test

Payment management via API

Features

NEW

200Request successful

404Error