Remote Host Authorization

Remote Host Authorization (RHA) is a functionality that provides you as an on-boarding partner, the capability to authorize (or forbid) real-time transactions.

When a cardholder attempts to make a card transaction via ISAC Switch system, the following process occurs:

  1. The merchant sends an authorization message to the card network.

  2. The card network sends an authorization message to the Switch platform.

  3. The Switch platform translate the ISO message and authenticates the request.

  4. Switch platform forwards the authorization request to the remote host.

  5. The remote host authorizes the request and sends the transaction response.

  6. The response received from the remote host is mapped to the network's response code and is sent to the network.

  7. Finally, the switch platform sends the transaction notification to the webhook endpoint.

Transaction Flow

To configure RHA, you must follow the below steps:

  1. Send a one-on-one email to vatech POC, containing a username, password, and URL.

  2. This URL must be configured to accept a POST request and validate it using basic authentication.

  3. The request timeout is set to 4 seconds, so make sure you perform all your operations within the timeout duration.

  4. You must respond back with either of the following http status codes. Any other statuses will be treated as the Remote Host’s server fault and the vatech platform will deny this transaction.

    • 200 - Transaction Approved By Remote Host

    • 402 - Transaction Denied By Remote Host

  5. For Balance Enquiry transactions, you are expected to send 200 http status code and balance in the response. A sample response is mentioned below

RHA Request

RHA Response

RHA Request Details

Field Name
Data Type
Required
Description

txn_log_id

string

M

Unique reference to the transaction

card_id

string

M

Reference to the card

user_id

string

M

Reference to the user

account_id

string

M

Account Id of the user

txn_date

string

M

Transaction Date time stamp

txn_type

string

M

Refer below for more details

txn_code

string

M

Refers to transaction code

channel

string

M

Mode of the transaction (POS, ATM, ECOM)

mcc

string

M

Merchant category code

mid

string

M

Merchant Id

rrn

string

M

Retrieval Reference Number

stan

string

M

-

terminal_id

string

M

Terminal Id

aid

string

M

Acquirer Id

is_afd_applicable

bool

M

Denotes if afd is applicable

acquiring_details.amount

numeric

M

Transaction’s Acquiring Amount

acquiring_details.currency.alpha_code

string

M

Transaction’s Acquiring Currency

acquiring_details.currency.numeric_code

numeric

M

Transaction’s Acquiring Numeric Code

account_balance.amount

numeric

M

-

account_balance.currency.alpha_code

string

M

-

account_balance.currency.numeric_code

numeric

M

-

authentication_details.pin_verified

bool

M

Denotes if pin is verified

authentication_details.cvv_verified

bool

M

Denotes if cvv is verified

merchant.name

string

M

Merchant name

merchant.city

string

M

Merchant city

merchant.state

string

M

Merchant state

merchant.country

string

M

Merchant country

txn_details.amount

numeric

M

Transaction Amount

txn_details.currency.alpha_code

string

M

Transaction Currency Code

txn_details.currency.numeric_code

numeric

M

Numeric Transaction Currency Code

txn_details.fee_details.fee_applicable

bool

M

Denotes if there is any transaction fees applicable

txn_details.fee_details.amount

numeric

M

Fee amount

txn_details.fee_details.currency.alpha_code

string

M

Fee currency

txn_details.fee_details.currency.numeric_code

numeric

M

Numeric code for fee currency

sub_txn_type.txn_condition

string

O

This refers to the sub type of transaction such as EMI/SI. Possible values are EMI_TRANSACTION, STANDING_INSTRUCTION, ACCOUNT_STATUS_INQUIRY

sub_txn_type.mandate.is_applicable

bool

O

Denotes if mandate is applicable

sub_txn_type.mandate.txn_type

string

O

Denotes type of SI transaction. Possible values are REGISTER_MANDATE, DEREGISTER_MANDATE, UPDATE_MANDATE, INTIMATE_PRE_DEBIT, DEREGISTER_MANDATE_FOR_CARD

sub_txn_type.mandate.number_of_instalments

string

O

Denotes total number of payment instalments

sub_txn_type.mandate.init_date

string

O

Preferred date for SI initialization

sub_txn_type.mandate.min_amt

string

O

Minimum Amount for which SI can be initiated.

sub_txn_type.mandate.max_amt

string

O

Maximum Amount for which SI can be initiated.

sub_txn_type.mandate.start_date

string

O

SI start date

sub_txn_type.mandate.end_date

string

O

SI end date

sub_txn_type.mandate.mode

string

O

SMS/EMAIL

sub_txn_type.mandate.freq_indicator

string

O

Mandate frequency indicator(DAILY/WEEKLY)

sub_txn_type.mandate.txn_id

string

O

Mandate id populated by npci during mandate registration

sub_txn_type.emi.is_applicable

bool

O

Denotes if EMI is applicable

sub_txn_type.emi.amount

string

O

EMI amount

sub_txn_type.emi.total_amount

string

O

Total amount

sub_txn_type.emi.number_of_instalments

string

O

Number of EMI instalments

sub_txn_type.emi.interest_rate

string

O

EMI interest rate

Transaction Types

txn_type

Description

txn_indicator

AUTH

Card Authorization transaction

Debit

AUTH_ADVICE

For any card authorization, if any pre-auth was done, you will get the actual transaction details here.

Debit

REVERSAL

This is the immediate reversal of the authorized transactions.

Credit

REVERSAL_ADVICE

This is the immediate reversal of the authorized transactions.

Credit

CLEARING_REVERSAL OR CR_EXTEND_LIMIT

This is the reversal due to settlement - An example: Payments on Credit Flipkart/Amazon. If you are returning an item, the refund amount gets posted back to the cardholder. Here the txn_type will be CLEARING_REVERSAL. This is basically known as Refunds.

Credit

FP_AE_CLEARED OR FP_AE_EXTEND_LIMIT

This is the reversal due to Acquirer Merchant Claim - If the cardholder does a Credit AUTH transaction of 1000 INR and the acquirer merchant claims only 990 INR, then a reversal of 10 INR is posted to the cardholder. Here the txn_type will be F P_AE_CLEARED. This scenario is very less frequent.

Credit

FP_CE_CLEARED OR FP_CE_WITHDRAW_LIMIT

n case, the acquirer merchant claims more than the authorized Debit transaction(surcharge on IRCTC, fuel stations, etc), an extra debit is posted to the cardholder.

Debit

ADJUSTMENT

When merchant sends the first presentment for a transactions which was immidiately reversed, we create a transaction of type ADJUSTMENT to debit the cardholder.

Debit

Last updated