Merchant_Administration_User_Guide
Merchant_Administration_User_Guide
Merchant Administration
User Guide
4 October 2024
MGMA
Contents
Contents
Notices.................................................................................................................................................... 138
Intended audience.................................................................................................................................................11
Getting support.....................................................................................................................................................11
Before you begin ...................................................................................................................................................12
Types of merchant profiles..................................................................................................................................12
Getting started..................................................................................................................................................... 12
Feature access in Merchant Administration...............................................................................................12
Process transactions in test mode and real time.......................................................................................13
Log in to Merchant Administration.............................................................................................................. 13
Login fields description............................................................................................................................. 13
Log out of Merchant Administrator.............................................................................................................14
Password management ................................................................................................................................ 14
Options to reset a forgotten password................................................................................................. 14
Request a temporary password.........................................................................................................15
Merchant Administration menu......................................................................................................................... 16
Merchant Administration homepage ..........................................................................................................16
Merchant Admin is an online self-service portal allowing merchants to easily view and manage their
transactions. The tool offers a web-based application that enables users to search and view payment
details, download csv reports, check 3DSecure results, set up risk controls, process transactions
manually, and manage refunds.
It can be securely accessed at any time and from anywhere with password strength requirements and
password meter applied to all its users.
Intended audience
This guide is intended for merchants and operations personnel using Merchant Administration,
and requires knowledge of the following:
• Web applications.
• Commercial practices.
• Merchant operational procedures of card processors.
• Transaction system operations.
Getting support
If you need support with Merchant Administration, contact CTS (Gateway Support Team) on
[email protected].
Test merchant Let's you perform test transactions against an emulator of the transaction
profile processing system. The test merchant profile always has TEST prefixed to the
production Merchant ID.
Using the test profile is an ideal way to become familiar with Merchant
Administration as it allows you to create orders, test transactions and use
other areas of the system without affecting your production system.
Production Let's you perform transactions directly against the live transaction
merchant processing system when you are satisfied with your test transactions. Be
profile aware that funds will be transferred from payer accounts.
Getting started
Authorized Operators can log in from the Login screen and use the various features of Merchant
Administration.
Authorized merchant personnel must be set up as operators before they can log in and use
various features of Merchant Administration. For more information, see Merchant
Administration operator operations.
Procedure
1. Go to Merchant Administrator login page.
2. Enter your Merchant ID.
3. Enter your Operator ID.
4. Enter your Password.
5. Select the Forgot Password link if the password requires a reset.
The system prompts you to change your password if the last password was changed before
90 days. Change any compromised password as soon as you can.
6. Select Log In.
Field Description
Merchant ID Unique alphanumeric identifier of a merchant
provided with each merchant account or profile.
Operator ID The operator ID.
Password The password must have the following attributes:
• It must be at least eight characters long.
• It must contain at least one alphabetical
character.
• It must contain at least one numeric character.
• Is case sensitive.
Procedure
1. Go to Merchant Administrator homepage.
2. Select the Logout link on the upper right corner of the screen.
Password management
The MSO provides the administrator password, while the Merchant Administration
Administrator provides the operator password.
If you forget your password, reset it using the Forgot Password Link from the Login screen. For
more information, see Options to reset a forgotten password.
NOTE: The administrator cannot process transactions. If you wish to process transactions, sign in with
an Operator ID. For more information, see Create a New Operator.
NOTE: The Forgot Password link displays only if your MSO supports the password reset functionality.
If you have made five or more unsuccessful log-in attempts using an incorrect password, reset
your password. You have two options to reset your password:
• Reset using the Forgot Password link.
• Contact the Administrator for a password reset, if one or more of these statements are true:
– An email address is not available against your operator profile.
– You have access to the privilege Enable Advanced Merchant Administration Features.
– You have access to the Perform Operator Administration privilege.
– You are the primary operator, also known as Administrator for the merchant profile.
– The operator with administrative privileges enables the Lock Operator Account privilege
on your profile.
– Your authentication was successful with the right password, but the account got locked.
The system recommends you contact the Administrator to unlock your account.
NOTE: For more information about how an administrator can change the operator password, see
Change an operator password.
Procedure
1. Go to the Login page.
Figure 1: Login page
Field Description
Home Access dashboard, shortcuts for order creation,
order and transaction search, and risk actions if
enabled for Risk Management.
Search Access orders, financial transactions, payment
authentications, and token details.
Orders Create an initial order manually or perform address
verification.
Batches Operation to upload batches.
Settlement Search Search for presettlement summary or settlements.
Reports Select and view reports.
Risk Management Access Risk Management solution of the gateway
if enabled for internal risk.
Admin Setup operators, change password, download
software, configure integration settings. Enable
reporting API integration access and so on.
Logout Log out and return to the login page.
The features provided by your payment gateway and the operator privileges assigned to you
determine the administration options available to you. For more information about privileges,
see the general privileges table in Merchant Administrator operator details.
Your dashboard
The dashboard provides a summary view of your transaction activity that enables you to view
key performance data at a glance.
Shortcuts
The shortcuts bar provides quick access to common tasks that you might need to perform on a
day-to-day basis. Select a shortcut to go to a relevant page to proceed or cancel a task. The
currently available links to common tasks are:
• Create a new order: Takes you to the Order Entry page.
• View orders created today: Takes you to the Order and Transaction Search page where all
orders with start and end date set to Today are displayed in the search results.
• View transactions processed today: Takes you to the Order and Transaction Search page
where all transactions with start and end date set to Today are displayed in the search
results.
• Risk assessments for review (n):
– This link displays only if the merchant operator has the May Perform Risk Assessment
Review privilege.
– The number of orders pending review and created within the last 60 days are represented
by n.
– Select this link to go to the Order and Transaction Search page where all orders with a
pending risk review, created within the last 60 days displays in the search results.
The admin function enables merchants to easily manage their system operators, securely change
integration settings, and set up various profile and access preferences. One of the admin functions,
the Operator list, enables authorized users to set up and manage different system operators as well
as their passwords, specific user rights, and privileges. The Emails section enables merchants to
configure preferred gateway notification settings and control all notifications sent directly to their
customers.
NOTE: The links provided in this guide are for a test environment. To access a production environment,
you must follow the appropriate steps. The Merchant Admin Portal may be accessed as an
administrator or user.
Procedure
1. Go to Admin, and then select Configuration Details.
The Admin - Configuration Details page is displayed.
2. In the Admin - Configuration Details, you can view Merchant and Internationalization
sections.
Configuration Details
The Configuration Details page allows you to view details of merchant configuration.
The following table describes the configuration details.
Field Description
Merchant Name The registered business, trading, or organization
names of merchants.
Merchant ID The merchant's unique alphanumeric identifier.
There are unique merchant IDs for merchant
accounts and profiles.
NOTE: You cannot change the Merchant Name and Merchant ID. Contact your MSO to change these
fields.
The Internationalization section on the Configuration Details screen contains the following
information:
Field Description
Locale The default locale for merchant administration
unless overridden by the operator locale.
Time Zone The default time zone for merchant administration
unless overridden by the operator time zone.
NOTE: You cannot change Locale and Time Zone. Contact your MSO to change these fields.
Manage an operator
You can create and edit a Merchant Administration Operator.
Procedure
1. Go to Admin, and then select Operators.
The Admin - Operator List page is displayed.
2. You can choose to create an operator, edit an operator, change an existing operator's
password, or delete an operator.
Figure 2: Admin - Operator List page
Procedure
1. Go to Admin, and then select Operators.
Field Description
Merchant Merchant's unique alphanumeric identifier. There is
a unique merchant ID for each merchant account
or profile.
Operator ID Unique identifier of the merchant operator.
Operator Name Name of the operator.
Description Extra description of the user. For example, job title,
department, and level of privileges allocated.
Password Password must be at least eight characters long
and contain at least one alphabetical, one special,
and one numeric character. The password is case-
sensitive. For more information about the
password requirements, see Password
configuration compliance.
Confirm Password Reenter the password to confirm
Email Address Operator's email address. If your MSO supports
the password reset functionality, then you receive a
temporary password on this email address when
the operator uses the forgot password link from
the login screen to request a password reset.
Locale Default language displayed in Merchant
Administration unless overridden by the operator.
Time Zone Operator's time zone.
Field Description
Lock Operator Account Enables an operator with administration privileges
to lock out an operator. The locked-out operator
cannot log in to Merchant Administration until an
operator with administration privileges clears the
check box to re-enable the operator
The system locks an operator account with more
than 90 days of inactivity.
Must Change Password at Next Login If you select this check box, the operator needs to
change the password on the next login.
Password Reset Required Indicates to reset the password. This field is set to
Yes after five failed login attempts or else set to
No.
You may request a password reset using the
Forgot Password link on the Merchant
Administration login screen or contact the
administrator for a password reset. For more
information about how to reset an operator's
password, see Changing an Operators Password.
View Unmasked Account Identifiers Enables the operator to view unmasked account
identifiers such as, card number, gift card number
when viewing order, and transaction details.
Field Description
Perform Verification Only Enables the operator to create a verify only
transaction to verify the status of a credit card
before performing a transaction.
Perform Authorizations Enables the operator to create an authorization
transaction using the Create Order option. An
authorization transaction reserves fund on the
payer's credit card.
Perform Captures Enables the operator to capture previously
authorized funds.
Field Description
Perform Purchases Enables the operator to create a purchase
transaction using the Create Order option. A
purchase is a single transaction to authorize and
capture a payment.
Perform Update Authorizations Enables the operator to update an existing valid
authorization for the authorization period (and or)
increment the authorization amount.
Perform Voids Enables the operator to reverse a previous
transaction. You can perform voids if the
transaction is in an unreconciled batch.
Perform Stand Alone Captures Enables the operator to perform captures for
orders authorized manually, or in an external
system.
Perform Bulk Captures Enables the operator to perform a capture against
a set of selected orders.
Perform Refunds Enables the operator to give refunds. A refund is
the transfer of funds from a merchant to a card
holder.
Perform Standalone Refunds Enables to perform a refund without first creating
a capture or purchase.
Perform Excessive Refunds Enables the operator to perform a refund for
amounts greater than the authorized amount.
Excessive Refund Limit The maximum limit allowed for an excessive refund
more than the authorized amount. Set a refund
limit for each currency configured for the
merchant.
Perform Gaming Winnings Enables the operator to submit transactions that
disburse gaming winnings to the payer's account.
Field Description
May Upload Batch Files Enables the operator to upload batch files to the
payment gateway via Merchant Administration.
The upload option is available through the Batches
tab on the main menu.
Field Description
May Download Batch Response Files Enables the operator to download the batch
response file from the payment gateway. The
download option is available through the Batches
tab on the main menu.
NOTE: Only merchants with the batch privilege can enable Batch operator privileges.
Field Description
Modify the merchant configuration Enables the operator to edit the merchant's
configuration details.
Perform Operator administration Enables the operator to create, edit, and delete
other operator's detail. If MSO supports the
password reset functionality, then enabling this
privilege prevents the operator from using the
Forgot Password link on the Login screen to
request a password reset.
Field Description
Perform Settlements Operator can perform settlements.
View Report Pages Operator can view Gateway Reports.
Download Order Search Results Enables the operator to download order search
results in the CSV format.
Download Transaction and Payment Enables the operator to download transaction and
Authentication Search Results search results of payment authentication in the
CSV format.
Allow Merchant Administration Documentation Enables the operator to download documentation
Download from the Merchant Administration portal.
View Settlement Pages Enables the merchant to view the batch
settlement details.
Initiate Manual Batch Closure Enables the merchant to trigger settlement for a
batch.
May Configure Risk Rules Enables the operator to configure a risk service
provider using the Risk Management module.
Field Description
May Configure Transaction Filtering Enables the operator to configure transaction
filtering rules for a merchant.
May Perform Risk Assessment Review Enables the operator to decide on whether to
accept or reject an order based on the assessment
results from the risk service provider and or
transaction filtering.
May Bypass Risk Management Enables the operator to process orders without
performing the risk assessment on orders. If you
configure both transaction filters and the risk
service provider, this privilege bypasses both at the
merchant level.
May Configure Integration Settings Enables the operator to configure integration
settings for a merchant. The integration methods
include API or Hosted Batch, which allow the
merchant application to connect to the payment
gateway.
May Configure Reporting API Integration Settings Enables the operator to generate passwords used
to integrate with the reporting API and download
transaction reports.
May Configure Email and Webhook Notifications Enables the operator to configure merchant and
customer notifications for payment events such as,
successful payments, successful refunds, and so on.
May Maintain Tokens Enables the operator to delete tokens associated
with the merchant's token repository.
May View Dashboard Enables the operator to view the dashboard on the
home page. The dashboard provides a graphical
indication of the merchant's authorization,
capture, pay, refund, and disbursed transactions
for the selected period.
Configure Surcharge Rules Enables you to configure surcharge rules if you
want the gateway to calculate surcharge for
transactions. Go to Admin > Configure Surcharge
Rules and select the Learn More… link for
information on how to configure surcharge rules.
Edit an operator
This section provides steps to edit an operator.
Procedure
1. Go to Admin from the main menu and select Operators.
The Operator list is displayed after you select Operators.
2. The Edit an Operator section lists all existing operators. Edit an Operator list page displays
the edit an operator section.
Figure 3: Edit an Operator section
a. To edit a particular operator, select Edit. The Admin - Operator Details page is
displayed.
b. To delete a particular operator, select Delete. A message prompts you to confirm the
deletion. Select OK or Cancel as appropriate.
c. To change an operator's password, click the Change Password link. The Admin - Change
Operator Password page is displayed.
3. The Change Password link does not display for the logged in user. Use Admin > Change
Password to change the password of the currently logged in operator.
Figure 4: Admin > Change Password
Procedure
1. Go to Admin from the main menu and select Operators.
The Admin – Operator List page is displayed.
2. Identify the operator to edit and select Edit.
The admin operator details display with the existing values and settings in the fields.
3. Clear the Lock Operator Account check box.
4. Select Submit to commit the changes.
The account unlocks to the selected operators.
Password management
This section briefs about the password management that includes:
• Password requirements.
• Password options.
• Changing a password.
• Change an operator's password.
• Unlock an operator's login.
• Change your password from time to time.
Before you do this, see Before you begin in respective sections.
Procedure
1. Go to Admin from the main menu, and then select Operators.
The Admin – Operator List page is displayed.
2. Identify the operator in the Edit an Operator section and select Change Password link.
The Admin - Change Operator Password page is displayed.
3. Enter the new password and reenter the new password in the Confirm New Password field.
4. Select Submit.
Procedure
1. Go to Admin from the main menu and select Change Password.
The Admin - Change Own Operator Password page is displayed.
2. Enter the old password, the new password, and reenter the new password in the Confirm
New Password field.
3. Select Submit.
Procedure
1. Go to Admin from the main menu.
2. Select Manage Payment Plans from the submenu.
The Manage Payment Plans page is displayed.
NOTE: If you have multiple acquirer links, the Acquirer Link Selection page displays the multiple
links.
3. Add payment plans as required in the Add Payment Plan.
NOTE: Only merchant operators with administrator privileges can view and manage payment
plans.
Field Description
Plan Name The plan name that you select as an identifier for
the payment plan. The plan name must be unique
per payment plan type for the merchant.
Plan Type The MSO operator enables the payment plan types
on your merchant profile. The drop-down list
displays only enabled payment plans for
configuration.
The payment plan options include:
• Pay in installments, interest-free: Pay in
installments for a specified number of months
without any interest payments to the payer.
• Pay in installments, with interest: Pay in
installments for a specified number of months
with interest payments to the payer.
• Pay in installments after a deferral period,
interest-free: Pay in installments for a specified
number of months without any interest
payments to the payer after a deferral period
specified in months.
• Pay in installments after a deferral period, with
interest: Pay in installments for a specified
number of months with interest payments to
the payer after a deferral period specified in
months.
• Pay in full after a deferral period: Pay the full
amount of the purchase after various deferral
months. The customer receives delivery of the
goods at the time of purchase and before
making any payment.
Start Date The start date for the payment plan. It must be
less than or equal to the current date for the
payment plan to be valid.
Field Description
End Date The end date for the payment plan. It must be
greater than or equal to the current date for the
payment plan to be valid.
Minimum Order Amount The minimum order amount for the payment plan
in the supported currency. When you create an
order, the configured payment plans appear only if
the total order amount is greater than or equal to
this minimum order amount. If you do not enter a
value for this field, the amount defaults to zero.
You can enter minimum order amounts only for
currencies supported on the selected plan type.
Plan Terms (Payer Options) The number of monthly installments and or
deferrals for the payment plan. The number of
applicable installments and deferrals vary from
plan to plan.
Configure an installment
This topic describes the steps to configure an installment.
Procedure
1. Review and select an installment term from the pre-defined set of default installment terms
listed under No of Installments, paid monthly.
2. Add a new installment term.
a. Enter the number of installments for the term in the installments text box.
The term is less than 99 months.
b. Select Add Installment.
The new installment term displays in the No of Installments, paid monthly list box.
3. Select Remove to delete any installment term. Use the <Ctrl> key to select multiple
installment terms.
Configure a deferral
This topic describes the steps to configure a deferral.
Procedure
1. Review and select a deferral term from the pre-defined set of default deferral terms listed
under Deferral Months.
2. If you wish to add a new deferral term, type the number of deferral months (less than 99
months) in the text box for deferral months and select Add Deferral.
The new deferral term displays in the Deferral Months list box.
3. Select Remove to delete any deferral terms. Use the <Ctrl> key to select multiple deferral
terms.
After configuring the payment plan terms, click Add to add the payment plan to the
Payment Plans list. Select Cancel to reset the Add Payment Plan section.
Field Description
Plan ID The system-generated unique identifier for the
payment plan. The Plan ID is unique across all
payment plan types configured for the merchant.
Payment Plan A concatenation of Payment Plan Name and
Payment Plan Type (<Plan Name> - <Plan Type> as
you enter in the Add Payment Plan section. For
example, Banamex - Pay without Interest.
# Of Installments A list of installment terms for the payment plan,
specifying the number of monthly installments
payable by the payer.
# Of Deferrals A list of deferral terms for the payment plan,
specifying the number of months for which the
payment can defer. The field displays the deferrals
that are not applicable to the plan type.
Start Date The start date for the payment plan, which must
less than or equal to the current date for the
payment plan to be valid. If a value is not specified,
the start date is valid now.
End Date The end date for the payment plan, which must be
greater than or equal to the current date for the
payment plan to be valid. If a value is not specified,
the end date is valid now and always.
Field Description
Minimum Amounts The minimum order amount for the payment plan
in the supported currencies. If a value is not
specified, the amount defaults to zero and hence
the validation is bypassed.
NOTE: Currently, only Mexican Peso currency is supported on Banamex Payment Plans.
• The card type for the order is not supported by your MSO.
Procedure
1. The page displays the card types and currencies configured for the acquirer link. Select
Show next to the acquirer link against which you wish to configure payment plans.
2. The name of the acquirer link displayed in the Add Payment Plan section label indicates the
acquirer link selected for the configuration.
For more information on configuring and managing a payment plan, see Add a payment plan
and Using a Payment Plan sections.
• You must have either of the following 3DS1 or 3DS2 privileges enabled.
– 3DS2 privileges - Mastercard SecureCode™ 2.0, Verified by Visa™2.0, American Express
SafeKey™2.0, JCB J/Secure™2.0, Discover ProtectBuy™2.0, Carte Bancaire™2.0, and ITMX
LSS EMV 3DS.
– 3DS1 privileges - Mastercard SecureCode™, Verified by Visa™, American Express
SafeKey™, JCB J/Secure™, Discover ProtectBuy™, and ITMX.
• The file is uploaded in the repository.
• Ensure that your MSO is enabled to download the SDK and integration guide files.
Procedure
1. Go to Admin from the main menu, and then select Software Download.
The Admin - Software and Documentation Downloads screen is displayed.
This section contains the following files for a specific merchant.
– Merchant Administration User Guide
– Mobile SDKs and Mobile SDK Integration Guide
NOTE: The Mobile SDK section displays only if it has at least one file entry and an MSO user has
the 3DS privilege.
2. Select the appropriate link and follow the prompts to download the required file.
NOTE: To modify integration settings, the operator must have 'May Configure Integration Settings'
privilege.
Integration Authentication
Configure a password or set up SSL certificates to authenticate yourself on the payment
gateway.
This helps to establish a secure channel between your integration and the payment gateway.
Procedure
1. Go to Admin, and then select Integration Settings.
The Admin - Integration Settings page is displayed.
2. View the admin integration set up for the authentication modes. Your merchant profile
enables these authentication modes. The MSO configures which authentication mode is
selected on the merchant profile, either password or SSL. The Integration Settings page
displays the authentication modes that were enabled on your merchant profile.
NOTE: The password cannot be shared between test and production merchant profiles.
Procedure
1. Go to Admin, and then select Integration Settings.
The Admin - Integration Settings page is displayed.
2. Select Edit.
The Admin - Integration Authentication Passwords page is displayed.
3. Select Generate New to generate a new password.
The system-generated password is a 16 byte randomly generated encoded value as a hex
string. Secure this password as user passwords and other sensitive data.
4. You can generate and enable a second password if you require a new password.
5. After generation, select Enable Integration access via password check box to use the
generated password to secure your transactions. Generate and enable at least one
password but you may have two passwords configured.
NOTE: Use only one password for configuration in your merchant application. The second
password is for rolling purpose. Use the second password when the first one expires.
6. Select Submit to save the settings.
Procedure
1. Go to Admin > Integration Settings > Hosted Checkout.
2. Select the payer authentication from the Payer Authentication drop-down list. Select a
value from:
– Authentication API: Hosted Checkout uses the Authentication API functionality to
perform payer authentication. If your merchant profile configures for EMV 3DS for the
respective scheme, Hosted Checkout attempts to authenticate the payer using EMV
3DS.
3. Select Submit to save the settings.
NOTE: Before you configure the payer authentication, click the available link to learn more.
Wallet configuration
Depending on your privileges, configure your wallet account on the wallet provider using the
wallet configuration screen.
The configuration supports the following wallet providers:
• Visa Checkout
• Amex Express Checkout
• MasterPass
NOTE: Hover the mouse over a field or section to view the tool-tip help and section help respectively.
Email notifications
This feature allows you to configure merchant and customer email notifications for events, such
as successful payments, successful refunds, and so on.
You can also set up merchant API notifications addressed to your system. The system sends
those notifications after creating a transaction and updating the transaction in the gateway.
The payment events are not applicable to customer emails. Types of payment events are:
• Successful payments notification is best suited if you are a low-volume merchant wishing to
receive an email when you have made a sale.
• Successful refunds: Once the system successfully processes a refund transaction, a
notification is sent for both Refund and Standalone Refund transactions.
• Payments requiring risk review: The risk service has identified a payment as potentially
fraudulent. You receive a notification to review the payment and decide whether to proceed
with processing the payment or not.
• Supported payment events: Successful payments notification is best suited if you are a low-
volume merchant wishing to receive an email when you have made a sale. This event is
generated for the transactions such as, Authorizations, Purchase, and Standalone Captures.
NOTE: Select May Configure Notifications privilege in your operator's profile to configure
notifications.
If there is a transaction subject to risk, the gateway completes the risk assessment and
transaction releases for payment processing. Further, the system sends a payment notification.
Procedure
1. Go to Admin > Device Payments.
2. Select Add New Certificate and follow the steps to procure a signed certificate from Apple
and to upload it to the gateway.
3. View the successfully uploaded certificates at the bottom of the page with the certificate
identifier, Submitted Date, and expiration date.
You can also delete an uploaded certificate.
Procedure
1. Go to Admin > Surcharge Rules
2. Select the Learn More… link for information on configuring surcharge rules.
3. Provide a pre-calculated surcharge amount for a transaction if required, when you create an
order using the Order Entry UI.
NOTE: Support for the surcharge on only card payment is available. Surcharge on payments using
digital wallets for example, Masterpass or browser payments for example, PayPal is not
applicable.
Configure PayPal
The payment service provider configures the PayPal acquirer link on the merchant profile.
Procedure
1. Go to Admin > PayPal Configuration.
2. Select Grant Permissions in PayPal link to redirect to the PayPal site to grant the required
permission.
For more information about how to configure your PayPal business account to use the
gateway, see API Online Integration Guidelines.
Merchant hosts
This section allows you to configure a list of allowed merchant hosts such as, domains or IP
addresses that you can use in Webhook notifications.
The gateway compares the entry in your list of allowed hosts with the Gateways blocked hosts
and provides the status. Only VALID hosts can be used for Webhook notifications. The MSO can
view the list of allowed and blocked hosts.
NOTE: You must have the Modify Merchant Configuration operator privilege to configure the allowed
merchant hosts.
Procedure
1. Enter the hosts that you wish to configure in the Hosts text box.
Enter a comma-separated list of one or more domains, and IP addresses. For example,
test.com, *.test.com, https://test.com. Do not use domains formatted as WWW.*.test.com.
2. View the result of allowed and blocked hosts in the Status column.
NOTE: The framework supports Mastercard, Visa, and American Express card schemes.
Click to Pay
NOTE: Administration privileges are also required to enable SRC after the onboarding process has
successfully completed. If you do not have the correct operator privileges the SRC configuration
screens will not be visible. Contact your payment service provider if you do not have the required
privileges.
Procedure
1. Go to Admin > SRC Configuration.
2. Scroll down to the Account Details section, enter the required information for all mandatory
fields.
3. Select the desired schemes to enroll in Click to Pay.
4. Click Enroll to initiate the enrollment process.
NOTE: Schemes that have been selected to be enrolled will automatically be activated and
Enrollment account details can't be modified.
Procedure
1. Go to Admin > SRC Configuration.
2. Click Enroll Another Card Brand for desired scheme.
Order details..........................................................................................................................................................47
Transaction details................................................................................................................................................47
Create an order.....................................................................................................................................................48
Order creation policy.......................................................................................................................................48
Types of an order.............................................................................................................................................48
Authorization transaction..............................................................................................................................48
Set an order certainty level...................................................................................................................... 49
Values of the order certainty field.....................................................................................................49
Order rejection rules.............................................................................................................................50
Authorization expiry.................................................................................................................................. 50
Automatic authorization reversals policy.........................................................................................50
Authorization update................................................................................................................................50
Authorization update policy................................................................................................................51
Partial Captures.........................................................................................................................................51
Capture a partial capture................................................................................................................... 51
Order totals.................................................................................................................................................52
Bypass the authorization update for an excessive capture.......................................................... 52
Order subtotals..................................................................................................................................................... 52
Update the surcharge amount........................................................................................................................... 52
Purchase transaction........................................................................................................................................... 53
Capture only...........................................................................................................................................................53
Refund only.............................................................................................................................................................53
Verify only...............................................................................................................................................................54
Create an order Using a Token............................................................................................................................54
Search an order or transaction...........................................................................................................................54
Using the Search for Orders and Transactions.......................................................................................... 55
Using the Search Fields.................................................................................................................................. 56
Export a search result.......................................................................................................................................... 60
View an order or transaction.............................................................................................................................. 62
Order and Transaction Details...................................................................................................................... 63
Action menu fields...........................................................................................................................................63
Add card numbers from the suspect or trusted Cards list............................................................................ 64
Remove the suspect and trusted cards.............................................................................................................65
Merchants can search for any transaction data through the Omnibox window by typing in the
relevant information, which could be the customer’s name, partial card number, payment reference
number, or even the purchase amount.
Order details
In its most simple form of an order, the payer provides their card details to you, through mail
order or telephone including Interactive Voice Response (IVR) systems to make immediate or
later payment for goods or services.
An order may also include a range of other actions, depending on your privileges and the
acquirer you have permission to use. For example, payment arrangements.
A successfully created order becomes available for further processing. For example, a refund or
a void. You can retrieve an existing order using order or transaction search.
Transaction details
Transactions represent the flow of information between the payer, you, and the acquirer when
purchasing goods and services.
They include transactions for purchasing goods immediately, authorizing and billing goods on
order, and performing refunds when necessary. An order can contain one or more transactions.
Create an order
Follow this step to create an order.
Procedure
Select Orders on the menu bar to view the types of orders you have the permission to create.
Types of an order
This section describes different types of an order.
The following types of orders are available to choose from when creating an order:
• Create Order (Authorization or purchase)
• Capture Only
• Refund Only
• Verify Only
NOTE: If the operator has privileges to perform both authorizations and purchases, they can select a
transaction type. Otherwise, the Transaction Type pane does not display.
Authorization transaction
The Authorization transaction verifies payer card details of a merchant, checks that your payer
has sufficient funds available against their line of credit, and attempts to reserve the requested
funds.
The authorized amount reduces the credit limit of a payer. According to the card scheme and
the card issuing rules of a payer, the authorization reserves the funds for a period of 5 to 8 days.
The authorization does not debit funds from a payer account of a merchant but reserves:
• The total order amount.
• Ready for the Capture operation to debit the card.
• Transfer the funds to your account.
Procedure
1. Go to Order > Create Order.
2. Set an order for the Order Certainty field.
Figure 5: Create Order page
For more information about the values of the order certainty field, see Values of the order
certainty field.
Values of the order certainty field
The merchant can set an order certainty field value from the following values.
FINAL The full authorized amount is expected to be captured with one or more captures
within the mandated time, which is typically 7 days. The order will only be
Authorization expiry
Authorizations have a validity period after which they expire.
The MSO configures the authorization validity period in the gateway for an acquirer, card type,
and order certainty combination. The gateway measures the authorization validity period in
milliseconds.
When a merchant submits an order, the gateway determines the authorization expiration date
and time based on the configured authorization validity period using the card type, acquirer, and
order certainty combination.
The transaction response returns the authorization expiry. This field contains the date and time
when the authorization expires.
Once the authorization validity period expires, the gateway:
• Rejects any Capture requests against the order.
• Automatically attempts to void the authorization and release funds back to the payer.
The gateway attempts to void or reverse the outstanding authorization amount if:
• The order has already been partially captured.
• The acquirer of a merchant supports voiding authorizations for partial captures.
Automatic authorization reversals policy
The MSO must enable the Automatically Reverse Expired Authorizations privilege for a
merchant profile to allow automatic authorization reversals.
Authorization update
The gateway can update the authorization validity periods, the authorization amount, or both
for valid authorizations if the merchant's acquirer supports authorization update.
The following are the scenarios to update authorization:
• If you update the authorization for the same amount as that of the original order, the
gateway extends the authorization period of the existing authorization accordingly. The
gateway returns the updated authorization expiration date and time in the transaction
response.
• If the provided amount is greater than the amount of the existing authorization, the
gateway updates the authorization amount to the new amount. For example, if the existing
authorization amount is USD 100, and you provide USD 120 as the order amount in the
Update Authorization request, then the new authorization amount available for capture is
USD 120.
• If you update an amount less than the amount of the existing authorization, it is only
supported through a Web Services API Update Authorization request.
For more information about the prerequisites for update authorization, see Authorization
update policy.
Authorization update policy
This section describes the authorization update policy.
The gateway can update an existing authorization through the Merchant Administration only if:
• The MSO must have the Update Authorization privilege enabled on their merchant profile to
update authorizations.
• The MSO set the order certainty on the order to ESTIMATED.
• The order amount is less than the amount of the existing authorization.
• The order currency matches the currency on the existing authorization.
• The existing authorization is valid, successful, and fully approved.
• The existing authorization is expired, voided, or partially or fully captured.
Partial Captures
When a merchant captures an order, the merchant can provide a Capture amount lower than
the Authorized amount for the order.
If a merchant does not capture all the authorized amount, the gateway can reverse the
remaining authorized amount that is outstanding beyond the current capture.
NOTE: The acquirer who processed the transaction must have the capacity to reverse authorization
amounts for partially captured authorizations.
NOTE: You must have the Automatically Reverse Outstanding Authorization Amounts privilege
enabled on your merchant profile.
Procedure
1. Select Yes to avoid capturing the remaining authorized amount.
The gateway indicates that this is the last capture for an order and reverses any
outstanding Authorization amount.
2. Select No if there are additional amounts that you want to capture for this order.
The gateway does not reverse any outstanding Authorization amount.
Order totals
After a successful Update Authorization transaction for a card or PayPal, the gateway updates
the order amount and the total authorized amount to the transaction amount of the Update
Authorization transaction.
This applies regardless of whether the acquirer submitted the Update Authorization transaction
to the acquirer, or the gateway automatically approved the Transaction Gateway Response
Code=APPROVED_AUTO.
Bypass the authorization update for an excessive capture
Follow this step to bypass the authorization update for an excessive capture.
Procedure
Select Do not Update Authorization in the Capture dialog box.
The gateway submits an excessive capture to the acquirer and does not update the order totals.
Order subtotals
The merchant can update the following subtotal amounts in an Update Authorization
transaction.
• Item Amount
• Tax Amount
• Shipping and Handling Amount
• Discount Amount (card payments only)
NOTE: The gateway does not validate if the subtotal amounts add up to the transaction amount, that
is, the order amount. However, the MSO must ensure this for the PayPal payments.
Procedure
1. If an MSO has enabled Surcharging, a merchant can update the surcharge amount for an
existing authorization in an Update Authorization transaction.
2. If the merchant has not enabled Surcharging, a Surcharge Amount field displays as a
subtotal amount field alongside other subtotal amounts, that is, item amount, tax amount,
and so on.
a. Enter the revised surcharge amount or the new surcharge amount in the Surcharge
Amount field.
NOTE: For PayPal payments, providing a Surcharge Amount is not supported and Update
Authorization transactions with a value for this field will be rejected.
Purchase transaction
The purchase transaction effectively combines an Authorize and Capture information into one
message.
A single transaction authorizes the payment and transfers funds from the payer's account into
your account.
Capture only
Capture Only captures funds for an order that the merchant has authorized either manually or
through an external system.
The merchant must provide the manually or externally produced Authorization ID to perform the
capture.
Refund only
Refund Only allows the merchant to refund funds from your account back to the payer, without
a previous purchase.
The merchants might perform a Refund only when they want to credit the payer's account
without associating the credit with a previous transaction or receipt.
Verify only
Verify Only allows the merchant to verify the status of a credit card before performing the
transaction.
Depending on the acquirer, address details or the payer's name may be matched to ensure the
card details are valid.
NOTE: The gateway does not support order creation for ACH and Gift Cards.
NOTE: The links provided in this guide are for a test environment. To access a production environment,
you must follow the appropriate steps. The Merchant Admin Portal may be accessed as an
administrator or user.
Procedure
1. Go to Search > Order and Transaction.
The Order and Transaction Search page is displayed.
NOTE: The entered or selected dates and times in the order and transaction search are based on
the time zone as determined by your browser.
4. Enter the order or transaction details to refine the search results, and then select Search.
NOTE: When using the searching functionality, you can enter a unique value or custom field. This
means that the search can be used equivalent to a "google search" and you can type in any search
criteria that you prefer, and the result will be returned based on that. The search field can, for
example, return results on most of the API response fields from the API guide. The search will
return the exact as well as close matches, ignoring the case, spelling, and accented characters.
NOTE: The Search Functionality does not support WildCard (*, ?) Searches. Refer to the following
guidelines for more detailed ways to use the search fields and examples thereof.
Using an identifier (Order ID, Merchant Order Reference, Transaction ID, Acquirer
ID, and so on)
• Enter the identifier in the search box.
• Additionally, provide only the first part or the last part of the identifier. The search returns
identifiers that start or end with the search term.
Examples may include - ORDER1 or R1234 returns all records where the fields start or end
with this value, including records with Order ID ORDER1234
• Enclose the identifier in quotes to only return exact matches.
Examples may include - ORDER1 or R1234 returns all records where any of the fields starts
or ends with this value, including records with Order ID ORDER1234
• To refine the search results, provide the field label and value separated by a : (colon). If the
field label or value consists of more than one word or contains a colon, enclose it in double
quotes.
Examples may include - "5123456789012346" returns all records where any of the fields has
the value 5123456789012346
Procedure
Select the Export results to CSV button to download the search results as a CSV file.
Figure 7: Export results to CSV
a. Select the time zone, CSV character encoding format, and the fields to export.
b. Select the + Add Custom Field link to add custom fields to export.
You can add any API response field, including itemized fields, to the list of available fields.
You can use any field name from the API Response displayed in the order or transaction
details screen. To add an API field, enter the name of the API field prefixed with api.
For example, api.airline.itinerary.leg[0].carrierCode .
d. Select the Save Selection link to save the selected fields for future use.
The saved selections display in the Load Saved Selection drop-down list.
Procedure
1. From the search result list, select View.
Figure 10: View order
Field Description
Authorize The merchant can perform this action to create an
Authorization or a Payment transaction.
Field Description
Capture The merchant can perform this action to request
funds from the payer's account for an authorized
transaction.
Refund The merchant can perform this action to return
funds to the payer's account. If there are multiple
captures, merchants can use the Capture
Transaction ID to refund the amount for a specific
capture.
Update Authorization The merchant can perform this action to either
increase or decrease the Authorized amount for an
order, extend the validity period for an
Authorization, or both.
Void Last Transaction The merchant can perform this action to void the
last transaction on the order, which can be
Authorization, Capture, or other.
Void Authorization The merchant can perform this action to void an
order with successful Authorization that the
gateway has partially captured.
Clone The merchant can perform this action to use
existing details of an order to create a new order.
NOTE: Select Learn about this page if you need assistance with performing actions including actions
associated with risk assessment of orders.
Procedure
Add the suspect or trusted cards from the Account Identifier drop-down list on the Order and
Transaction details page.
SAQ-A compliant merchants can add cards directly to the suspect or trusted Cards list using the
Transaction Filtering option on the main menu.
Procedure
Remove the suspect or trusted cards from the Account Identifier drop-down list on the Order
and Transaction details page.
Field Description
Risk Provider Specifies the name of the risk service provider that
risk assessed the transaction.
Rule ID Specifies the unique identifier for the risk rule
provided by the risk service provider.
Rule Type Specifies information on the entity who defined
the rule, for example, the risk service provider. Note
that this field is not available for search.
Rule Description Specifies description of the risk rule.
Field Description
Rule Outcome Specifies the risk service provider's risk assessment
score for the order based on the risk rule.
Procedure
1. Search for tokens using:
– Token ID
– Card number
– Expiration date
– Gift card number
– ACH payment details
2. If you have the aggregator privilege, use the Sub Merchant ID field to limit the result list to
tokens for a specific sub-merchant.
This finds all tokens that match the search criteria.
NOTE: Searching for tokens created using external repositories is currently not supported.
Settlement
Settlements are balance operations between the merchant's account and an acquirer's record.
Orders are unsettled transactions that a user can settle based on their privilege.
Based on their merchant profile settings, users can perform settlement in one of the two ways where
one is manual and other is automatic that requires no user intervention:
Settlement This section displays orders in the current settlement that are to be settled.
Settlement History This section allows a user to search and view orders that are already
Selections settled.
NOTE: The links provided in this guide are for a test environment. To access a production environment,
you must follow the appropriate steps. The Merchant Admin Portal may be accessed as an
administrator or user.
Procedure
1. Select Settlement > Pre-settlement Summary.
If you have multiple acquirer links, the Settlement Acquirer Link Selection page is displayed.
The card types and currencies configured for the acquirer link is also displayed.
2. Select the required Acquirer ID from the available options and then select Submit.
The Unsettled Transactions Summary page is displayed.
3. The Settlement page shows the current orders awaiting settlement. It details a settlement
by currency. Each row for a currency provides details for transactions processed by a specific
card type.
4. Select Settle Now to settle a batch of unsettled transactions.
This option is available only if you have the Initiate Manual Batch Closure privilege.
The Batch Closure Receipt page is displayed.
Field Description
Number of Batches Currently Open The number of the batches that are currently open.
Transactions by currency
The transactions are grouped into sections by the transaction currency.
This table describes the fields of Transactions by summary page.
Field Description
Card Types The type of cards in transactions. For example,
Mastercard, Visa, Discover, and so on.
Debits Count The number of debits in the settlement batch.
Total Debits or Debits Amount The total amount of debit in the settlement batch.
Credit Count The number of credits in the settlement batch.
Total Credits The total credit amount in the settlement batch.
Field Description
No. of Batch being Closed The number of the batches closed in a transaction.
Procedure
1. Go to Settlement > Settlement Search.
The Settlement Search screen is displayed.
2. In Search for Settlements section:
a. Enter the Merchant ID.
b. Enter the date range of orders in From Date and To Date fields. The required format
should be, for example, 11/15/05 3:45 PM or 1/15/05.
If the From Date field is empty, the Merchant Manager portal displays all transactions
up to the current date. The date and time values are based on the operator's time zone
as configured on the Merchant Manager portal.
c. Enter the Batch Number.
The batch value of Mastercard cannot be used for communications with the processor
or the processor's back-end processing network.
d. Select the status of the required settlement in the Settlement Status drop-down list.
Default value is All Settlement Responses.
e. Select the acquirer, to which the settlement is sent, in the Acquirer ID drop-down list.
Default value is All.
3. Select Submit.
The Settlement List screen displays details of the settlements based on the search
parameters.
4. Select the Batch Number link corresponding to a settlement to view its details.
The Settlement Details page displays merchant and acquirer settlement details and its
comparison.
Settlement List
The Settlement List page displays information about settled batches.
This table describes the fields available in the Settlement List page.
Field Description
Acquirer ID The identification value of the card-processor.
Batch Number The identification value of the settled batch.
Settlement Date The date and time when the batch is settled.
Debits Count The number of debits in the settled batch.
Credits Count The number of credits in the settled batch.
Settlement Details
The Settlement Details page consists of two sections:
• Merchant and Acquirer Settlement Details
• Merchant and Acquirer Settlement Details Comparison
The transactions in the Merchant and Acquirer Settlement Details Comparison section are
grouped by currencies.
Field Description
Merchant ID The identification value of the merchant.
Acquirer ID The unique identifier of the card-processor to
which the order is directed for processing.
Settlement Batch number The identifier for the batch to which the
transactions belong.
Submission Date The date on which the settlement occurred.
Settlement Response The response received back from the acquirer.
Payment Method The method of funds transfer used for the
transaction. For example, Credit.
Field Description
Currency The currency used for the transaction.
Debits Count The number of debits in the settlement batch.
Total Debits or Debits Amount The total debit amount in the settlement batch.
Number Credits The number of credits in the settlement batch.
Total Credits The total credit amount in the settlement batch.
3DS is an authentication protocol that is designed to reduce fraud and provide more security for the
e-commerce transactions. 3DS enables the merchant to authenticate the payer at their card issuer
before submitting the Authorization or Purchase transaction.
3DS benefits
3DS offers the following benefits to the merchant:
• Protection against fraud as the payer is authenticated at their card issuer.
• Shift of liability. Payments where 3DS is performed shifts the liability to the issuer. If a payer
disputes the payment and claims a chargeback, the liability for fraudulent chargebacks shifts
from the merchant to the issuer.
• Enhanced security on payments as the Access Control Server (ACS) of an issuer assesses a
payer for risk.
EMV 3DS
EMVCo has designed EMV 3DS, which is a new authentication version, and most of the card
schemes have adopted this version.
This version provides enhanced security during online purchases.
It provides a frictionless checkout experience for payers wherever applicable. For example, an
issuer might bypass the authentication challenge if the payment is at low risk.
The following items are the supported authentication schemes for EMV 3DS:
• Mastercard SecureCode™2.0
• Verified by Visa™2.0
• American Express SafeKey™2.0
• JCB J/Secure™2.0
• Discover ProtectBuy™2.0
Access Control Server (ACS) uses the information from various sources to determine the risk.
ACS can obtain information from a merchant, browser fingerprinting, and previous interactions
with a payer. ACS subjects a payer to a challenge only when the additional verification is
mandatory to authenticate a payer. This authentication version is also known as 3DS2 in the
gateway.
For more information about how to add 3DS authentication to your gateway integration, see
EMV 3-D Secure Authentication in the API online Integration Guidelines.
NOTE: If a payer does not authenticate successfully or does not enroll in EMV 3DS, then the gateway
will determine the next steps based on the authentication details from the issuer and the 3-D Secure
Risk Rules. For more information, see 3D-Secure Rules.
NOTE: The links provided in this guide are for a test environment. To access a production environment,
you must follow the appropriate steps. The Merchant Admin Portal may be accessed as user or
administrator.
Procedure
1. Go to Search > Orders and Transactions.
2. Select Orders as the search criteria from the drop-down list.
3. Select value from the Order Status drop-down list.
You can select multiple values from the drop-down list.
4. Select Search.
Procedure
1. Go to Search > Orders and Transactions.
2. Select Transactions as the search criteria from the drop-down list.
3. Enter value in the Transaction Type drop-down list.
4. Select Search.
For more information about the Order and Transaction search page, see More tips.
Merchants can save their preferred search through the Save search link.
Authentication Use the Payer Authentication Status field to search based on the
Status authentication status.
• "Payer Authentication Status":"Authentication Successful"
• "Payer Authentication Status":"Authentication Available"
Authentication Type Use the field “Payer Authentication Type” to search based on the
authentication version – EMV 3DS.
• "Payer Authentication Type":"EMV 3DS"
Authentication If the merchant uses payer authentication across multiple channels, for
Channel example, website and mobile app, then you can use the following API fields to
refine the results.
For order search:
• @api.transaction.authentication.channel:"PAYER_BROWSER"
• @api.transaction.authentication.channel:"PAYER_APP"
For transaction search:
• @api.authentication.channel:"PAYER_BROWSER"
• @api.authentication.channel:"PAYER_APP"
Procedure
1. Go to Search > Orders and Transactions.
Based on your search choices, the results display at the bottom of the screen.
2. Select the Export results to CSV button.
3. (Optional) Select values from the Time Zone and Format drop-down lists.
4. (Optional) Select fields from the Available Fields list.
5. (Optional) Select the + Add Custom Field link to add custom fields.
Figure 13: Add custom fields
Procedure
1. Go to Search > Orders and Transactions.
2. Select View on the transaction or the order record in the search results.
The result screen is displayed.
3. Select View in the Transactions section.
You can see the individual response fields associated with the authentication transaction.
Procedure
1. Go to Search > Authentications.
2. Use the fields on the Payment Authentications Search page to find the required payment
authentication details.
3. Select Submit to start the search.
The search results display on the Payment Authentication List page.
Field Description
From/To Specifies the search for orders within a date range.
If you clear the From field, all transactions up to
the current date is displayed. The From and To
dates are based on the time zone of an operator as
configured in Merchant Administration.
Authentication ID Specifies the search for an order with a particular
authentication ID.
Card Number Specifies the search for an order using a specific
card number.
Order Reference Specifies the search for an order created with
specific Order Reference text.
Currency Specifies the search for orders processed by a
particular currency or all currencies.
Field Description
Authentication Type Specifies the search for a particular type of 3DS
authentication. Select an authentication type from
the drop-down list or leave the default entry to
display all authentication types. Following are the
possible options.
• All Authenticated Transactions
• Mastercard SecureCode
• Verified By Visa
• JCB J/Secure
• American Express SafeKey
• Discover ProtectBuy
• UnionPay 3-D Secure
Number of Results to Display on Each Result Page Specifies the number of rows of search results that
you want to see on a single page.
Leave this field blank for the default number of
search results to display.
Field Description
Authentication ID Specifies as a unique identifier for the
authentication attempt. You can see the
authentication details through the ID.
Field Description
Authentication Type Specifies the type of 3DS authentication. Following
are the available authentication types.
• Verified by Visa
• Mastercard SecureCode
• JCB J/Secure
• American Express SafeKey
• Diners ProtectBuy
• UnionPay 3-D Secure
NOTE: You might not see all the fields listed here. Depending on your configuration, some fields may be
enabled or disabled.
Field Description
Authentication ID Specifies a unique identifier for the authentication
attempt.
Date Specifies the user-locale date and time at which
the order was created.
Card Number Specifies the card number used in the order
displayed in the card format configured on your
profile.
Amount Specifies the total amount of the order in the
transaction currency. For example, AUD $100.00.
Field Description
Authentication Type Specifies the type of payment authentication.
• Verified by Visa (Visa 3-D Secure)
• Mastercard SecureCode 3-D Secure
• JCB J-Secure
• American Express SafeKey
• Discover ProtectBuy
• UnionPay 3-D Secure
Field Description
3-D Secure PARes.status Indicates the result of the payer authentication.
The available values are:
• Y – Yes
• N – No
• A – Attempted authentication but failed. For
example, the payer failed to enter the correct
password in three attempts.
• U – Undetermined. The payment authentication
system was unavailable at the time of the
authentication.
For more information about how to interpret the
authentication result based on the 3-D Secure
PARes.status field, see the card scheme
documentation.
Response details
You can see or hide the response details through the Show or Hide button.
Field Description
VERes Specifies the details of the Verify Enrollment
Response (VERes), in the XML format. The details
are received in response to the Verify Enrollment
Request (VEReq) message that the Payment
Server sends to the Directory Server. If the card is
enrolled for 3-D Secure, VERes will contain the
address of an Access Control Server (ACS).
PARes Specifies the details of Payer Authentication
Response (PARes) in the XML format. The details
are received in response to the Payer
Authentication Request (PAReq) message that the
Payment Server sends to the Access Control Server
(ACS). PARes contains the verification result.
Field Description
Source Specifies the source of the fields. For example,
ACS, DS, and so on.
Message Type Specifies the type of the message, Invalid Request
Response (IREQ), or Error.
Error Message Version Specifies the version of the message as the ACS or
DS returns.
Error Code Specifies the error code that ACS or DS returns.
Error Detail Specifies the message details that ACS or DS
returns.
Vendor Code Specifies the vendor code for ACS or DS.
Error Description Specifies the description of the error that ACS or
DS returns.
Procedure
1. Go to Search > Authentications.
2. Select the file format from the drop-down list under the Download button.
3. Select the Download button.
If you select the CSV file format from the drop-down list, it contains orders with the
associated payment authentication data that matches the search criteria.
Upload a batch......................................................................................................................................................91
Batch status list....................................................................................................................................................92
Download the batch response............................................................................................................................93
In addition to allowing the upload of batches of transactions for processing to the payment gateway,
the user can also:
• View the status of the batch that you uploaded for processing.
• Download the batch response file that contains the result of each of the uploaded operations.
NOTE: You can apply surcharging to transactions uploaded through Batch. For information about
surcharging, see Configure Surcharge Rules.
Upload a batch
This section allows you to upload a batch file containing the transactions for processing.
Procedure
In the Merchant Admin Portal, go to Batches.
a. Enter the API version that matches the field names in the batch file.
For example, if version X is entered then the operations accepted are those supported in
version X of the API.
NOTE: Entering an invalid value will return an error during batch file validation. Entering an
unsupported value will return errors on all operations in the batch response file.
b. Select the character encoding of the batch file from the Batch File Encoding drop-down list.
The list contains supported encoding types. For example, UTF-8 and Latin1 (ISO-8859-1).
c. Select Browse to upload the batch file that you want to upload for processing.
The batch file name is used as the batch name. This file must comply with the Native
Format (CSV). For information on the Native Format, see the Batch online integration
documentation.
d. Select Upload to upload all the details including the batch file.
Field Description
Batch Name The name of the batch file containing operations.
Upload Completed The time and date when uploading of all records got complete.
Batch Status The current processing status of a batch. The valid values are:
Errors The total count of records that have timed out or cannot process
due to system errors.
Last Action Time and date of the last action on the batch.
Processing Completed The time and date when the batch processing was completed and
all records were in their final state.
Response File This column displays the Download link to download the batch
response file.
NOTE: The Response File column appears only if you have the
May Download Batch Response Files operator privilege.
Procedure
1. Go to the Batches section to locate the response file that you want to download.
2. Select Download to open or save the file on your local machine.
NOTE: The information provided in the batch response file is based on the fields specified in the
batch upload file. You might find it useful to include API fields such as response.gatewayCode and
error.cause to identify problems in processing operations. For more information about fields that
you can include in the response, see the Batch Online Integration Documentation.
Within the portal, you can easily generate and download customized reports by specifying required
dates, time interval, and currency.
The transaction details can be searched and listed in the gateway reports by:
• Date
• Merchant profile type, for example, test or production
• Time intervals, for example, daily, weekly, monthly, or yearly, and
• Currency, for example, AUD, USD, and so on.
NOTE: The links provided in this guide are for a test environment. To access a production environment,
you must follow the appropriate steps. The Merchant Admin Portal may be accessed as an
administrator or user.
Procedure
1. Select Reports > Gateway Reports.
2. Enter the search parameters based on which the gateway generates the report.
3. Select Submit.
Field Description
From or To Date Search for transactions within a date range. If you
clear the From Date field, all transactions up to the
to date are displayed.
Date Type Search by transaction date or settlement date.
• Transaction Date: Specifies the date and time
that the gateway considers the processing of
the transaction to have occurred. This date is
based on the operator’s time zone.
The gateway reports that you search by the
transaction date do not include transactions
that are flagged for risk review.
• Settlement Date: Specifies the expected date
of funds transfer between an issuer and an
acquirer. This date is based on the acquirer's
time zone.
Start Time for Time Interval Specifies the start time for time interval
Reports are generated for 24-hour periods from
the start time of the time interval as defined in this
field. By default, start time is 00:00.
This field is not applicable if you search by
settlement date.
NOTE: A merchant may have multiple merchant acquirer relationships with the same acquirer.
Field Description
Transaction Date The start date of the period for which transactions
are aggregated.
Acquirer The name of the acquirer who processed the
transactions.
Merchant The merchant's unique alphanumeric identifier.
There is a unique Merchant ID for each merchant
account or profile.
No. Transactions The number of transactions processed by the
acquirer, in a given currency, during the reporting
period.
Total Authorizations The total number of authorizations, exclude any
voids or refunds, in the reported transactions.
Total Captures The total number of captures, exclude any voids or
refunds, in the reported transactions.
Total purchases The total number of purchases, exclude any voids or
refunds, in the reported transactions.
Total Refunds The total number of refunds in the reported
transactions. This amount is specified using the
currency and the currency symbol of refunds.
Total Disbursements The total number of disbursements in the reported
transactions. This amount is specified using the
currency and the currency symbol of
disbursements.
NOTE: The Total Disbursements field is displayed irrespective of the gamingWinningsPayment or the
creditCardBillPayment privileges enabled for you.
A set of customized rules can be configured to enable the gateway to identify high or low risk
transactions. That include:
• IP address range rules
• IP country rules
• card BIN rules
• 3D Secure rules
• and CSC rules
The MSOs and merchants can configure the rules. The rules are evaluated based on the principle of
gates or hurdles. Even if a single rule fails, the gateway rejects the transaction and does not allow the
order to proceed.
The Order response and order details screen display the assessment result. You can also search for
orders based on the assessment results, transaction filtering, or the risk service provider.
The gateway only assesses the Authorization, Pay, Verification Only, and Standalone Capture
transactions against the transaction filtering rules. It does not perform assessment on other
transactions such as Standalone Refunds or Voids.
The gateway offers advanced fraud management of transactions through the Risk Management
feature. For more information, see Managing Risk.
• May Perform Risk Assessment Review enables the merchant operator to review orders
marked for review. See Risk Assessments for Review.
• May Bypass Risk Management enables the merchant operator to process the transaction by
bypassing transaction filtering rules that the merchant configures.
For more information about these privileges, see Merchant Operator General Privileges.
Pre-transaction checks
Pre-transaction checks refer to assessment before performing the transaction.
No transaction response data from the acquirer AVS and CSC result is available for assessment.
If the assessment result is Reject, voids or reversals are not applicable as the transaction is yet
to perform.
The following table describes the pre-transaction checks.
Step Description
3DS check If a 3DS authentication scheme is enabled and
configured, 3DS authentication is performed. If
payer authentication fails, the gateway
automatically rejects the transaction.
MSO pre-transaction check Transaction filtering rules that the MSO configures,
runs before performing the transaction.
Post-transaction checks
Post-transaction checks refer to assessment after performing the transaction. The transaction
response data from the acquirer AVS and CSC result is available for assessment.
If the recommendation is Reject, and if the transaction assessed is Verification Only, then there
is no requirement of voids or reversals as the acquirer submits the financial transaction.
However, when the system rejects the Authorization, Purchase, or Standalone Capture
transaction after assessment, it system automatically voids or reverses the transaction.
Step Description
Process transaction Gateway processes the transaction.
MSO post-transaction check Transaction filtering rules that the MSO configures,
runs after performing the transaction.
Merchant post-transaction check Transaction filtering rules that a merchant
configures, runs after performing the transaction.
Assessment result
MSO rules
A set of rules configured by the MSO for filtering transactions. MSO can configure the rules that
apply to all merchants or configure rules per merchant.
Merchant rules
A set of rules configured by the merchant for filtering transactions.
Trusted cards
An accepted list of trusted credit card numbers owned by those cardholders whom the
merchant considers trustworthy to transact with.
System reject
An MSO action to reject the transaction because the rules configured by the MSO evaluated to
Reject.
No action
An action available when defining rules that instructs the gateway to process the transaction.
Accept
An action available when defining rules that instructs the gateway to accept the transaction.
Reject
An action available when defining rules that instructs the gateway to reject the transaction.
Review
An action available when defining rules that instructs the gateway to mark the transaction for
review so that the merchant can manually review the transaction either to accept or reject.
Not assessed
The MSO-configured risk rules did not assess the order for risk except for risk assessment and
these rules did not reject the order.
To configure the transaction filtering rules, you must have May Configure Transaction Filtering
operator privilege.
You can configure the rules to filter transactions based on the following:
• Assessing the results returned by industry standard card verification processes
– 3D-Secure authentication rules
– CSC (Card Security Code) rules
– IP Address Range rules
– IP Country rules
– Card BIN rules
Select Transaction Filtering on the main menu and then select the rule you wish to configure.
As a merchant, you can set the action to No Action (accept), Reject, or Review.
NOTE: The links provided in this guide are for a test environment. To access a production environment,
you must follow the appropriate steps. The Merchant Admin Portal may be accessed as an
administrator or user.
NOTE:
Only transaction filtering rules configured for IP Address Range and IP Country applies to browser
payments.
Trusted Cards
Trusted cards list is a set of credit card numbers owned by cardholders.
Transactions originating from such cards are considered trustworthy. Typically, a cardholder with
a good record of transaction history has a high potential to add to the trusted card list.
Configure trusted card rules ensures that transactions from trusted cards are always accepted.
Procedure
1. Select Transaction Filtering > Trusted Cards from the submenu.
The Transaction Filtering - Trusted Cards configuration page is displayed.
2. In the Add New Card Number pane, enter the following details:
a. In the Card Number box, enter the card number of the cardholder.
b. In the Card Holder Name box, enter the name of the cardholder.
The name cannot exceed 40 characters.
c. In the Reason box, enter the reason to add the card as trusted card.
The reason cannot exceed 40 characters.
3. Select Add.
The Trusted Cards page redisplays with the new entry appearing in the Current Trusted
Cards Numbers list. The card number displays in the 6.4 card masking format irrespective of
the masking format configured on your merchant profile.
Procedure
1. Select Transaction Filtering > Trusted Cards from the submenu.
The Transaction Filtering - Trusted Cards configuration page is displayed.
2. In the Current Trusted Card Numbers pane, filter the list based on a card number.
a. In the Filter By Card Number box, enter the card number.
Select Clear if you want to clear the filter string. Clearing the filter repopulates the
entire list of card numbers and turns off the filter mode.
– Filter mode Off: This indicates that the filter option is disabled on the Trusted Cards
list.
– Filter mode On: This indicates that the filter option is enabled on the Trusted Cards
list.
b. Select Go.
Only card numbers that match the filter criteria displays in the Current Trusted Card
Numbers list. The card numbers appear in ascending order.
Procedure
1. Select Transaction Filtering > Trusted Cards from the submenu.
The Transacting Filtering - Trusted Cards configuration page is displayed.
2. In the Current Trusted Card Numbers pane, filter the trusted cards list based on a card
number.
3. Select one or more card numbers that you want to delete using the check boxes in the
Select column.
You may use Select All or None to select or clear all card numbers.
4. Select Remove Trusted Card Numbers to delete the selected card numbers.
Suspect Cards
Suspect cards list is a set of credit card numbers owned by cardholders. Transactions originating
from such card numbers are considered untrustworthy. Typically, a cardholder with a fraudulent
transaction history has a high potential to add to the suspect card list. Configure suspect card
rules to ensure transactions from suspect cards are always rejected.
Procedure
1. Select Transaction Filtering > Suspect Cards from the submenu.
The Transaction Filtering - Suspect Cards configuration page is displayed.
2. In the Add New Card Number pane, enter the following details.
a. In the Card Number box, enter the credit card number of the cardholder.
b. In the Card Holder Name box, enter the name of the cardholder.
The name cannot exceed the 40 characters.
c. In the Reason box, enter the reason to add the card as a suspect card.
The reason cannot exceed the 40 characters.
3. Select Add.
The Suspect Cards page redisplays with the new entry appearing in the Current Suspect
Cards Numbers list. The card number displays in the 6.4 card masking format (irrespective
of the masking format configured on your merchant profile).
Figure 17: Suspect Cards page
Procedure
1. Select Transaction Filtering > Suspect Cards from the submenu.
The Transaction Filtering - Suspect Cards configuration page is displayed.
2. In the Current Suspect Card Numbers pane, filter the list based on a card number.
a. In the Filter by Card Number box, enter the card number.
Click Clear if you want to clear the filter string. Clearing the filter repopulates the entire
list of card numbers and turns off the filter mode.
– Filter mode Off: This indicates that the filter option is disabled on the Suspect Cards
list.
– Filter mode On: This indicates that the filter option is enabled on the Suspect Cards
list.
b. Click Go.
Only card numbers that match the filter criteria displays in the Current Suspect Card
Numbers list. The card numbers display in the ascending order.
Figure 18: Current Suspect Card Numbers list
Procedure
1. Select Transaction Filtering > Suspect Cards from the submenu.
NOTE: A browser rejects the payment if originating from an IP address of a range, which has an action
of Review.
Procedure
1. Select Transaction Filtering > IP Address Range Rules from the submenu.
The Transaction Filtering - IP Address Range Rules configuration page is displayed.
2. In the Add IP Address Range pane, enter the following details.
The IP address specified in IPv4 format must be between the range 0.0.0.0 and
255.255.255.255.
a. In the IP Address Range Start box, enter the first IP address range to block review.
b. In the IP Address Range End box, enter the last IP address in the range to block or
review.
You can block or review a single IP address or an IP address range. For example, if you
want to block IP Address 192.0.2.255, then enter 192.0.2.255 as the IP Address Range
Start entry. To block an IP address range, for example, 192.0.2.222 to 192.0.2.255, then
enter 192.0.2.222 and 192.0.2.255 as the start and end IP address ranges respectively.
If the specified IP addresses form a large range, the system displays a warning 'The rule
you want to configure will apply to a very large number of IP addresses. Are you sure
you want to add this rule?.'
c. Select OK if you want to continue else select Cancel.
3. Select Add.
The IP Address Range Rules page redisplays with the added entry appearing in the
Currently Blocked IP Address Ranges list. You can filter the following list based on an IP
address:
1. In the Filter Ranges by IP Address box, enter the IP address. Select Clear if you want to
clear the filter string. Clearing the filter repopulates the entire list of IP address ranges
and turns off the filter mode.
You can also use the filter option to check if an IP range is currently blocked.
2. Select Go. Only IP ranges that match the filter criteria are displays in the Currently
Blocked IP Address Ranges list. The IP ranges are sorted in ascending order.
If the list of IP address range rules exceeds 20 entries, pagination triggers which allows
you to navigate between multiple pages.
Figure 19: IP Address Range Rules page
Procedure
In the Currently Blocked IP Address Ranges pane, enter the following details.
a. Filter the IP address range rules list based on an IP address. See Step 3 in Add an IP Address
Range Rule.
b. Select one or more IP address range rules that you want to delete in the Select column. You
can Select All or None to select or clear all IP address ranges.
c. Select Delete to delete the selected IP address range rules.
A warning message displays, which alerts you about deleting IP ranges that may occur in
multiple IP ranges if overlapping IP ranges have been defined.
d. Select OK if you want to proceed with the deletion of the selected IP ranges.
Select Cancel to cancel the deletion.
Figure 20: Confirmation message
IP country rules
IP Country rules are configured to block or review transactions originating from a predefined list
of countries. You can configure additional rules to block countries identified as using IPs from
unknown countries or IPs of anonymous proxies that mask the true origin of the request.
NOTE: A browser payment is rejected if originating from an IP address of a country that lists in the
review.
You can configure Unknown Country and Anonymous Proxy independently even when a country
is in the reject list. Before saving your configuration, it is mandatory that you accept the
disclaimer regarding an IP Country-mapping solution, displayed at the bottom of the IP Country
Rules configuration page.
Procedure
1. Select Transaction Filtering > IP Country Rules from the submenu.
The Transaction Filtering - IP Country Rules configuration page is displayed.
2. In the Add an IP Country Rule pane, select from the following actions that you want to
perform on the unknown countries and anonymous proxies.
Unknown A country that is not listed on this page or an IP address that does not
Country resolve to a valid country.
Anonymous It refers to an IP address of a known anonymous proxy server. These are
Proxy the addresses that have been identified to mask the true origin of the
request.
No Action This is the default. An unknown country or anonymous proxy with this
status is accepted.
Review An unknown country or anonymous proxy with this status is manually
reviewed and either accepted or rejected.
Reject An unknown country or anonymous proxy with this status is rejected
automatically.
NOTE: If the gateway adds country to the Reject list due to the transaction originating from an
Unknown country or Anonymous Proxy, then the No Action radio button remains enabled. You may
choose to allow tractions by selecting it.
3. Assign a country or list of countries to one of the following actions:
No action It lists countries that you want to accept transactions from.
Review It lists the countries that you want to mark for review before proceeding with
the order. Marking countries for review provides merchants with the flexibility
to decide on whether to process or reject a transaction from the specified
country.
Reject It lists the countries that you want to reject transactions from.
NOTE: If a country is added to the Reject list, then the gateway automatically sets the action for
these two options for an unknown country and an anonymous proxy to Reject. If the countries are
only listed for Review, the action for these two options is automatically set to Review. However
you may choose to set it to Reject.
4. Mark a country for review:
a. From the No Action or the Reject list box, select the country.
b. Select Review at the bottom of the box to move the country to the Review list box.
If you want to undo your action, select the country in the Review list box, and then select
No Action or Review at the bottom of the box.
5. To reject a country:
a. Select the country from the No Action or the Review list box.
b. Select Reject at the bottom of the box to move the country to the Reject list box.
If you want to undo your action, select the country in the Reject list box, and then select
No Action or Review at the bottom of the box.
6. Select Save to save the IP country rule.
7. Select Cancel if you want to exit the IP country rules configuration page without saving any
changes.
Procedure
1. From the Review and Reject list boxes, select the countries.
2. Select the No Action at the bottom of the box and save changes.
Procedure
1. Select Transaction Filtering > Card BIN Rules from the submenu.
The Transaction Filtering - Card BIN Rules configuration page is displayed.
2. Select Add a BIN Range. The Add a BIN Range window opens.
NOTE: Changing your configuration option when you already have an option configured, will clear
your currently configured BIN ranges.
Procedure
In the Currently Blocked BIN Ranges pane, enter the following details.
a. Select one or more BIN rules that you want to delete using the check boxes in the Select
column.
You may use Select All or None to select or clear all BIN rules.
b. Select Delete.
A warning message displays, which alerts you about deleting BIN ranges that may occur in
multiple BIN ranges if overlapping BIN ranges are defined. Click Yes if you want to proceed
with the deletion of the selected BIN ranges. Click No to cancel the deletion.
3D-Secure Rules
3-Domain Secure™ (3-D Secure or 3DS) authentication is designed to protect online purchases
against credit card fraud by allowing the merchant to authenticate the payer before submitting
an Authorize or Purchase transaction.
NOTE: The 3-D Secure Transaction Filtering rules do not apply to scheme token transactions.
EMV 3DS
EMV 3DS, is the new version designed by EMVCo and adopted by most card schemes. It is an
intelligent solution that provides enhanced security in online purchases while providing a
frictionless checkout experience to payers where applicable. For example, the issuer may bypass
the authentication challenge if the payment is considered low risk.
The ACS determines the risk using information provided by the merchant, browser
fingerprinting, and/or previous interactions with the payer. The ACS subjects the payer to a
challenge (for example, entering a PIN) only where additional verification is required to
authenticate the payer. This authentication type is also known as 3DS2 in the gateway.
Supported authentication schemes for EMV 3DS include:
• Mastercard SecureCode™2.0
• Verified by Visa™2.0
• American Express SafeKey™2.0
• JCB J/Secure™2.0
• Discover ProtectBuy™2.0
• ITMX LSS EMV 3DS
For information on how to add 3DS authentication to your gateway integration, refer to EMV 3-
D Secure Authentication in the API Online Integration Guidelines.
3DS rules allow you to configure options to filter transactions based on the 3DS authentication
results. Only transactions with an authentication scheme that has been enabled for the
merchant will be filtered by 3DS rules. Note that the gateway by default rejects transactions
where payer authentication failed.
Procedure
1. Select Transaction Filtering > 3-D Secure Rules from the submenu.
The Transaction Filtering - 3-D Secure Rules configuration page is displayed.
2. Select Learn More to learn about 3-D Secure Rules and how to configure them.
NOTE: The gateway always rejects transactions where the payer failed to provide valid authentication
credentials when requested by the issuer. 3-D Secure transaction filtering rules will not be applied to
direct marketing transactions (mail order, telephone order, voice response, call centre), card present
transactions or device payments. Verify transactions, subsequent recurring transactions and
installment payments are also excluded from filtering by 3-D Secure transaction filtering rules. If the
payment transaction is in scope for PSD2 SCA and an acquirer exemption has been requested,
Transaction Filtering rules will not be applied.
Transaction Filtering Rule: 3DS Not Attempted will reject transactions where:
• 3DS authentication of the payer was not attempted. This includes cases where a 3DS
interaction was:
– Not initiated, or
– Initiated and the card was enrolled for 3DS. However, authentication of the payer was not
attempted or not completed.
Transaction Filtering Rule: Gateway Recommends Reject will reject transactions where:
• The card scheme recommends not to proceed, or processes the transaction as fully
authenticated, authentication attempted, or an unauthenticated transaction.
• The gateway determines this after evaluating the 3DS authentication results against the
card scheme's recommendation.
Transaction Filtering Rule: No Liability Shift will reject transactions where:
• 3DS authentication of the payer has not resulted in liability shift to the issuer.
Transaction Filtering Rule: Not Fully Authenticated will reject transactions where:
• Full 3DS authentication of the payer was not accomplished.
The Address Verification Service (AVS) is a security feature used for e-commerce transactions. It
compares the card billing AVS data that the cardholder supplies with the records held in the
database of the card issuer. Once the transaction is successfully processed and authorized, the
card issuer returns a result code (AVS result code) in its authorization response message. The
result code verifies the AVS level of accuracy used to match the AVS data.
Procedure
1. Select Transaction Filtering > AVS Rules from the submenu.
The Transaction Filtering - AVS Rules configuration page is displayed.
2. In the Configure AVS Response Codes pane, select an action for each AVS response code.
No Action (default) Accept transactions returning the selected AVS response code.
Review Mark transactions returning the selected AVS response code for
review.
Reject Reject transactions returning the selected AVS response code.
3. Click Save to save the AVS Rule.
4. Click Cancel if you want to exit the AVS Rules page without saving any changes.
Procedure
1. Select No Action against the CSC response code.
2. Select Save.
Procedure
1. From the Create Order page or Verify Only page, select Transaction Filtering.
2. Under the Order Details (from Create Order page) or Payment Details (from Verify Only
page), click Transaction Filtering.
The Transaction Filtering menu expands the displaying drop-down list for different
attributes for which you want to set the AVS response code rules.
3. Select the appropriate drop-down menu (No action, Reject, or Review) to override the AVS
response codes for the attributes as per your requirement.
Merchants can override the AVS Response Code Transaction Filtering rules. The merchant
defines these rules in Merchant Administration for a specific transaction by providing the
Transaction Filtering rule to apply for the transaction on the API request. See Online
Integration Guide for the details of implementation.
Procedure
1. Select Transaction Filtering > CSC Rules from the submenu.
The Transaction Filtering - CSC Rules configuration page is displayed.
2. In the Configure CSC Response Codes pane, select an action for each CSC response code.
No Action Accept transactions returning the selected CSC response code.
(default)
Review Mark transactions returning the selected CSC response code for
review.
Reject Reject transactions returning the selected CSC response code. For the
response code (M) CSC Match, the Reject action is disabled.
3. Click Save to save the CSC Rule.
4. Click Cancel if you want to exit the CSC Rules page without saving any changes.
Procedure
1. Select No Action against the CSC response code.
2. Select Save.
A risk service provider integrates with the gateway to perform risk assessment of transactions
processed through the gateway. When an MSO enables transaction filtering, the gateway prescreens
the transaction before sending it to the risk service provider for risk scoring. For more information
about filtering transactions through the gateway, see Transaction Filtering.
One of the features available through the Risk Management section is 3D Secure Control. It allows
users to set up automatic rules accepting or rejecting transactions based on specific circumstances.
It also applies to the new version of the feature EMV 3DS.
Those rules can also be changed as and when needed.
For more information about the risk assessment, see Risk Assessments for Review.
For more information about the privileges of a merchant operator, see Merchant Operator
General Privileges.
Internal risk
The transaction filtering functionality supersedes the internal risk functionality of the gateway.
A merchant can configure all the existing internal risk rules under transaction filtering with
updates to the 3-Domain (3-D) Secure rules. The Risk Management 3-D Secure rules are
available for configuration until a merchant activates the transaction filtering 3D-Secure rules.
The ACS subjects the payer to a challenge, for example, entering a PIN, only where extra
verification is necessary to authenticate the payer who provides increased conversion rates.
NOTE: The links provided in this guide are for a test environment. To access a production environment,
you must follow the appropriate steps. The Merchant Admin Portal may be accessed as an
administrator or user.
Procedure
1. Select Transaction Filtering > 3-D Secure Rules from the submenu.
The 3-D Secure Rules configuration page is displayed.
2. In the Configure Clash Action pane, select the action you want to perform when the risk
rules evaluate to both Always Accept and Always Reject.
By default, the action is Always Reject.
3. Select the action for each 3DS authentication state.
No action (default) Accepts transactions that return the selected 3DS authentication
state.
Review Marks transactions that return the selected 3DS authentication state
for review.
Reject Rejects transactions that return the selected 3DS authentication
state.
4. Select Save to save the 3DS rule that includes the clash rule configuration.
5. Select Cancel if you want to exit the 3DS Rules configuration page without saving any
changes.
Select Learn Moreto learn about 3-D Secure Rules and how to configure them.
Risk rules evaluation
Internal risk evaluates rules based on the action associated with that rule.
The risk service provider determines a risk status. They must evaluate all the rules associated
with a transaction that include the rules that the payment service provider defines.
Occasionally, these rules can clash when they evaluate to both, Always Accept and Always
Reject and fail to determine the final action on the order.
For example, if the gateway lists a card number as a Suspect Card (Always Reject) and the 3DS
rule results in Always Accept for an authentication state, then the system encounters a rule
deadlock. Deadlock requires an operator's intervention to break the deadlock. In such a case, the
action set for the clash rule comes into effect to determine the final action on the order.
The following are the risk status that the risk service provider determines.
Always Accept Accepts the transaction by overriding all other actions except Always Reject.
Always Reject Rejects the transaction by overriding all other actions except Always Accept.
Procedure
1. Change the configured actions against the 3DS authentication states anytime.
NOTE: You can enable Always Accept for the authentication state Y-Card Holder Verified only.
2. Save the changes.
Procedure
1. Select No Action against the 3DS authentication state.
2. Save the changes.
3DS check
If an MSO enables and configures the 3DS authentication scheme, the gateway performs the
3DS authentication.
If payer authentication fails, the gateway automatically rejects the transaction.
Pretransaction check
Pretransaction check refers to risk assessment before performing the transaction.
The acquirer's transaction response data, which includes Address Verification Service (AVS) and
Card Security Code (CSC) results, is not available for risk assessment. The transaction is
incomplete if the risk assessment result is reject, no voids or reversals.
If an MSO has configured a risk service provider for a merchant to run before transaction
processing, the gateway sends the transaction directly to the risk service provider for risk
scoring before performing the transaction.
Post-transaction check
Post-transaction checks refer to assessment after performing the transaction.
The transaction response data from the acquirer, which includes AVS and CSC results, is
available for risk assessment. If the recommendation is reject and the risk service provider
assesses the transaction for verification only, then the gateway does not require no voids or
reversals as the system has not submitted the financial transaction yet. However, when the risk
service provider rejects an Authorization, Purchase, or Standalone Capture transaction after
assessment, the system automatically voids or reverses the transaction.
If the MSO operator has configured the risk service provider to run after transaction processing,
the gateway allows the transaction to proceed first, and then sends to the risk service provider
for risk scoring.
Review required The risk service provider assesses the order for risk and requires a review.
Accepted The risk service provider assesses and accepts the order for risk.
Rejected The risk service provider assesses and rejects the order for risk.
Not Assessed The risk service provider assesses the order for risk except for risk assessment
by the MSO-configured rules and these rules do not reject the order.
Procedure
1. Select Tenant Configuration to view the risk service provider Tenant Configuration page.
2. Select OK to answer the questionnaire later.
If the MSO has changed the tenant details at the Merchant Manager level, such as changing
the merchant currency, the merchant may get a prompt to reanswer the questionnaire.
NOTE: This mapping applies only to merchants with a Silver or Gold service levels.
This table shows how the role of a risk service provider aligns with the merchant operator
privileges in Merchant Administration.
Merchant Operator
May Configure Risk Risk service provider Link to the risk service Key Capabilities in the
Rules Role provider risk service provider
˟ Merchant Fraud Support View in the External View transaction details.
Risk Provider link
displays in the order and
transaction details
screen.
NOTE: If at any step, either transaction filtering rules or risk service provider rules evaluate to reject
the transaction, the order is blocked, and further checks will not be performed. The order will be
reversed where appropriate.
NOTE: When transaction filtering rules or the risk service provider rules evaluate to accept or review,
the transaction will progress to the next step of assessment until all checks have been performed and
a final assessment result of accept or review can be returned.
Step Description
1) 3DS check If a 3DS authentication scheme is enabled and
configured, 3DS authentication is performed. If
payer authentication fails, the gateway
automatically rejects the transaction.
2) MSO pretransaction checks Transaction filtering rules configured by the MSO
are run before performing the transaction
3) Merchant pre-transaction checks Transaction filtering rules configured by the
merchant are run before performing the
transaction.
4) Risk service provider pretransaction checks If the risk service provider is configured to run
before transaction processing, the transaction will
be sent directly to the risk service provider for risk
scoring before the transaction is performed.
Pretransaction checks refer to assessment before performing the transaction. No transaction response
data from the acquirer (AVS and CSC results) will be available for assessment. If the assessment result
is Reject, voids or reversals are not applicable as the transaction has not yet been performed.
5) Process transaction The gateway processes the transaction.
6) MSO post-transaction checks Transaction filtering rules configured by the MSO
are run after performing the transaction.
7) Merchant post-transaction checks Transaction filtering rules configured by the
merchant are run after performing the
transaction.
8) Post-transaction checks If the risk service provider is configured to run after
transaction processing, the transaction will be
performed first and then sent to the risk service
provider for risk scoring.
Post-transaction checks refer to assessment after performing the transaction. The transaction response
data from the acquirer (AVS and CSC results) will be available to be assessed. If the recommendation is
Reject, and if the transaction that was assessed is Verification Only, then no voids or reversals are
required as the financial transaction has never been submitted. However, when an Authorization,
Purchase, or Standalone Capture transaction has been rejected after being assessed, the system will
automatically void or reverse the transaction.
Step Description
9) Assessment Result The assessment result from transaction filtering
and the risk service provider is returned in the
transaction response. This may be:
• Review required: The order was assessed and
requires a review.
• Accepted: The order was assessed and
accepted.
• Rejected: The order was assessed and rejected.
• Not Assessed: The order was not assessed
except for assessment by MSO-configured rules
and these rules did not reject the order.
NOTE: If the merchant has not configured any rules or if the merchant rules are bypassed, the rules
configured by the MSO are always applied to the transaction.
NOTE: Assessment after the financial transaction, also known as post-transaction assessment, is not
applicable to Referred transactions (Authorization or Purchase transactions that received a Refer to
Issuer acquirer response).
Procedure
1. Go to Search > Orders and Transactions.
2. Enter the order or transaction details, and then select Search.
Mercado Pago is a processor that provides services in the Latin American region and offers support
for a wide range of acquirers and alternative payment methods. Mercado Pago Checkout is one of
the payment options for Mercado Pago.
NOTE: The delay in the updated changes to reflect may impact the Mercado Pago payments
processed during this time.
2. The payment service provider configures the access token on behalf of the merchant.
NOTE: The links provided in this guide are for a test environment. To access a production environment,
you must follow the appropriate steps. The Merchant Admin Portal may be accessed as an
administrator or user.
Procedure
1. Go to Admin > Mercado Pago Integration Settings.
2. In the Configure Access Tokens section, select Add against your preferable currency.
3. Enter the access token number in the Access Token column, and then select Submit.
Procedure
1. Go to Admin > Mercado Pago Integration Settings.
2. In the Access Tokens section, identify the currency that you want to edit, and then select
Edit.
3. Enter the required access token number, and then select Submit.
Procedure
1. Go to Admin > Mercado Pago Integration Settings.
2. In the Access Tokens section, identify the currency that you want to delete, and then select
the Select check box.
3. Select Delete.
Notices
Following are policies pertaining to proprietary rights, trademarks, translations, and details
about the availability of additional information online.
Proprietary Rights
The information contained in this document is proprietary and confidential to Mastercard
International Incorporated, one or more of its affiliated entities (collectively “Mastercard”), or
both.
This material may not be duplicated, published, or disclosed, in whole or in part, without the
prior written permission of Mastercard.
Trademarks
Trademark notices and symbols used in this document reflect the registration status of
Mastercard trademarks in the United States. Consult with the Global Customer Service team or
the Mastercard Law Department for the registration status of particular product, program, or
service names outside the United States.
All third-party product and service names are trademarks or registered trademarks of their
respective owners.
EMV® is a registered trademark of EMVCo LLC in the United States and other countries. For
more information, see http://www.emvco.com.
Disclaimer
Mastercard makes no representations or warranties of any kind, express or implied, with respect
to the contents of this document. Without limitation, Mastercard specifically disclaims all
representations and warranties with respect to this document and any intellectual property
rights subsisting therein or any part thereof, including but not limited to any and all implied
warranties of title, non-infringement, or suitability for any purpose (whether or not Mastercard
has been advised, has reason to know, or is otherwise in fact aware of any information) or
achievement of any particular result.
Translation
A translation of any Mastercard manual, bulletin, release, or other Mastercard document into a
language other than English is intended solely as a convenience to Mastercard customers.
Mastercard provides any translated document to its customers “AS IS” and makes no
representations or warranties of any kind with respect to the translated document, including,
but not limited to, its accuracy or reliability. In no event shall Mastercard be liable for any
damages resulting from reliance on any translated document. The English version of any
Mastercard document will take precedence over any translated version in any legal proceeding.