Q: What is the messgae type used by Visisonplus for its credit card transaction

processing
VisionPLUS, a popular credit card processing system developed by First Data (now
Fiserv), uses various message types for its transaction processing. The primary
message format utilized in VisionPLUS for credit card transactions is based on the
ISO 8583 standard.

ISO 8583 Message Types

ISO 8583 is an international standard for systems that exchange electronic
transactions made by cardholders using payment cards. It defines a message format
and a communication flow so that different systems can exchange these transactions
in a standardized way.

Here are the key components of ISO 8583 messages:

Message Type Indicator (MTI): This is a 4-digit numeric field that indicates the
type of message and its purpose. For example:

0100: Authorization request

0110: Authorization response
0200: Financial transaction request
0210: Financial transaction response
0420: Reversal request
0430: Reversal response
Bitmap: A string of bits (binary digits) that indicates which data elements are
present in the message.

Data Elements: Specific fields within the message that carry transaction
information. Examples include:

Primary account number (PAN)

Processing code
Transaction amount
Transmission date and time
System trace audit number
Response code
VisionPLUS Message Handling
In VisionPLUS, these ISO 8583 messages are used to handle various types of credit
card transactions, such as:

Authorization: Requesting approval for a transaction from the card issuer.

Capture: Completing an authorized transaction.
Reversal: Canceling a previously completed transaction.
Refund: Returning funds to the cardholder.
Settlement: Finalizing the day's transactions and submitting them for clearing and
settlement.
VisionPLUS processes these messages to manage cardholder accounts, authorize
transactions, and perform end-of-day processing and settlement.

Example of ISO 8583 Message Structure

An example of an authorization request (MTI 0100) might look like this:

MTI: 0100
Bitmap: Indicates which data elements are present.
Data Elements:
DE 2: Primary Account Number
DE 3: Processing Code
DE 4: Transaction Amount
DE 7: Transmission Date and Time
DE 11: System Trace Audit Number
DE 32: Acquiring Institution Identification Code
DE 37: Retrieval Reference Number
DE 41: Card Acceptor Terminal Identification
DE 49: Currency Code
Summary
VisionPLUS uses ISO 8583 messages to handle credit card transaction processing.
Each message type and its corresponding data elements are used to perform specific
actions within the transaction lifecycle, ensuring standardized communication
between different financial systems and networks.

=======================================================================

Q:What is a Block code in VisionPlus?

A:
In the context of VisionPLUS, a "block code" refers to a specific code used within
the system to categorize and manage various types of credit card transactions,
account activities, and cardholder statuses. VisionPLUS uses these block codes to
facilitate the organization and processing of data related to credit card accounts
and transactions.

Purpose of Block Codes

Block codes in VisionPLUS are utilized for several key purposes:

Categorization: They help categorize transactions, account actions, and statuses to

streamline processing and reporting.
Routing: Block codes can be used to route transactions through appropriate
processing paths based on the type of transaction or action required.
Control: They enforce specific business rules and controls for different types of
transactions and account activities.
Reporting: Block codes enable detailed reporting and analysis by categorizing
transactions and account activities into predefined segments.
Common Types of Block Codes
While the exact codes and their meanings can vary based on the specific
implementation and customization of VisionPLUS, common types of block codes
include:

Transaction Block Codes: Codes that categorize different types of financial

transactions such as purchases, cash advances, payments, reversals, and
adjustments.
Account Status Block Codes: Codes that represent different statuses of a
cardholder's account, such as active, delinquent, closed, or suspended.
Cardholder Block Codes: Codes that pertain to the cardholder's profile, indicating
special conditions like VIP status, high-risk, or restricted use.
Example Block Codes
Here are hypothetical examples of block codes and their potential meanings:

Transaction Block Codes:

PUR: Purchase
CAD: Cash Advance
PAY: Payment
REV: Reversal
Account Status Block Codes:

ACT: Active
DEL: Delinquent
CLS: Closed
SUS: Suspended
Cardholder Block Codes:

VIP: VIP Customer

HRK: High-Risk Customer
RST: Restricted Use
How Block Codes are Used
Transaction Processing: When a transaction is processed, VisionPLUS assigns the
appropriate block code to the transaction based on its type. This helps in routing
the transaction through the correct processing workflow.
Account Management: Block codes are used to update and maintain the status of
cardholder accounts. For example, if an account becomes delinquent, the system
updates the account status block code accordingly.
Reporting and Analysis: Block codes facilitate detailed reporting and analysis by
segmenting transactions and account activities into specific categories. This aids
in monitoring, compliance, and strategic decision-making.
Summary
In VisionPLUS, block codes are integral to the efficient processing and management
of credit card transactions and account activities. They categorize and control
various actions within the system, ensuring that transactions are processed
accurately and accounts are managed effectively. These codes are essential for
routing, control, and reporting, providing a structured way to handle the diverse
activities associated with credit card operations.

