Recurring Payments (Pay as Order) Guide

Transcription

1 Corporate Gateway Recurring Payments (Pay as Order) Guide V4.2 October 2014 Use this guide to: Find out about our recurring payments service Learn about setting up regularly occurring payments

2 Recurring Payments (Pay as Order) Guide > Contents Contents 1 Introduction What are recurring payments? Who is this guide for? Skills and knowledge More help? Legal Overview Enabling recurring payments Your responsibility The recurring payments process How recurring payments work Using recurring payments Submitting recurring payments Administering recurring payments Start and end dates Payment notifications Cancelling recurring payments Viewing recurring payments Payment methods Example of a recurring payment Recurring payment submitted - XML message Recurring payment reply - XML message Recurring payment error - XML message Risk, legal issues and pricing... 12

3 Recurring Payments (Pay as Order) Guide > Contents Risks Legal issues Pricing Appendix A: CVV and recurring payments Including CVV in recurring payment messages Sending an incorrect CVV Appendix B: Changes to the guide... 17

4 Recurring Payments (Pay as Order) Guide > 1 Introduction 4 1 Introduction Welcome to this guide on recurring payments. It tells you about Worldpay's online recurring payments service and how you can enable recurring payments. 1.1 What are recurring payments? Recurring Payments can be used for: Monthly subscriptions of any kind Regularly recurring payments such as upgrading online credits for services Recurring Payments is an XML function around which your legacy or own-built customer applications can be built. Recurring Payments requires all payment administration to be done by you. The shopper has no control over the process, but can receive notifications when payments are made. 1.2 Who is this guide for? This is a technical integration guide, aimed at: System integrators Other technical roles, including managers who are involved in designing and managing your integration Skills and knowledge To carry out the tasks described in this guide, you will need: XML programming skills Some knowledge of how our payment services work 1.3 More help? For more information about our products and services, including payment methods: See our website at Talk to your dedicated Relationship Manager For technical guides and developer resources (including our DTD) see: To contact Corporate Support: corporatesupport@worldpay.com Phone: +44 (0)

5 Recurring Payments (Pay as Order) Guide > 1 Introduction Legal Worldpay All rights reserved. This document and its content are proprietary to Worldpay and may not be reproduced, published or resold. The information is provided on an AS IS basis for information purposes only and Worldpay makes no warranties of any kind including in relation to the content or suitability. Terms and Conditions apply to all our services. Worldpay, the logo and any associated brand names are all trade marks of the Worldpay group of companies.

6 Recurring Payments (Pay as Order) Guide > 2 Overview 6 2 Overview 2.1 Enabling recurring payments To be able to process recurring payments, the Recurring Payment function in the Worldpay system must be enabled. Please contact your Relationship Manager or Corporate Support to set this up. 2.2 Your responsibility Worldpay require that you communicate your intention for recurring payments clearly and unambiguously with your shoppers, particularly in those cases where the amount varies from order to order. 2.3 The recurring payments process The recurring payments process is as follows: 1. You submit the initial order for a shopper with Worldpay as a regular order. 2. The shopper then submits his payment details, after which the payment is processed. 3. For each subsequent order for the same shopper, you refer to the initial order. All subsequent orders will then be paid in the same way as the first one, using the same payment details. For these subsequent orders there is no more need for Worldpay to interact with the shopper to receive payment details. You cannot automate the management of recurring payments. You must send a new payment request for each subsequent order. 2.4 How recurring payments work The first payment is processed as a regular payment: you store an order into Worldpay s payment system and then either collect the payment details from the shopper and forward these in a message to Worldpay (XML Direct), or redirect the shopper to Worldpay s payment pages (XML Redirect). Worldpay processes the payment as a regular order. For subsequent orders, you submit the order (only as XML through HTTPS) and add a field to the order data that refers to the first order and the merchant code from the initial order. Worldpay then automatically processes the payment for the subsequent order, using the payment details that are stored from the first order. The recurring payment can only be submitted if the payment for the first order is processed successfully.

