课程内容

An action corresponds to the combination of a payment mechanism and a command. The concept of an action is used within the documentation and examples as a means of describing functionality. The Enterprise API and iVeri Gateway use the concepts payment mechanism and command instead of Action.

The iVeri Gateway allows for the following actions:

Authorisation with PAN

Reserve funds when a card is not present. 

This action is commonly known as a "Pre-Auth/Pre-Authorisation"

 

Authorisation with Track2

Reserve funds when a card is present. Funds reservation is not applicable for cards requiring a PIN.

This action is commonly known as a "Pre-Auth/Pre-Authorisation"

Authorisation with

VisaCheckoutCallID

Reserve funds when a card is present. Funds reservation is not applicable for cards requiring a PIN.

This action is commonly known as a "Pre-Auth/Pre-Authorisation"

Usage: The use of the VisaCheckout CallID is only applicable to Visa Checkout Transactions 

 

Additional Authorisation with

 TransactionIndex

Increase the amount previously reserved via iVeri by an additional amount. 

Note: The addition of funds previously reserved outside the iVeri Gateway is not supported.

 

Authorisation Reversal with

TransactionIndex

Release the funds previously reserved on the cardholders account via the iVeri Gateway. 

NOTE:The release of funds reserved outside the iVeri Gateway is not supported.

 

Debit with PAN

Transfer of funds from cardholder to merchant when a card not present. The use of an AuthorisationCode previously obtained outside the iVeri Gateway is supported.

 

Debit with Track2

Transfer of funds from cardholder to merchant when a card is present. The use of an AuthorisationCode previously obtained outside the iVeri Gateway is supported.

 

Debit with PIN

Transfer of funds from cardholder to merchant when a card requiring a PIN is present.

 

Debit with TransactionIndex

Transfer of funds from cardholder to merchant. Follow up of an action previously sent to the iVeri Gateway. Not supported for cards requiring a PIN.

 

Debit with VisaCheckoutCallID

Transfer of funds from cardholder to merchant. 

NOTE: Follow up of an action previously sent to the iVeri Gateway is not supported for cards requiring a PIN.

 

Credit with PAN or Tokenised card data 

Transfer of funds from merchant to cardholder when a is card not present.  When used, the refund is not linked to an original transaction, it is deemed a stand-alone refund.

Usage: applicable for use cases where a merchant wants to refund a customer without having an original transaction.

 

Credit with Track2

Transfer of funds from merchant to cardholder when a card is present. Credit is not currently supported for cards requiring a PIN.

 

Credit with TransactionIndex

Transfer of funds from merchant to cardholder. Follow up of an action previously sent to the iVeri Gateway. Not supported for cards requiring a PIN.

Usage: Applies in uses cases where a merchant has an original transaction and either part or full refund of the original transaction is required

 

Credit with VisaCheckoutCallID

Transfer of funds from merchant to cardholder. Follow up of an action previously sent to the iVeri Gateway. Not supported for cards requiring a PIN.

 

Void

Cancel a transaction command within a short time after the command was initiated.  See more on ensuring end-to end transaction integrity 

 

Balance Enquiry with PIN

Obtain the balance of the PIN based account in the currency of the account. 

Note that this currency may be different to the currency of the merchant.

 

PAN Enquiry with PAN

Obtain information about a card (which is not present) without performing a transaction, for example to check if the card is a hot card or blacklisted by the merchant.

 

PAN Enquiry with Track2

Obtain information about a card (which is present) without performing a transaction, for example to check if the card is a hot card or blacklisted by the merchant. PAN Enquiry is not currently supported for cards requiring a PIN.

 

 

PAN Token Enquiry

Obtain a TransactionIndex for the card number and expiry date without performing a transaction. The TransactionIndex is to be used in a Tokenized transaction.

Usage: Tokenise a card without doing a transaction and use the token on subsequent transactions.

 

Ping

The Ping command is primarily used to determine if the connection status between the Merchant and the Acquirer. If the connection is down, then the Ping command can also be used to check when the status is back up.

Usage: To check the status of the Gateway is up or down

 

Get Device PIN Key

Get the current Triple DES session key for a device. See PIN based transactions (section Error: Reference source not found).

 

ThreeDSecureCheckEnrollment

Check the CardHolders 3DSecure Enrollment.

NOTE: Only applicable to 3DS 1 integrations

 

ThreeDSecureValidateAuthentication

Validate the CardHolders 3DSecure Authentication process

NOTE: Only relates to 3DS 1 integrations

 

RequestForDebit

A Request for a Debit (Sale) which contains a payment Link is generated by the Gateway onbehalf of the merchant and can be distributed to the customer by the Gateway or using the merchants distribution channels such as SMS or EMAIL etc

Usage: Only applicable to the Divert solution and where merchants wants to embed the payment Link into their own applications.

 

MasterPassQuickResponseCode

Generating / Managing a transactional code that can be paid for by a cardholder. See MasterPass section.

 

DynamicCurrencyConversion

Generating / Managing a transactional code that can be paid for by a cardholder. See Dynamic Currency Conversion 

 

MultiCurrencyPricing

Generating / Managing a transactional code that can be paid for by a cardholder. See Multi Currency Pricing section.

 

MasterPassPaymentNotification

Inquiring whether a payment notification has been received from MasterPass.

 

UPOPAuthenticationRequestCreation

The creation of the Authentication Request message to be posted to the UPOP authentication server. See UPOP Authentication Request section 

NOTE: Only applicable to UPI cards and support is dependent on the acquiring bank

 

UPOPAuthenticationRequestValidation

The validation of the Authentication Response message received from the UPOP authentication server. See UPOP Authentication Request section.

NOTE: Only applicable to UPI cards and support is dependent on the acquiring bank


视图
706 总浏览
2 成员的观点
1032 公众浏览
操作
0 喜爱
0 不喜欢
0 注释
分享到社交网络
分享链接
通过邮件分享

登录 分享这个 webpage 通过电子邮件。