Page tree
Skip to end of metadata
Go to start of metadata

 Request

Response


The doScheduledWalletPayment function registers a scheduled payment request and does the requested day a debit authorization request with the data of a wallet.

The payment record is characterized by:

  • information from an existing virtual wallet 
  • the payment due date: an amount, a currency, a due date, a status, etc...

The request is refused in the following cases :

  • The identifier of the virtual wallet provided does not exist or the wallet is inactive 
  • The payment date is beyond the expiry date of payment method 
  • The payment method is not accepted 

Payment is refused only if the request for authorization is refused.

Payline informs you, through its notification function, the processing of your payment request. The notification URL used is defined at your point of sale on the Administration Center.

Request

The doScheduledWalletPaymentRequest request must have the following structure :

Element

Description

Mandatory

Format

Condition 

version

Payline web services version. To be valued with the latest version: see the table of versions

Yes

N2


paymentPayment informationYesObject payment
orderRefReference of the orderNoAN50
orderDateDate of the orderNoAN16
scheduledDate
The desired date for the authorization request
YesAN10
walletId
The unique identifier of the virtual wallet. This is the identifier that you communicated during the request to create the Wallet.
YesAN50
cardInd
This field is required if you use the multiwallet
NoN2
order

Order information

YesObject order
recurringRecurring informationNoObject recurring
authentication3DSecureauthentication3DSecure informationNoObject authentication3DSecure

privateDataList

Personal information

No

Object privateDataList


media

Detection of the media used during the payment.
The possible values ​​of this tag are:

-       Computer
-       Mobile
-       Tablet
-       TV
-       Console
-       Undefined

No

AN25


subMerchantPayment Facilitator informationNoObject subMerchant
linkedTransactionIdUse to identify the first authorization request which initializes the payment (for merchants managing their own wallets).NoANversion 26 or higher