Request |
The function doRecurrentWalletPayment saves a payment record for automatic and recurring billing of your customer.
Payline processes day-by-day deadlines and informs you of the result via the notification function.
The payment record is characterized by:
- information from an existing virtual wallet ;
- payment deadlines: an amount, a currency, a due date, a status, etc.
The registration of the payment file is refused in the following cases:
- The identifier of virtual wallet provided does not exist or the wallet is inactive
- The amount of payment.Amout field does not have the correct value
- The payment method is not accepted
In the event that the expiry date of credit card does not cover all the future due dates, Payline will alert you with the return code 02506.
A payment is refused only if the request for authorization is refused.
Request
Element Description Required Format version Version of Payline web services. See the table of versions. Yes N2 The unique identifier of the virtual wallet. This is the identifier that you communicated during the request to create the Wallet This field is required if you use the multi-wallet Information on deadlines privateDataList Personal information No Order information media - Computer No AN25The request doRecurrentWalletPaymentRequest must have the following structure :Condition payment Payment information Yes Object payment orderRef Order information Yes AN50 orderDate Date of the orderYes AN16 scheduledDate The desired date for the authorization requestYes AN10 walletId Yes AN50 cardInd No N2 cvx No AN recurring Yes Object recurring order No Object order Detection of the media used during the payment.
The possible values of this tag are :
- Mobile
- Tablet
- TV
- Console
- Undefinedauthentication3DSecure 3DSecure operations information No Object authentication3DSecure Version 27 or higher (3DSV2) linkedTransactionId In case of installment, recurring or split shippment payment refers to the first authorization (bank id). No AN200 Version 27 or higher (3DSV2)