==========================================================================

Q: Explain Base1 transaction flow in Visionplus

A:
In the VisionPLUS system, the BASE1 module is a critical component for managing
credit card transactions and cardholder account data. The BASE1 transaction flow
outlines the steps and processes involved in handling credit card transactions,
from authorization to settlement. Here’s a detailed explanation of the BASE1
transaction flow in VisionPLUS:

BASE1 Transaction Flow Overview

1.Transaction Initiation:
A transaction begins when a cardholder initiates a payment or withdrawal using
their credit card at a merchant's point of sale (POS) terminal, ATM, or online.
The transaction details are captured, including the card number, transaction
amount, merchant information, and any other relevant data.

2.Authorization Request:
The POS terminal or ATM sends an authorization request to the acquiring bank (the
merchant’s bank).
The acquiring bank forwards this request to the card network (e.g., Visa,
MasterCard), which then routes it to the issuing bank (the cardholder’s bank).

3.BASE1 Authorization Processing:

Upon receiving the authorization request, the BASE1 module in VisionPLUS processes
the request.
BASE1 validates the transaction details against the cardholder's account
information. This includes checking for:
Available credit limit
Card status (active, lost/stolen, etc.)
Fraud indicators
Transaction limits and restrictions

4.Authorization Response:
If the transaction is approved, BASE1 updates the cardholder’s available credit
limit and generates an authorization response.
If the transaction is declined, BASE1 provides a reason code for the decline.
The authorization response is sent back through the card network to the acquiring
bank and then to the merchant’s POS terminal or ATM.

5.Transaction Posting:
Approved transactions are temporarily held in a pending state until the end-of-day
processing.
During end-of-day processing (also known as batch processing), BASE1 posts the
transactions to the cardholder's account, updating balances and generating
necessary entries in the transaction ledger.

6.Settlement:
After posting, the transactions are sent to the settlement process, where funds are
transferred from the issuing bank to the acquiring bank.
This involves clearing the transactions through the card network, which ensures
that the merchant receives payment.

7.Statement and Reporting:

BASE1 generates periodic statements for cardholders, detailing all transactions,
payments, fees, and interest charges.
Reporting tools within VisionPLUS provide insights into transaction volumes,
authorization rates, and other key metrics for issuers.

Detailed Flow Diagram

Here’s a more detailed breakdown of the transaction flow steps:

1.Cardholder Initiates Transaction:

Transaction data is captured at the POS/ATM.
Data includes card number, amount, merchant ID, etc.

2.Authorization Request Sent:

POS/ATM → Acquiring Bank → Card Network → Issuing Bank.

3.BASE1 Authorization:
BASE1 validates transaction details.
Checks available credit, card status, fraud indicators, etc.
Decision: Approve or Decline.

4.Response Sent Back:

Issuing Bank → Card Network → Acquiring Bank → POS/ATM.
Authorization code or decline reason provided.

5.End-of-Day Processing:
Approved transactions are posted to cardholder accounts.
Balances are updated in BASE1.
Transactions are prepared for settlement.

6.Settlement Process:
Transactions are cleared through the card network.
Funds are transferred from issuing bank to acquiring bank.
Merchant receives payment.

7.Statement Generation:
Periodic statements are generated for cardholders.
Statements include all transactions, fees, interest, and payments.

8.Reporting and Analysis:

BASE1 provides data for various reports.
Reports include transaction volumes, authorization rates, and other metrics.

Key Features of BASE1 in VisionPLUS

Real-Time Processing: BASE1 handles real-time authorization requests and responses,
ensuring quick and accurate transaction approvals.
Fraud Detection: Integrated fraud detection mechanisms help identify and prevent
fraudulent transactions.
Comprehensive Reporting: Detailed reporting features support compliance,
operational monitoring, and strategic decision-making.
Scalability: BASE1 can handle high transaction volumes, making it suitable for
large-scale credit card operations.
Integration: BASE1 seamlessly integrates with other VisionPLUS modules, including
collections, rewards, and customer service, providing a unified platform for credit
card management.
Conclusion
The BASE1 transaction flow in VisionPLUS encompasses the entire lifecycle of a
credit card transaction, from initiation and authorization to posting and
settlement. By efficiently managing these processes, BASE1 ensures the smooth
operation of credit card services, maintaining accuracy, security, and customer
satisfaction.

===============================================================================