Bharaat eCommerce Payment Gateway
When you request an authorization using a supported card type and a supported processor, you
can include payer authentication data in the request.
During an online purchase,
RuPay
Bharat eCommerce
Payment Gateway (BEPG) Redirection Flow redirects the customer to an issuer-provided
authentication page that protects payment information as it is transmitted over the
Internet.Before implementing payer authentication, contact customer support to have your account
configured for this feature.
Fields Specific to the Bharat eCommerce Payment Gateway Use Case
- Set the value to INR.
Endpoint
Set the
ccAuthService_run
field to
true
.Send the request to
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
.Related Information
Authorizations Using Redirection Flow
Redirection flow authenticates the customer by directing the customer from the merchant site
to an authentication page that is hosted by the issuer.
Required Fields for Processing an Authorization Using Seamless Flow with an Account
Number (No Token)
These fields are required when you use an account number in an authorization request
for seamless flow. The values for these fields are in the response from the payer
authentication validate service. When you request the payer authentication validate
and authorization services together, the data is automatically passed from one
service to the other.
- billTo_city
- billTo_country
- billTo_email
- billTo_ipAddress
- billTo_lastName
- billTo_postalCode
- billTo_state
- billTo_street1
- card_accountNumber
- card_cvNumber
- card_expirationMonth
- card_expirationYear
- ccAuthReply_requestAmount
- ccAuthService_aggregatorID
- Required for an aggregator or seller. Otherwise, this field is optional.
- ccAuthService_commerceIndicator
- Set the value torpy.
- invoiceHeader_submerchantID
- Required for an aggregator or seller only whenccAuthService_aggregatorIDis not present in the response from the payer authentication validate service. Otherwise, this field is optional.
- invoiceHeader_submerchantName
- Required for an aggregator or seller. Otherwise, this field is optional.
- merchantReferenceCode
- orderInformation.billTo.firstName
- payerAuthEnrollService_httpAccept
- payerAuthEnrollService_httpUserAgent
- purchaseTotals_currency
- Set the value toINR.
Related Information
Optional Fields for Processing an Authorization Using the Seamless Flow with an Account
Number (No Token)
You can use these optional fields to include additional information when processing
an authorization using the seamless flow with an account number (no token)
method.
- If you do not send this field, the system time in Indian Standard Time (IST) is used.
Related Information
Simple Order Example: Redirection Flow
Request
billTo_city=Bangalore billTo_country=IN billTo_email=johndoe@example.com billTo_firstname=John billTo_lastname=Doe billTo_postalCode=01310-000 billTo_state=KA billTo_street1=201RedSt card_accountNumber=6074819900XXXXXX card_expirationMonth=12 card_expirationYear=2026 ccAuthService_run=true ccAuthService_cavv= WhPlErd9WE1234562pb1yFjFHlewUIQwQ ccAuthService_commerceIndicator=rpy ccAuthService_xid=WhPlErd9WE1234562pb1yFjFHlewUIQwQ ccAuthService_veresEnrolled=Y payerAuthEnrollReply_paresStatus=Y merchant_id=MID23 merchant_referenceCode=Merchant_REF purchaseTotals_currency=INR purchaseTotals_grandTotalAmount=100
Successful Response
merchantReferenceCode=Merchant_REF request_id=6461515866500167772420 decision=ACCEPT reasonCode=100 purchaseTotals_currency=INR ccAuthReply_cardCategory=F ccAuthService_reconciliationID=ZUDCXJO8KZRFXQJJ ccAuthReply_reasonCode=100 ccAuthReply_amount=100.00 ccAuthReply_avsCode=5 ccAuthReply_authorizationCode=570110 ccAuthReply_processorResponse=1 ccAuthReply_authorizedDateTime=2023-03-01T161947Z ccAuthReply_paymentNetworkTransactionID=111222