Arborescence des pages

Comparaison des versions

Légende

  • Ces lignes ont été ajoutées. Ce mot a été ajouté.
  • Ces lignes ont été supprimées. Ce mot a été supprimé.
  • La mise en forme a été modifiée.





Align
alignright

     



Align
aligncenter


 Request

Response




Introduction

The doWebPayment function initialises a web payment before Payline begins payment flow. This allows immediate or deferred full payments, instalments payments, and subscription payments to be made.


Full payments allow you to carry out an authorisation+validation or a simple authorisation. If using simple authorisation, validation (or capture) takes place either automatically by the Payline payment solution, or by the merchant, using webservice calls or via our back office Payline administration centre. This can also be programmed from the authorisation request, always within 7 days, using the batch interface function or the doCapture web service by entering the date of action.

NOTE : With a debit authorization, you have up to 7 days to validate the payment request. Outside of those 7 days, your authorization expires and is no longer valid.


The notifications 

To be informed that your customer has paid once the authorization request has been accepted, even if the customer does not return to your site, fill in the notificationURL field in your point-of-sale settings or when you make a web payment initialisation request. Payline will then contact a page from your site and send back the token linked to the payment in the GET parameter of the HTTP request. This page must be accessible by Internet using the HTTP/S protocol.

When a notification is received, your site must carry out a result request for the notified web payment.

NOTE : If your site cannot be accessed, Payline tries every minute during 2 hours. After this, notification is deactivated. You can find your payments in the Merchant Administration Centre web interface.


Instalments or subscription payment is possible using a virtual wallet. 

Payline takes charge of the creation of a virtual wallet after the validation of data collected at first payment. When the customers make a second purchase on your online store, Payline suggests that they use their virtual wallet. In this case, “one click” payment is used and the customer does not need to enter any payment information.
Payline can manage instalment payments. When payment is carried out, you can be advised by email by activating the “send an email to merchant” option in the Merchant Administration Centre. If there is a problem with payment, Payline tries the transaction 3 times during one week. Each time an attempt fails, you are informed.


Alternative payment method  : this feature allows the merchant, in case of bank refusal, to offer his customers to pay with another means of payment.
This function only applies: for the same order, at the time of the first payment and in the event of a bank refusal. A list of alternative payment methods must have been provided in doWebPayment (secondSelectedContractList).


Request

The doWebPaymentRequest request must have the following structure:


Element

Description

Required

Type

Example

Condition
versionPayline web services version. To be valued with the latest version: see the table of versions.YesN2

18


payment

Information regarding payment. see the items below

YesObject payment


Possible values ​​of payment.action = 100, 101, 108, 110, 120, 121.

returnURL

URL on which the shopper's browser is redirected in case of acceptance or refusal of payment on Payline. 
The merchant must call getWebPaymentDetails

Yes

AN255

http: // ... or https: // ...


cancelURL

URL on which the shopper's browser is redirected in case of abandonment of the user, Payline or merchant.

Yes

AN255

http: // ... or https: // ...


order

Order Information see the items below

Yes

Object order



notificationURL

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

noNo

AN255

http: // ... or https: // ...


selectedContractList

The list of contract you wish to use for this payment. Payline displays the list of payment methods according to the list ordersee the items below

Yes

Object selectedContractList


Mandatory from version 4

secondSelectedContractList

The list of contract numbers that you want to be able to resubmit when the first transaction attempt fails.

If this field is not filled in, Payline will not resubmit a payment method when the first transaction attempt fails.see the items below

noNo

Object selectedContractList



privateDataList


Your own personal information : see the items belowinformation 

Nono

Object privateDataList



languageCode

Fill in this field with the ISO code of the language in which you want to display the Payline payment web pages. By default, the web browser of your shopper asks Payline for the page in the desired language : cf. complete list  language code 

noNo

AN6

fr

customPaymentPageCode

The personalization identifier of the merchant's customization web pages

noNo

AN50

1fd51s2dfs51


buyer

Shopper information see the items below

Nono

Object buyer



owner

Cardholder Information see the items below

Nono

Object owner


Applicable only for AMEX

securityMode

Selecting the security mode to use for the payment transaction

Yes

AN

SSL


recurring

Recurring payment information see the items below

Nono

Object recurring



customPaymentTemplateURL

Dynamic template URL

