Recurring Credit Card Billing

Transcription

1 Recurring Credit Card Billing Recurring Credit Card Billing (RCCB) allows recurring debits to a credit card in a PCI compliant method. System Overview This document is intended for merchants and developers that want to gain a high level understanding of integrating to MyGate s RCCB Solution.

2 CONTENTS Overview... 3 Benefits of RCCB... 3 Key Benefits:... 3 Reduce Risk Using MyGate s RCCB... 3 Process Descriptions Subsequent Transactions... 4 Amending Card Detail... 4 Expired Card Lookup... 4 MyGate s Role in RCCB Subsequent Transactions... 4 Developers Integration Role in RCCB... 4 RCCB - My Virtual Solution RCCB - My Enterprise Subsequent Transactions... 5 Merchants Role in RCCB... 5 Manage RCCB... 5 Perform Manual RCCB... 6 Terminology... 6 MyGate RCCB Page 2

3 Overview RCCB allows a website to post through a transaction value to be debited, frequency of the debit and for the period that the credit card is to be debited. RCCB is typically used for subscription based services and provides for fully automated recurring billing. Debits to credit cards can occur weekly, monthly or annually. The initial transaction is initiated by the card holder (push) and subsequent transactions are initiated by MyGate (pull) based on the parameters passed through on the initial transaction. Many merchants want to store customer credit card numbers for later use. For example, a merchant might want to save payment information on the first purchase so that they can reinitiate a recurring debit against the credit card at a later stage. MyGate can process and store card transactions for recurring transactions without taking away core functionality from the merchant. MyGate s RCCB solution enables merchants to easily integrate into a payment solution that can be built around their specific requirements without the merchant getting involved with storing of the credit card detail. Benefits of RCCB The benefits of MyGate s RCCB solution are far reaching including the reduction of PCI Compliance scope and increased security as no sensitive card data is present in a merchant environment, even in the case of a breach. Key Benefits: Initiate recurring debits to credit cards No sensitive card data is present in a merchants environment Operate without the burdensome required controls and procedures The merchant is not required to install SSL, saving costs. Both the merchants logo and details can be hosted on the payment page. Additional detail such as shipping address and purchase items can be displayed on the payment page This is a quick and easy method which ensures less programming. Intermediate development skills are required. Reduce Risk Using MyGate s RCCB Rather than encrypting sensitive data, it is better to keep it out of the database and rather manage recurring transactions using a unique MyGate transaction index that links back to a MyGate s database which will be used for managing recurring transactions. If your servers were to be compromised you are safe because the transaction index can only be used with your payment gateway and merchant account. Process Descriptions The initiated transaction is the first transaction to take place. The first transaction will include the full card detail, authorization request, settlement request, debit period and debit frequency. MyGate will store Recurring information and initiate subsequent transactions based on the recurring criteria. The initiated transaction value will be debited from the credit card. This value can differ from subsequent transactions. MyGate RCCB Page 3

4 Subsequent Transactions The subsequent transaction will be for a subsequent recurring debits to the credit card. MyGate will initiate the subsequent transactions based on the information passed in the initiated transaction. In the event that the card has expired a subsequent transaction will not be initiated. The debit date and period would have been defined in the initiated transaction. Amending Card Detail In the event that any information changes on the card such as PAN or expiry date a new initiated transaction must be initiated by the card holder on the merchants website. Expired Card Lookup It is recommended that when the initiated transaction takes place to ensure that the card expiry date and the collection end date are the same. MyGate s Role in RCCB The below illustrates MyGate s role in RCCB: 1. Receive form post request 2. Security validation 3. Data integrity validation 4. Store data related for subsequent debits 5. Process authorization and settlement request 6. Process merchant response. Subsequent Transactions 1. Initiate subsequent transaction to bank based on: a. Start Date b. End Date c. Card Expiry d. Frequency 2. Decrypt card data 3. Process authorization and settlement request Developers Integration Role in RCCB RCCB - My Virtual Solution If you are integrating to RCCB - My Virtual solution, MyGate will host the payment pages. The MyGate hosted payment page can be configured to the merchants look and feel from the MyGate Web Console. The below is a brief description of the developers role in the process: MyGate RCCB Page 4

5 1. Calculate the start date of the subsequent debit from the initiated transaction 2. Data Preparation 3. Create Form Post 4. Prepare Form Post Response RCCB - My Enterprise If you are integrating to RCCB - My Enterprise solution, the merchant will host the payment page. RCCB - Enterprise requires that SSL is active on merchants website. The below is a brief description of the developers role in the process: 1. Calculate the start date of the subsequent debit from the initiated transaction 2. Data Preparation 3. Collect Card Data on Payment Page 4. Initiate Web Service Request 5. Prepare Web Service Response 6. Insert to Merchant Database Subsequent Transactions It is important to note that no form post or web service is returned on a subsequent transaction. In order to access subsequent transactional data you can: 1. Log into the MyGate Web Console and download a transaction report. 2. Integrated to the MyGate Transactional Persistence Report. Merchants Role in RCCB Within the MyGate Web Console MyGate provides reporting screens to manage RCCB solution. Manage RCCB Once a RCCB transaction has been processed to MyGate (the initiated transaction) you can use the Manage RCCB section to view information related to that RCCB Client Within Manage RCCB you can: View RCCB Clients Edit RCCB Detail View Transaction Processed against the RCCB Client Cancel or Pause subsequent RCCB debits Note: For more information on Manage RCCB refer to the Recurring Credit Card Billing User Manual. MyGate RCCB Page 5

6 Perform Manual RCCB Perform Manual RCCB is used in the event that a RCCB debit is unsuccessful and you need to manual process a credit card debit against the cardholder. This can happen due to their being insufficient funds or processing failure. From within this area the merchant can view the expected debits based on the date and frequency. In the event a debit failed, they can manually initiate a subsequent debit. Note: For more information on Manage RCCB refer to the Recurring Credit Card Billing User Manual. Terminology Term API Authorization & Capture Authorization Capture Credit CVV PCI Compliance Processing Methods Settlement Subsequent Transactions Void Definition API stands for Application Programming Interface A 'purchase' transaction is the most common transaction type. Successful purchase transactions result in funds being debited from the credit card holder s account and deposited into the merchant s electronic merchant facility. This transaction type is sent for authorization only. The transaction will not be sent for settlement until the credit card transaction type Capture (see definition below) is submitted, or the transaction is submitted for capture manually in the Merchant Interface. This transaction type is used to complete a previously authorized transaction A 'credit' is a transaction type where funds are debited from the merchant s electronic merchant account and credited to the card holder. This is also known as a refund. Refunds can be processed from within the MyGate Web Console. The Card Verification Value/Code is a security number which is found on all credit cards. This number is required for additional identity verification and fraud prevention. This is the transaction that is used to submit the original transaction with subsequent transaction parameters. Payment Cards Industry Standard (PCI) is a standard created by MasterCard and Visa to ensure that card data is stored securely. These are the solutions that MyGate provides to merchants for processing of credit card transactions The process by which merchant and cardholder banks exchange financial data and value resulting from sales transactions, cash disbursements and merchandise These are the subsequent RCCB debits that MyGate initiates against the credit card based on the parameters passed through on the initiated transaction. This transaction type is used to cancel an original transaction that not yet settled and prevents it from being sent for settlement. By voiding the transaction it will not be batched and processed to the acquirer. MyGate RCCB Page 6