7 Recurring Payments (Pay as Order) Guide > 2 Overview 7 For step-by-step instructions of how to set up recurring payments, see 3 Using recurring payments. Important note about merchant ids and recurring payments Worldpay only accepts Recurring Payments on a separate account (i.e. for a separate Merchant ID). This means that Worldpay have to set up another Merchant ID if you want to make recurring payments. You send the initial payment with your original Merchant ID (also known as the merchant code) and all subsequent recurring orders with the other Merchant ID supplied to you by Worldpay.

8 Recurring Payments (Pay as Order) Guide > 3 Using recurring payments 8 3 Using recurring payments 3.1 Submitting recurring payments The following steps describe how you submit recurring payments for a shopper: Step 1 Create an initial order for the shopper and submit the order as a regular order (as XML through HTTPS), with all the standard parameters, and your original Merchant ID. The first payment must always be a regular payment. Orders can be submitted to the payment system by posting orders to the URLs: Test: Production: The XML order should be included in the Body of the message. Step 2 Step 3 Step 4 Either collect the payment details from the shopper and forward these in a message to Worldpay (Direct using XML), or redirect the shopper to Worldpay s payment pages (XML redirect). Worldpay processes the payment as a regular order. Once the initial order has been successfully processed, create a subsequent order using your other Worldpay-supplied Merchant Code. The subsequent order must contain the standard parameters: description, amount and ordercontent. To identify the order as a subsequent order and refer to the correct initial order and original merchant code, instead of payment details you include the following two extra parameters: payasorder: specifying the ordercode and merchantcode from the initial order amount: specifying the amount and currencycode of the initial order A subsequent order can have a different currencycode and amount than the initial order. An example of a subsequent order submitted in XML is shown in Recurring Payment Submitted - XML Message. Step 5 Step 6 Submit the subsequent order only as XML through HTTPS. Repeat steps 3 to 5 for all subsequent payments.

9 Recurring Payments (Pay as Order) Guide > 3 Using recurring payments Administering recurring payments Recurring payments allow you to: Vary the interval between the initial order and the subsequent order so it is different to the period between the subsequent orders. Submit an initial order amount that is different from the subsequent order amount. Renew subscriptions by sending a new order referring to the initial order. Have regular intervals between payments. Pay regular amounts. Pay varying amounts at regular intervals. Change the frequency of payments within set limits. Repeat payments indefinitely. Payment can be processed until the card expires (then authorisation bounces) Start and end dates The start date for the recurring payments is the date on which the initial order is submitted. There is no agreement so therefore no formal end date, but you can set a card end date earlier than the card expiry date. Recurring payments run until you no longer submit subsequent (PayAsOrder) orders, the card expires, or the card end date is reached Payment notifications Worldpay issues an XML or message to you when each payment is processed (see Recurring payment reply - XML message). You can enable notification to the shopper from either the Worldpay system or from your own system. You can also customise the content sent to the shopper Cancelling recurring payments You can cancel recurring payments by not submitting any more subsequent payments. The shopper can cancel recurring payments by reversing payments (using chargebacks, etc) Viewing recurring payments Recurring payments are shown in the Merchant Interface like any other Payment, and cannot be distinguished from non-recurring payments. For more information, refer to the Merchant Administration Interface User Guide. Because Worldpay only accepts recurring payments for a separate Merchant ID, you can choose between two Merchant IDs in the Merchant Interface: one to monitor regular payments and one to monitor recurring payments.

10 Recurring Payments (Pay as Order) Guide > 3 Using recurring payments Payment methods Due to the nature of payment methods, recurring payments are only available for the payment methods shown in the table below. Cards Direct debit Other AirPlus, American Express, Carte Bancaire, Carte Bleue, Dankort, Diners, Discover, JCB, Laser, MasterCard, Visa Netherlands: Signed Permanent Mandate for Direct Debit Single Mandate for Direct Debit (signed or unsigned) ("Eenmalige Machtiging") Spain: Domiciliación Bancaria Table 1: Payment methods for Recurring Payments ELV (Elektronisches Lastschrift Verfahren) For ELV and Direct Debits in the Netherlands, there are changes you need to be aware of as a result of SEPA regulations. For more information see the SEPA Integration guide at All payment methods can be initiated without shopper interaction. 3.4 Example of a recurring payment This section shows the following examples of a recurring payment: Recurring Payment Submitted - XML Message Recurring Payment Reply XML Message Recurring Payment Error XML Message Recurring payment submitted - XML message Below is an example of a recurring payment submitted to Worldpay: <?xml version="1.0"?> <!DOCTYPE paymentservice PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//en" " <paymentservice version="1.4" merchantcode="techman"> <submit> <order ordercode="1234"> <description>monthly subscription.</description> <amount value="1399" currencycode="eur" exponent="2" /> <ordercontent>provide your or dercontent here</ordercontent> <payasorder ordercode="1111" merchantcode="originalmerchantcode">

