Last update 6/09/2019

6. Alias Manager: Recurring transactions

You can perform recurring transactions with PayPal Express Checkout without having to re-enter the customer's identification details.

In order to work with recurring PayPal transactions, you need to activate the Alias Manager option in your ePDQ account. Alias Manager allows you to process recurring transactions.

6.1 PayPal Account Configuration

Next to the basic PayPal account configuration, the following boxes will also need to be ticked for the API permissions:

  • Create and manage Recurring Payments
  • Obtain authorization for pre-approved payments and initiate pre-approved transactions
  • Charge an existing customer based on a prior transaction
Note: The actual structure and behaviour of the PayPal back office may differ from the description below.

6.2 Integration: identification and transaction in one step

To create an alias, in addition to the default hidden fields the merchant must send specific alias fields:

Field Description
ALIAS Alias proposed by the merchant
ALIASOPERATION Fixed value “BYMERCHANT”
ALIASUSAGE A text explaining the reason for the Alias registration
SHASIGN SHA-IN signature, for data integrity. (Please refer to the Alias Manager integration guide)

When the customer is sent to the PayPal login screen, he will identify himself and verify the payment (the current and future amounts) by clicking the “Agree and Pay” button.

When the customer clicks the “Agree and Pay” button, he enters into an invoicing agreement with PayPal, which authorises the merchant to charge the customer's PayPal account directly. We will create the Alias in our Alias database based on the PayPal invoicing agreement.

6.3 Integration: splitting identification and payment

6.3.1 Step 1: Identification request

To create an alias, in addition to the default hidden fields the merchant must send specific alias fields:

Field Description
ALIAS Alias proposed by the merchant
ALIASOPERATION Fixed value “BYMERCHANT”
ALIASUSAGE A text explaining the reason for the Alias registration
SHASIGN SHA-IN signature, for data integrity. (Please refer to the Alias Manager integration guide)

When the customer is sent to the PayPal login screen, he will identify himself and verify the payment (the current and future amounts) by clicking the “Agree and Pay” button.

When the customer clicks the “Agree and Pay” button, he enters into an invoicing agreement with PayPal, which authorises the merchant to charge the customer's PayPal account directly. We will create the Alias in our Alias database based on the PayPal invoicing agreement.

6.3.2 Step 2: Client details reception

Same as normal "Step 2" (cf. Step 2: Client details reception), but only via e-Commerce (hosted payment page).

6.3.3 Step 3: Authorisation payment request

In step 3, the same additional fields as in "Step 1" must be sent (see default hidden fields of Step 3):

Field Description
ALIAS Alias proposed by the merchant (the same as in step 1)
ALIASOPERATION Fixed value “BYMERCHANT” (the same as in step 1)
ALIASUSAGE A text explaining the reason for the Alias registration (the same as in step 1)

At this stage we will create the Alias in our Alias database, based on the invoicing agreement from PayPal.

6.4 Alias usage

The merchant can perform a recurring PayPal transaction via the e-Commerce or DirectLink mode.

6.4.1 e-Commerce

The merchant needs to send an existing ALIAS value in the “ALIAS” hidden field. We will then check whether the ALIAS already exists for the merchant’s PSPID. If the ALIAS exists, we will trigger a recurring payment. The customer will be sent straight to the payment confirmation screen (unless an error occurs).

Please refer to the Alias Manager integration guide for information on the mandatory pre-payment checks (SHA-IN signature) and post-transaction feedback requests (SHA-OUT signature).

The merchant has to send the “ALIAS” parameter in his request. We will then check whether the ALIAS exists for the merchant’s PSPID and look up the financial profile (based on the ALIAS) in the database.

Please refer to the Alias Manager integration guide for information on the mandatory pre-payment check (SHA-IN signature).

Important
When using an Alias with Paypal, the Merchant also has to specify the brand in his request (PM=PAYPAL)

6.5 Alias management

The value in the “card number” field in the alias management page represents the PayPal invoicing agreement for that specific alias.

It is not possible to update an alias (manually or during a transaction). The merchant needs to delete the original alias and create a new one in the event that some of the details change. 

Every Alias remains valid until it is deleted.

*Call Charges: The following is a guide to call charge information from Business landlines within the UK.

Barclaycard is a trading name of Barclays Bank PLC. Barclays Bank PLC is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority (Financial Services Register number: 122702). Registered in England. Registered No. 1026167. Registered office: 1 Churchill Place, London E14 5HP

Barclays Bank PLC subscribes to the Lending Code which is monitored and enforced by the Lending Standards Board. Further details can be found at www.lendingstandardsboard.org.uk escape arrow


© Barclaycard 2016