Requirements for the RCS payment method:

📘

Note:

A merchant agreement with RCS is required in order to use the RCS payment method. (Please contact Ecentric Product support for more details.)

Merchants can opt to send either customer authenticated or non-authenticated transactions.

Please note: that merchants will need to advise RCS of the intention to use non-authenticated transactions as this requires a different setup process.

1. Authenticated Transactions

The following diagram illustrates the payment flows for authenticated RCS transactions:

2. Non-authenticated Transactions

Where customer OTP authentication is not required, merchants will not call the Secure3DLookup and the payment flow is illustrated in the diagram below:

API messaging

AddCard

RCS cards can be saved for future use using the AddCard method.

When adding an RCS card:

• CVV is not required.
• Expiry date not required.

Example card:

<Card>
<CardholderName>Joe Blogs</CardholderName>
<CardNumber>6010248200009035453</CardNumber>
</Card>

Secure3DLookup

Merchants will send the Secure3DLookup method to authenticate transactions:

• Expiry date is not required.
• CVV is not required

Example of Secure3DLookupRequest using a Full Card PAN

• CardholderName is required

<Secure3DLookupRequest>
<MerchantID>8B67BF88-BB8D-4EB5-ADFC-0F5C97C7ED67</MerchantID>
<MerchantUserID>978e566b-d62a-42c0-9843-381b3588f333</MerchantUserID>
<TransactionID>0f750d6e-5336-4da1-9cd5-1896797f5f54</TransactionID>
<Amount>50</Amount>
<CurrencyCode>ZAR</CurrencyCode>
<OrderNumber>MR64503998</OrderNumber>
<Card>
<CardholderName>Joe Blogs</CardholderName>
<CardNumbr>6010248200009035453</CardNumber>
</Card>
<PaymentService>CardNotPresent</PaymentService>
<TermUrl>http://localhost:3000/term-url</TermUrl>
</Secure3DLookupRequest>

Example of Secure3DLookupRequest: using a Token

• CardholderName is not required

<Secure3DLookupRequest>
<MerchantID>8B67BF88-BB8D-4EB5-ADFC-0F5C97C7ED67</MerchantID>
<MerchantUserID>978e566b-d62a-42c0-9843-381b3588f333</MerchantUserID>
<TransactionID>0f750d6e-5336-4da1-9cd5-1896797f5f54</TransactionID>
<Amount>50</Amount>
<CurrencyCode>ZAR</CurrencyCode>
<OrderNumber>MR64503998</OrderNumber>
<Card>
<Token>6CC36FEF-14C8-4F6F-A39C-1C077DAAAE3B</Token>
</Card>
<PaymentService>CardNotPresent</PaymentService>
<TermUrl>http://localhost:3000/term-url</TermUrl>
</Secure3DLookupRequest>

Example of RCS OTP capture page:

Authorize or Payment

RCS cards are processed using PaymentServiceType of CardNotPresent or CardNotPresentRecurring.

• CVV and expiry are not required

Use Case

📘

Note:

RCS requires API merchants to display the supported RCS card images per BIN (first 6 or 8 digits of a card) as well as the specific logo of the card BIN entered when making an RCS card payment.

Please contact Ecentric Product Support for RCS logo pack.

Budget Facility

API merchants are required to ensure they cater for the below where the budget facility (BudgetPeriod in an Authorize or Payment request) is offered:

• Only the budget plans (24/36 month) are available for the listed BINS where the transaction is R600 or greater.
  • All other BINS will only support Straight payment.
  • 3/6/12 month budget offerings are not available for any BIN.
• Any RCS budget card transaction that does not comply with the below requirements will decline with an “05 - do not honor”

Refund or Void

Refund and Void transactions for RCS are required to use PreviousTransactionID using the original payment or authorize transaction id as per normal refunds or voids.