11 Recurring Payments (Pay as Order) Guide > 3 Using recurring payments 11 <amount value="1399" currencycode="eur" exponent="2" /> </payasorder> </order> </submit> </paymentservice> Code example 1: Recurring payment submission This message sends order 1234 to Worldpay and instructs the system to use the same payment details as for the previous order As a result, order 1234 for merchant TECHMAN will be created for an amount of EUR and the payment details for order 1111 will be used to pay this order Recurring payment reply - XML message Worldpay s reply displays the payment details for order 1111: <?xml version="1.0"?> <!DOCTYPE paymentservice PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//en" " <paymentservice merchantcode="techman" version= 1.4 > <reply> <orderstatus ordercode="1234"> <payment> <paymentmethod>visa-ssl</paymentmethod> <amount value="1399" currencycode="eur" exponent= 2 debitcreditindicator="credit"/> <lastevent>authorised</lastevent> <balance accounttype="in_process_authorised"> <amount value="1399" currencycode="eur" exponent= 2 debitcreditindicator="credit"/> </balance> <cardnumber>4568********0015</cardnumber> </payment> </orderstatus> </reply> </paymentservice> Code example 2: Recurring payment reply

12 Recurring Payments (Pay as Order) Guide > 3 Using recurring payments Recurring payment error - XML message If your account hasn't been set up to allow split payments, the following error message will be received instead: <?xml version="1.0"?> <!DOCTYPE paymentservice PUBLIC "-//WorldPay/DTD WorldPay PaymentService v1//en" " <paymentservice merchantcode="techman" version="1.4"> <reply> <orderstatus ordercode="1234"> <error code="2"><![cdata[your contract does not allow split payment.]]></error> </orderstatus> </reply> </paymentservice> 3.5 Risk, legal issues and pricing Risks Code example 3: Recurring payment error There are a number of risks attached to using recurring payment, described below. Authorisation can be refused The payment details that were used for the initial order do not always automatically generate an authorisation for a subsequent order. Authorisation for a subsequent order can be refused if, for instance, the spending limit on the card has been exceeded, or if the card has expired since the initial transaction. If a recurring payment cannot be processed successfully, the merchant is responsible for initiating a new order by the shopper. This new order will have to be processed as a regular order through the Worldpay service. The shopper does not agree with the recurring payment Recurring payments are processed based on a merchant s instruction to Worldpay, without direct interaction between the shopper and Worldpay. If a shopper does not agree with a payment that has been processed as a recurring payment, he can either ask the merchant for a refund, or reverse the transaction with the card issuer, resulting in a chargeback. At all times, the merchant is responsible for chargebacks, and for taking appropriate measures to limit the number of chargebacks.

13 Recurring Payments (Pay as Order) Guide > 3 Using recurring payments Legal issues A merchant is allowed to process transactions as recurring payments. Credit card organisations refer to this type of transaction as "continuous authority" transactions (C.A.T.) or subscription transactions. As a merchant you are allowed to process these C.A.T. / subscription transactions, provided that you are authorised by the shopper to do so. This authorisation can be given by a signature or by clicking on an OK button on a website after having read the conditions. The merchant is responsible for clearly communicating to the shopper that the additional payments will be initiated from the shopper s card on a recurring basis. Furthermore, it is preferable, and in some countries obligatory, that prior to each payment the merchant notifies the shopper by sending an or an invoice Pricing Pricing for recurring payments is similar to pricing for regular orders. This also applies for refunds and chargebacks. Please refer to your contract for further information.

