Create a MXWallet session

post

https://api-sandbox.retail.monext.com/v1/checkout/mxwallets/sessions

Create an MXWallet session to initiate the creation of a virtual wallet via the web interface.
This feature enables management of wallet cards, allowing your client to:
- View registered cards in their wallet
- Delete a registered card from their wallet
- Add multiple cards to their wallet
- Set a card from their wallet as the default payment method.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

pointOfSaleReference

string

required

1 to 50

Point of sale reference.

paymentMethodIDs

array of strings

required

The list of payment methods you wish to use for the wallet session.

paymentMethodIDs*

mxWalletId

string

required

1 to 50

The unique identifier of Monext virtual wallet.
You must provide Monext with an unique identifier that corresponds to one and only one buyer on your information system.
This identifier will be used when you request a payment by Monext virtual wallet.
MXWallet ID must:

Start and contain only an alphanumeric characters (A-Z, a-z, 0-9).
May include dots ('.'), hyphens ('-'), and underscores ('_').
Have a length between 1 and 50 characters.

buyer

object

Buyer information.

allowUpdatePersonalDetails

boolean

Defaults to false

Indicates whether updating personal data is allowed.

threeDS

object

3DS information

privateData

object

Additional data to be used throughout the payment lifecycle.
A dictionary of key-value pairs where the values can only be strings.
e.g. {"suborderid": "AE-3023-001", "chanel": "mobile"}

returnURL

string

required

URL on which the buyer's browser is redirected in case of acceptance or refusal of payment on Monext Online.
The merchant must call getWebPaymentDetails or GET /sessions.

notificationURL

string

URL on which Monext Online will ask the merchant site to retrieve the result of the transaction.

languageCode

string

Buyer browser language by default. Example : FR

customPaymentPageCode

string

The identifier of customized template pages.
If not set, the default one will be used.

Headers

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Responses

201Created

400Bad Request

401Unauthorized

403Forbidden

404Not Found

409Conflict

412Precondition Failed

422Unprocessable Entity

429Too Many Requests

500Internal Server Error

501Not Implemented

502Bad Gateway ou Proxy Error

503Service Unavailable

504Gateway Time-out