Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This page serves as a supplementary guide for integrating Real-Time Recurring Credit Card transaction payment into the payment flow and is to be read in conjunction with the PayU Enterprise API integration documentation.

Overview

PayU Real-Time Recurring (RTR) transaction processing is a card processing solution where the merchant is allowed to deduct specified amounts from a card holder's account as agreed between card holder and merchant without the card holder initiating the actual transaction. Real-Time Recurring (RTR) Credit Card transaction solution is available on the PayU payment system via both the API and responsive channel through tokenised enterprise API integration. API channel due for release last quarter of 2015 with redirect following shortly during first quarter 2016. Please consult with PayU Sales for more information.

Real-Time recurring transactions are set-up by providing full card data (Card holder provide during agreement process) for transaction authorisation initially and on subsequent transactions only the card number is required to authorise payment to the merchant. To assist Enterprise merchants in reducing PCI exposure with API integrations PayU offers RTR as a tokenised payment solution. The card details will be encrypted by PayU and stored in a token which should be stored against a merchant user profile for future recurring transactions. Future transactions can happen via administrative process or on-line transactions where card holder launch payment process.

Merchants using Real-Time Recurring transactions are always liability for charge-backs from issuers. For some chargeback risk reduction Real-Time Recurring transactions can be paired with eCommerce transactions with Secure 3D during the setup transaction. More details below on the flows. Enterprise merchants needs to manage the flow, for redirect merchants PayU will ensure correct flow is applied based on transaction perimeters.

Merchant Requirement

Merchant will need to have the following in place before attempting Real-Time Recurring integration. 

  • User profile system with secure login process for merchant users.
  • Capabilities to store one or more PayU created payment tokens against user profiles.
  • UI with some processing intelligence to make decisions on:
    • displaying card capture for new users or users without tokenised cards.
    • ability to add new card to be tokenised against user profile
    • Ability to display a list of one or more tokenised cards for payment selection.
  • Back-end processing capability to process recurring subscription transactions.

Additional considerations:

For Enterprise Integration: As card holder data is captured on the merchant's hosted pages the merchant needs to be PCI compliant to the level required by the acquiring bank and PCI-DSS guidelines. Merchants do not need to save sensitive card holder information. The merchant needs to be able to save the token value returned in the API response against the user profile to re-use for future payment requests.

For Redirect Integration: No sensitive card holder data will be exposed to the merchant, all card capturing happens at PayU. The merchant can still process back-end transactions via Enterprise API by making use of the tokens.

To ensure integration is a smooth process please ensure that integration is first completed and tested on the PayU Staging platform before switching to production.

doTransaction amendments for Real-Time Recurring Credit Card Transactions (RTR)

Setup Call: Merchants will need to make the following amendments to the normal doTransaction API call in order to do Real-Time Recurring Credit Card transactions with and without tokens on the PayU platform. All credit card details are required during setup. 

  • AuthenticationType = TOKEN
  • storePaymentMethod = TRUE

  • merchantUserId = Identifying value at merchant

  • Customfield

    • key = processingType

    • value = REAL_TIME_RECURRING

 

<AuthenticationType>TOKEN</AuthenticationType>
 
<AdditionalInformation>
  <storePaymentMethod>true</storePaymentMethod>
</AdditionalInformation>
 
<Customer>
  <merchantUserId>123</merchantUserId>
  <regionalId>123456</regionalId>
  <countryCode>27</countryCode>
</Customer>
 
<Customfield>
  <key>processingType</key>
  <value>REAL_TIME_RECURRING</value>
</Customfield>

 

Additional payments 

  •  

 

<AuthenticationType>TOKEN</AuthenticationType>
<AdditionalInformation>
  <storePaymentMethod>true</storePaymentMethod>
</AdditionalInformation>
<Customer>
  <merchantUserId>123</merchantUserId>
  <regionalId>123456</regionalId>
  <countryCode>27</countryCode>
</Customer>
<Customfield>
  <key>processingType</key>
  <value>REAL_TIME_RECURRING</value>
</Customfield>

 

  • Integration payment sequence/flow

When developing a solution with PayU's Enterprise API you will need to cater for the implementation user profile management section against which a token can be stored for future recurring payments..

Simple payment sequence integration:

  • todo

Example of the stored card selection page developed by the merchant

todo

  • API call examples

Please refer to the doTransaction API example page for more information

 

  • No labels