noNo

AN255


https: // .... only

contractNumberWalletList

A chart of the contract numbers of the wallet.

The Widget mode uses the multi-PDV Wallet and multi-contract.see the items below

noNo

Object contractNumberWalletList


Not used in Widget mode. RELEASE 4.53
merchantNameName displayed on the ACS authentication pagenoNoAN25Your name of signboard
subMerchantPayment Facilitator Information see belownoNoobject subMerchant
version 18 or later RELEASE 4.53
miscDataAdditional data , without character limit and transmitted to the partners. Consult the payment method for each use see belownoNoAN
version 18 or later RELEASE 4.53
asynchronousRetryTimeout

For the Asynchronous Retry function , this is a numeric that specifies the period in minutes. It must be between 5 and 10080 (7 days).

noNoAN10080RELEASE 4.56
threeDSInfoInformation specific to 3DS authenticationNoObject - threeDSInfo

version 21 or higher (3DSV2)

RELEASE 4.58

merchantScore
Score calculated by the merchant
(Used exclusively for CB Scoring)
NoAN

version 21 or higher (3DSV2)

RELEASE 4.58



Extrait
hiddentrue

The reference elements


Ancre
Object_payment
Object_payment

Object payment

Inclusion d'extrait
Object - payment
Object - payment
nopaneltrue



Ancre
Object_order
Object_order

Object order

Inclusion d'extrait
Object - order
Object - order
nopaneltrue




Ancre
Object_orderDetail
Object_orderDetail

Object orderDetail

Inclusion d'extrait
Object - orderDetail
Object - orderDetail
nopaneltrue




Ancre
Object_selectedContractList
Object_selectedContractList

Object selectedContractList

Inclusion d'extrait
Object - selectedContractList
Object - selectedContractList
nopaneltrue



Ancre
Object_privateDataList
Object_privateDataList

Object privateDataList

Inclusion d'extrait
Object - privateDataList
Object - privateDataList
nopaneltrue




Ancre
Object_privateData
Object_privateData

Object privateData

Inclusion d'extrait
Object - privateData
Object - privateData
nopaneltrue


Ancre
Object_buyer
Object_buyer

Object buyer

Inclusion d'extrait
Object - buyer
Object - buyer
nopaneltrue




Ancre
Object_owner
Object_owner

Object owner

Inclusion d'extrait
Object - owner
Object - owner
nopaneltrue



Ancre
Object_addressOwner
Object_addressOwner

Object addressOwner

Inclusion d'extrait
Object - addressOwner
Object - addressOwner
nopaneltrue




Ancre
Object_address
Object_address

Object address

Inclusion d'extrait
Object - address
Object - address
nopaneltrue



Ancre
Object_recurring
Object_recurring

Object recurring

Inclusion d'extrait
Object - recurring
Object - recurring
nopaneltrue



Ancre
Object_contractNumberWalletList
Object_contractNumberWalletList

Object contractNumberWalletList

Inclusion d'extrait
Object - contractNumberWalletList
Object - contractNumberWalletList
nopaneltrue



Ancre
Object_subMerchant
Object_subMerchant

Object subMerchant

Inclusion d'extrait
Object - subMerchant
Object - subMerchant
nopaneltrue








Ancre
miscData
miscData

Additional Private Data (example)


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
<impl:miscData>
    <![CDATA[
        { "ContratVAD": "{'optionalTravelDetails':
                                {'class':'First',
                                 'departureDate':'2014-10-05T08:43:00',
                                 'destinationCountry':'GN',
                                 'insurance':'SIMPLE',
                                 'mainDepartureCompany':'Luftansa',
                                 'ownTicket':false,
                                 'ticketCount':1,
                                 'travellerCount':2,
                                 'travellerPassportList':[{'expirationDate':'2018-12-31T08:45:00','issuanceCountry':'FR'},
                                                          {'expirationDate':'2019-01-01T08:45:00','issuanceCountry':'DE'}],
                                 'type':'TwoWay'
                                },
                            'additionalNumericFieldList':[{'index':'1', 'value':'10'},
                                                          {'index':'2', 'value':'20'}],
                            'additionalTextFieldList':[{'index':'11', 'value':'val11'},
                                                       {'index':'22', 'value':'val22'}]
                          }"
        }
      ]]>
</impl:miscData>