Page Comparison

...

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

Setup Call: No token exist at this time.

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>

Response: Token created and returned by PayU on successful transaction completion.

• pmId = This value needs to be associated with merchantUserId and used for Enterprise payments. (Back-end Real-Time recurring transactions)

...

• cardExpiry = Store this value to ensure recurring transactions are not requested beyond expiry date of card
• cardNumber = Purely used by merchants for statistical reasons and UI selection

<pmId>C113C08A96F9E1177DB441EAB08DC046</pmId>
<cardExpiry>102018</cardExpiry>
<cardNumber>403822******8021</cardNumber>

Additional payments: Tokens exist and used in place of credit card values. No expiry or CVV required. 

• AuthenticationType = TOKEN

• merchantUserId = Identifying value at merchant

• CreditCard
  • pmId = Token representing the card. For additional recurring transactions this can be send without CVV.

• 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>
 
<Creditcard>
  <amountInCents>1000</amountInCents>
  <pmId>f1VnURZ/QBV6FVVpJhBgVGdVEHFFDANFFBAWNj5RZkkRekQQehJec1xke1Fl</pmId>
  <cvv></cvv>
</Creditcard>
<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.some de-risking of transactions can be done be performing a normal .

Simple payment sequence integration:

...

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

...