❓ Frequently Asked Questions
Welcome to the VisaGlobalServer Help Center. Find answers to common questions about our software, protocols, and security.
🔑 Access & Security
What is the primary purpose of the VGS application?
The VGS (VisaGlobalServer) application is the official desktop client for authorized agents and partners.
Its primary purpose is to access 'privileged functions' within the card networks. This enables fund execution that can 'bypass standard authorization and settlement rules'.
How long is an Access Token valid after generation?
Each Access Token is valid for 7 days from the moment it is generated.
When exactly is my Access Token 'consumed'?
Your token is not consumed when you log in. The token is permanently 'consumed' when you initiate your first 'NEW TRANSACTION' after logging in.
Once consumed, the token cannot be used again to start a new transaction session.
Why did my login fail? I'm sure my token is correct.
Based on the system documentation, a login failure is most often caused by one of these three reasons:
- The token was mistyped.
- The token has expired or has already been consumed.
- The source card was not 'prepared' in the web portal before you attempted to log in.
When does the 5-minute session timer start?
The 5-minute security timer begins immediately after you authenticate your Token and click the 'NEW TRANSACTIONS' button.
Once this session is active, you have 5 minutes to complete all data entry. The session will automatically terminate after 5 minutes to protect your account and transaction data.
What is the 'SYSTEM IP' in the application header, and why does it keep changing?
The displayed IP is part of our internal Secure Proxy Network (SPN). It is intentionally designed to change every few seconds.
This is a normal part of the system's operation to enhance security, anonymity, and ensure a stable connection to our global servers. This connection is tied to official processing ASNs (like ASN 2559 for Visa) for maximum compliance.
Why does the 'SYSTEM IP' keep changing even when I'm offline?
The application runs a local scheduler that rotates the display of the IP addresses. Even when offline, this scheduler continues to run and display the next IP from its pre-loaded list.
However, no connection is being made. The system is only cycling in the background. Full functionality and active connections are only established once you are back online.
Why did my login fail with an 'Update Required' message?
For security and compliance reasons, the application automatically checks for the latest version when you log in. If your version is outdated (e.g., you are using v3.5.0 when v3.5.1 is available), the server will block the login.
You must download the newest version from the member dashboard to continue.
💳 Transactions & Protocols
What is the difference between a “DECLINED” and an “ERROR” status?
These are two different outcomes:
- ERROR (e.g.,
ERROR 503): This is a technical error. It usually indicates a connection problem, the server is down, or the request format is incorrect. Each error code has a clear technical meaning. - DECLINED: This means the request was successfully processed by the issuing bank, but it was rejected. This can happen for many reasons, such as:
- The transaction data (card, expiry date) does not match the data prepared on the server.
- The card was not injected or prepared correctly.
- The received data was not genuine or failed the bank's internal validation.
What is the difference between Protocol 201 and Protocol 201.3?
These protocols use different methods for transaction processing.
- Protocol 201 is a general category (
201 Offline Auth). You should select this if your loader or banker does not specify a particular protocol. - Protocol 201.3 is a more specific sub-protocol (
201.3 Offline 6 DG).
Always use the protocol specified by your provider to ensure success.
What is the 'BIN Checker' feature?
The 'BIN Checker' is a utility integrated with a service similar to the Visa BIN Attribute Sharing Service (VBASS). This feature allows you to enter the first 6-8 digits of a card number to validate:
- The Issuing Bank
- The Card Type (e.g., DEBIT/CREDIT)
- The Card Level (e.g., CLASSIC/PLATINUM)
Is this application only for VISA?
No. The application fully supports both Visa and Mastercard protocols. You can switch between the 'Visa' and 'Mastercard' themes on the login screen. Changing the theme also adjusts the relevant system configuration (like ASN and TX Prefix) to match the correct network.
💸 Payouts & System
How does the Payout/Settlement system work?
The system is connected to our proprietary global payout network, which is built on the foundation of 'Visa Direct'. This enables real-time push payment delivery.
You can configure it in the 'Settings' menu to support:
- Crypto Wallet Payout: Funds are sent to a Crypto address (e.g., TRC20).
- International Bank Payout: Funds are sent as an Original Credit Transaction (OCT) via SWIFT to an international bank account.
What is the 'Settlement Split' (Receiver % and Sender %)?
'Settlement Split' is a feature of the Crypto Payout method. It allows you to automatically divide the funds from a successful transaction between two destination wallets:
- Receiver Wallet
- Sender Wallet
This division is based on the percentage you set when entering the transaction details.
Can I integrate my own system with VGS via an API?
Yes. In addition to this desktop application, we also provide a 'Developer API Reference' (Public v1) for direct integration.
This public API allows you to build your own applications by accessing public endpoints like get_token_details.php (to check token status) and bin_checker.php (for BIN validation).
Does this application connect directly to the Visa or Mastercard networks?
Yes, functionally. This desktop application is a 'direct interface' to the VisaGlobalServer core system.
Our core system then directly accesses 'privileged functions within card networks' and is built upon the 'Visa Direct' foundation. All connections are routed through our Secure Proxy Network (SPN), which is tied to official processing ASNs (like ASN 2559) to ensure secure, industry-standard communication.