14 Recurring Payments (Pay as Order) Guide > Appendix A: CVV and recurring payments 14 Appendix A: CVV and recurring payments The CVV (Card Verification Value) is a three or four digit numeric code on your credit or debit card. CVV is also known as CVC (Card Verification Code). CVV checks help you authenticate a transaction by comparing the code entered by the shopper during the payment process with the code held by the card issuer. You ll find a three digit CVV on the back of Visa and MasterCard cards on the upper right hand side of the signature strip. On American Express cards, the CVV is a four digit number above the long card number. For more information about the CVV number, see Including CVV in recurring payment messages CVV is not mandatory for recurring transactions. It s up to you to decide if you want to send the CVV in your recurring payment submissions. If you include CVV in your submission it ll be passed to: The card issuer for checking. Our risk management module (RMM) for checking, if you ve configured it to do so. Recurring payment submission with CVV The example code below shows you how to include a CVV check in your recurring payment submissions: <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE paymentservice PUBLIC "-//Bibit//DTD Bibit PaymentService v1//en" " <paymentservice version="1.3" merchantcode="payasorder"> <submit> <order ordercode=" orderpmpayas/2"> <description>default Description</description> <amount currencycode="eur" exponent="2" value="5000"/> <ordercontent>default Order Content</orderContent> <payasorder ordercode=" orderpmpayas" cvc="123"> <amount value="5000" currencycode="eur" exponent="2"/> </payasorder> </order> </submit> </paymentservice> Code example 4: Including CVV/CVC in a recurring payment submission The CVV / CVC number is highlighted in red in the above example

15 Recurring Payments (Pay as Order) Guide > Appendix A: CVV and recurring payments 15 Response to a recurring payment submission with CVV The example code below shows a response to a recurring payment submission with CVV. The parameter to look for in the response is <CVCResultCode>: <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE paymentservice PUBLIC "-//WorldPay//DTD WorldPay PaymentService v1//en" " <paymentservice version="1.4" merchantcode="merchanteur"> <notify> <orderstatusevent ordercode=" "> <payment> <paymentmethod>visa_credit-ssl</paymentmethod> <amount value="14074" currencycode="eur" exponent="2" debitcreditindicator="credit"/> <lastevent>refused</lastevent> <IssuerResponseCode code="5" description="do not honour"/> <CVCResultCode description="unknown"/> <AVSResultCode description="unknown"/> <cardholdername> <![CDATA[Annette Ziemer]]> </cardholdername> <issuercountrycode>de</issuercountrycode> <riskscore value="86"/> </payment> <journal journaltype="refused"> <bookingdate> <date dayofmonth="14" month="01" year="2014"/> </bookingdate> </journal> </orderstatusevent> </notify> </paymentservice> The <CVCResultCode> parameter is highlighted in red.

16 Recurring Payments (Pay as Order) Guide > Appendix A: CVV and recurring payments 16 Sending an incorrect CVV If an incorrect CVV is sent the transaction could be declined. It s up to the card issuer to decide whether or not to authorise or decline a transaction. They re not obliged to tell us why a transaction was declined so we can t provide you with any detailed analytics. However, an incorrect CVV would increase the chances of a failed transaction. We don t set a limit to the number of attempts a shopper can make to enter the correct CVV before we block a recurring payment. You can configure the risk management module to block subsequent attempts, if you choose to.

17 Recurring Payments (Pay as Order) Guide > Appendix B: Changes to the guide 17 Appendix B: Changes to the guide Revision Release date Changes 4.2 October 2014 Added: Reference to SEPA Integration Guide for ELV and Direct Debit payments in the Netherlands, to 3.3 Payment methods Extra information, including example code for a payment response, to Appendix A:CVV and recurring payments 4.1 October 2014 Updated: Moved Changes to the guide to this appendix Added: New appendix: Appendix A:CVV and recurring payments 4.0 July 2014 Updated: 3.1 August 2013 Updated: Applied the rebranded template Prélèvement Automatique was removed because it s no longer supported by Worldpay. Table 2: Changes to the guide

18 Recurring Payments (Pay as Order) Guide > Contact us 18 Corporate support: +44 (0) UK Sales: International Sales: +44 (0) Worldpay Support Centre: Worldpay All rights reserved. Worldpay, the logo and any associated brand names are all trademarks of the Worldpay group of companies. 1.