GP webpay - system administration

Transkript

GP webpay - system
administration
Version: 1.0
Global Payments Europe, s.r.o.
Created 14.8.2015
Last update 14.12.2015
GP webpay - system administration. Role: Merchant
Author
Dimitrij Holovka
Manager
Approved by
Version
1.0
Confidentiality
Confidential
Document history:
Version
1.0
Date
11.26.2015
Author
D. Holovka
Comments
Initial document version
Table of contents
1.
Formula clause ........................................................................................................................ 3
2.
Introduction .............................................................................................................................. 4
3.
Logging in to the GP webpay application ................................................................................. 4
4.
Main menu for the Merchant role ............................................................................................. 5
4.1
Administration ................................................................................................................... 6
4.1.1
Password change ...................................................................................................... 6
4.1.2
Downloads ................................................................................................................. 7
4.1.3
Users ......................................................................................................................... 8
4.2
Processing orders ............................................................................................................. 8
4.2.1
Orders ....................................................................................................................... 8
4.2.2
Deposit orders ......................................................................................................... 13
4.2.3
Deleting pending ...................................................................................................... 14
4.3
Batches........................................................................................................................... 16
4.3.1
Search batches ........................................................................................................ 16
4.3.2
Batch closure ........................................................................................................... 18
4.4
Log off ............................................................................................................................ 18
5.
Error statuses ........................................................................................................................ 19
6.
Annexes................................................................................................................................. 21
6.1
Order status .................................................................................................................... 21
6.2
Supported requests ........................................................................................................ 22
6.3
Return codes .................................................................................................................. 23
6.3.1
PRCODE - primary return code ............................................................................... 23
6.3.2
SRCODE - secondary return code ........................................................................... 24
Global Payments Europe, s.r.o., V Olšinách 80/626, 100 00 Prague 10 – Strašnice, Czech Republic
2 / 25
1. Formula clause
This document including any possible annexes and links is intended solely for the needs of an eshop service provider (hereinafter referred to as “Customer”).
Information included in this document (hereinafter referred to as "Information") are subject to
intellectual property and copyright protection of the Global Payments Europe, s.r.o. (hereinafter
referred to as "GPE") and are of a commercially confidential nature in accordance with the
provisions of the section 504 of the Act No. 89/2012 Coll., Civil Code. The Customer is aware of
the legal obligations in relation to the handling of Information.
Information or any part thereof may not be provided or in any way made available to third parties
without the prior written consent of the GPE. At the same time, Information may not be used by the
Customer for purposes other than for the purpose for which it serves. To avoid any doubts, without
the prior written consent of the GPE, Information or any part thereof may be provided or in any way
made available neither to companies providing payment processing services on the Internet.
The GPE to the extent permitted by applicable law retains all rights to this document and
Information contained therein. Any reproduction, use, exposure, or other publication, or
dissemination of Information or its part by methods known and as yet undiscovered without the
prior written consent of the GPE is strictly prohibited. The GPE is not in any way responsible for
any errors or omissions in Information. GPE reserves the right, without giving any reason, to
amend or repeal any Information
3 / 25
2. Introduction
This document is designed for merchants, who will accept payments in their e-shops carried out by
payment cards issued by VISA, MasterCard, Diners Club, and AMEX associations using the
Internet-based payment gateway GP webpay.
GP webpay supports fully the 3-D Secure standard and provides merchants with the possibility to
integrate the functionality of a standard web interface by means of Web Services (WS).
The application can be accessed via URL address: https://3dsecure.gpwebpay.com/gui
Note: All screenshots used in the following text were copied from the GPE, s.r.o, testing
environment and therefore their content does not have to fully correspond with the content of
screens in real operation of the application.
3. Logging in to the GP webpay application
After opening of the URL address, a screen for logging in to the GP webpay application is
displayed automatically. Access is permitted only after the username and password is entered.
Pic.1: Login screen
Based on the data entered, the application makes the concrete user environment accessible.
The merchant receives a password for the first login to the system from the GP webpay system
administrator in GPE together with the signed contract.
After successful login with this password, the GP webpay displays automatically a screen for the
password change. The merchant enters there his/her new password, which will be used for his/her
4 / 25
loging into the system in the future. It is in his/her own interest to use a password that is as
“complicated” as possible, to make it uneasy for unauthorized persons to deduce it.
The password should never be a simple repeating of the merchant´s username. Whole words, or
sequences of keys located next to each other on the keyboard, or sequences of numbers going
one after another, etc., are not suitable for this purpose as well.
This manual describes all the possibilities that are offered by the application for the role defined on
the side of the application user for the role of Merchant.
The main task of a user in the Merchant role (i.e. merchant’s administrator) is to process orders,
i.e. to search for orders in accordance with the given conditions, to pay for orders, to search for
batches, to close batches, or to delete incomplete orders.
4. Main menu for the Merchant role
After the user is loged successfully into the system, the introductory screen with the main menu of
the GP webpay application is displayed.
In heading of this screen – as well as of all the other screens – besides the application logo, there
is displayed the title of the society and username of the loged user.
Content of the menu (i.e. concrete user environment of the application) corresponds with the role
assigned to the loged user.
A language for further communication with the system can be selected by click on a relevant flag in
the right corner of the screen heading.
Pic.2: Successful login, Merchant role
5 / 25
Menu designed for a user with the Merchant role:
Administration:

Account setting

Change password;

Downloads – possibility to download documentation, support applications, certificates, logs,
and examples

Users – possibility to accommodate users’ accounts registered for your company;
Orders processing:

Search order – a possibility to find orders on the basis of identification of a merchant or an
order, according to order status, date of payment, or currency and amount. Display of a
summary of the orders found, possibility to display a detail of the selected order, including
offer of possible (allowed) transactions;

Deposit orders – display of all as yet unpaid orders (successfully authorized), a possibility
to display a detail of a selected order, including offer of possible transactions. Deposit of the
selected order, or of a group of orders;

Deleting unsettled orders – display of the summary of uncompleted orders, a possibility to
display detailed data of the selected order. Deletion of selected orders (individual, or all of
them);

Search batches – a possibility to find merchant´s batches on the basis of the batch´s
identification, according to the batch´s status, opening or closing date of the batch. Display
of summary of the searched out orders with a possibility to display selected batches.
Display of summary of orders included in the batch, a possibility to display a detail of the
order with an offer of other possible transactions. A possibility to close the opened batch;

Closing batches – a possibility to close the currently opened batch and thereby enable
further operations with the order.

Logout – logout of the current user from GUI.
4.1 Administration
Primary actions for setting up access rights, documentation download.
4.1.1 Password change
Clicking on Password change in the “Administration” menu opens the Password change screen.
After entering the old and new password, confirmation of the new password is requested.
6 / 25
Following the data sending, if the password change has been successful, information about the
carried out change is displayed. The user is invited to change the password automatically after the
first login.
The choice “Change password” is a part of the menu designed for a user loged into the application
by a name and a password.
The period of validity of the password is set by the system administrator in GPE, s.r.o.
Pic.3: Change password
4.1.2 Downloads
In this section, there are all necessary resources for successful implementation and using of the
GP webpay payment gateway.

Documentation both in Czech and in English

Logos of GP webpay and card associations

Examples in PHP, Java, and .Net

Applications for private key generating, keystore formats converter
7 / 25
Pic.4: Downloads
4.1.3 Users
This choice displays overview of your company’s users. It enables changing of assigned roles,
password change, adding new users.
4.2 Processing orders
4.2.1 Orders
The choice enables searching orders and their administration. The Search order screen is
displayed.
It is important to set up the filter correctly. If the chosen criteria are too general, timeout can
appear and the application displays an error.
8 / 25
Pic.5: Searching for orders – filter
Options of the setting of the Merchant filter

Merchant: the merchant´s name, the local offer is available;

Bank: if you have more merchants at various banks, criteria limiting banks can be set;

Order number: the order number in the GP webpay application – ORDERNUMBER field;

Merchant order: the order number in the merchant’s system – MERORDERNUM field;

Time created from – to: creation date of the order, max. 35 days;

Amount from - to: amount range;

Currency: offer of enabled currencies;

Associations: selecting orders according to a payment card used;

Status: desired status of the order is to be ticked in the checking field, see Annex: Order
status
Ticked/filled-in criteria are confirmed by pressing the Search button.
After submitting an empty form, all orders of the selected merchant will be searched out, except
from the orders in the DELETE status.
Searched out orders
9 / 25
In the summary of orders searched out according to criteria specified in the previous step, there is
displayed basic information about the found orders.
Pic.6: Orders
In the search result, there is displayed a brief overview of the found orders. In the bottom part of
the list, there is the total number of the orders found. GP webpay displays maximally 100 items per
page in response to 1 request; it means that if the number of selected orders is higher, not all of
the orders are displayed. In case of higher total number of orders, there are displayed browsing
arrows. Therefore it is recommended to input an as precise as possible request to search for a
concrete order.
In the summary of authorized orders, the merchant selects individual orders for further processing.
The Select all button can be used for marking of all orders at the same time.
All the originally not ticked orders will be marked after clicking on the Inverse selection button.
The Cancel selection button cancels the selection made up to now; marking of all ticked fields will
be cleared away at the same time.
Processing orders
10 / 25
A precondition for processing of the marked orders is setting up of the corresponding Keystore and
entering Password for access into this keystore1. This is a standard way of confirmation of all
requests for processing in GP webpay.
Submission of a request has to be confirmed once more. In case of multiple orders it can be e.g.
the Deposit the selected items button, or the Delete the selected items button.
If detailed data of the selected order is displayed, then there is the Processing button available
(this button carries out an operation selected from Transactions).
Pic.7, 8: Entering of Keystore and password
Order details
Detailed information about the selected order will be displayed after clicking on an item in the
summary of orders:
Pic.9: Detail
Besides basic information about the order, the GP webpay offers also the option Transactions.
Further possible processing depends on the current status of the order.
1
Password and Keystore generates the merchant by himself/herself at the moment of signing the contract with GPE, s.r.o..
11 / 25
For example an authorized order can be deposited (DEPOSIT) or the order authorization can be
invalidated (APROVE_REVERSAL).
If entering the amount is requested, the amount has to be entered in the same format as shown in
the overview – i.e. with decimal point. E.g.: the amount 10 crowns and 30 hellers is entered as 10.3
(or 10,30). This is a crucial difference from other parts of order processing (creation, manipulation
via web services), where the amount is entered without decimal point (i.e. 1030).
A detailed description of the order status, see Annex: Order status.
Description of supported requests (possible transactions), see Annex: Supported requests
If a user marks one of the enabled transactions, GP webpay may offer in some cases another field
for filling-in of necessary data.
For example as concerns the CREDIT or DEPOSIT requests, Amount of credit (deposit) has to be
specified as well, if CREDIT_REVERSAL is requested, the number of credit (Number) has to be
added.
The Process request for an individual order is confirmed in the usual fashion (entering of Keystore
path and password).The user is informed about the result of processing.
Information about the result of the order processing:
Pic.10: Information about the successful order processing
In the report about the successful order processing, there are the primary (PRCODE) and the
secondary (SRCODE) return codes set to “0” value; the text designed for the error description
contains “OK” value, the OK-column contains a green point.
12 / 25
In the report about the unsuccessful order processing, the PRCODE return code contains the type
of error, while SRCODE contains specification of this error. The text describes the type of error and
the OK-column contains a red point.
Pic.11: Information about unsuccessful processing of an order
For description of return codes, see Annex: Return codes.
4.2.2 Deposit orders
The summary of successfully authorized orders is displayed after selection of Deposit orders.
These orders are in the status “authorized” - APPROVED and they are ready for deposit.
13 / 25
Pic.12: The searched-out orders designated for deposit
Detailed information about the selected order will be displayed after clicking on an item in the
summary of orders; it means that before the transaction is authorized, some data may still be
verified.
Orders for processing can be selected one by one (by ticking) or they can be marked altogether
(the Select all button), or there can be used the button to Inverse selection. After the request is
confirmed, the marked orders will be processed.
The result of a successfully processed (i.e. deposited) order is a request for entering the order into
accounts. This request is transmitted to the card issuer.
The carried-out deposit can be invalidated.
The request for invalidation of the deposit can be used only for deposited orders, which have not
been processed yet, i.e. the batch containing this order has not been closed.
4.2.3 Deleting pending
After selecting Deleting pending, the summary of all orders in the REQUESTED status is
displayed.
14 / 25
Pic.13: Pending orders
Orders to be processed (delete) can be selected one by one (by ticking) or they can be marked
altogether (the Select all button), or there can be used the button for Inverse selection.
After the request is confirmed in a standard way, the marked requested orders will be deleted.
Information about the result of processing is displayed, e.g.:
Pic.14: Results of orders processing
15 / 25
Details of a deleted order
If the Transaction result screen will contain the summary of deleted orders, then after clicking on
a selected item, the following basic information will be displayed:
Pic.15: Details of a deleted order
4.3 Batches
4.3.1 Search batches
After selecting Search batches, the Search batch screen with a relevant form – filter/search
criteria – is displayed.
16 / 25
Pic.16: Searching for batches – filter
Options of the filter setting:

Merchant: the merchant’s name. The local offer is available;

Batch number: the number of batch;

Date of batch opening from – to;

Date of batch closing from – to;

Status: choice according to the batch status.
List of batches
Information about the result of searching contains the number of searched-out and displayed
items.
In the summary of the searched-out batches, there is displayed a number and status of the batch,
time of opening and closing of the batch.
Detail of a batch
After clicking on the selected item, there will be displayed basic information about the batch
together with the summary of all payments (Payments tab) and credits (Credits tab) contained in
this batch.
The opened batch can be closed.
17 / 25
Pic.17: Detail of a batch
4.3.2 Batch closure
Opened batches are searched out automatically and their closing is offered.
Pic.18: Batches to be closed
4.4 Log off
To log out from the application is designed the Log off option.
18 / 25
After clicking on this offer, the following information is displayed “You have successfully logged out
from the application”.
5. Error statuses
The application distinguishes between two types of messages – information and error messages.
Both types of messages are displayed above the form, to which they are referring.
The Information message (a blue form) usually informs about the result of the just completed
action.
Pic.19: Information message
The Error message (a red form) notifies of serious errors that have to be corrected, otherwise
processing cannot continue.
19 / 25
Pic.20: Error message
20 / 25
6. Annexes
6.1 Order status
Status
REQUESTED
Status description
Possible
following
statuses
The order has been successfully received by GP webpay. The system now waits for
the result of sensitive data filled in (entered) by the cardholder.
After the card holder enters sensitive data, the request is sent to the 3D system to find
out if authentication of the card holder is required. The system waits for the result from
the 3D system.
If the cardholder stops entering the card data, this will be the final status of the order.
CANCELLED
Payment is cancelled by the card holder (he/she has chosen an option “Back to eshop” on the payment gateway)
APPROVED
The result of the authentication of the card holder in 3D has been successful, a request
for authorization is sent to the authorization centre.
DEPOSITED
The result of the authorization is successful.
REVERSED
If the order is in APPROVED status for more than 30 days, authorization is cancelled
automatically and the order cannot be processed any more.
DELETED
AUTO CANCELLED
It is to meet directives of the card associations regarding “pending hold”.
REVERSED
The authorization of the order is invalidated.
DELETED
The money previously authorized has been unblocked.
UNAPPROVED
The result of the authorization of the order is not successful. The order cannot be paid
for.
DELETED
The system cannot continue.
DEPOSITED
The order has been marked for payment during the following batch processing.
PROCCESED
The payment can be invalidated before the batch containing the payment is closed.
APPROVED
The batch has been automatically closed and the data has been transmitted to the
financial systems.
CREDITED
CLOSED
The order has been closed. The only allowed operation now is deletion.
DELETED
AUTO CLOSED
The order has been closed automatically. This situation appears automatically after
defined period.
DELETED
PROCESSED
CLOSED
It is to meet directives of the card associations and technical limits of bank systems.
DELETED
The order has been deleted.
CREDITED
The order has been marked for return during the following batch processing.
CLOSED
A return of the order can be invalidated any time before the batch containing the order
is closed. The order remains in this status after the batch is closed.
More than one credit can be created for an order.
DECLINED
The result of the authentication of the card holder in the 3D system has not been
successful.
DELETED
The card holder has not been authenticated. The system cannot continue. The order
can be deleted.
21 / 25
6.2 Supported requests
Request
Meaning
Description
approveReversal
Invalidation of the order
authorization
Request to make the authorization of an order
invalid.
Possible
previous
statuses
Possible
final
statuses
APPROVED
REVERSED
APPROVED
DEPOSITED
DEPOSITED
APPROVED
Request to return the payment for orders that
have already been processed.
PROCESSED
CREDITED
It is used to mark an order for further
processing after which the money will be
transferred back from the merchant to the card
holder.
CREDITED
Request to cancel the reversal of the payment
for an order.
CREDITED
DEPOSITED
Applicable only to orders made invalid that
have not yet been processed - the money will
not be transferred back from the merchant to
the cardholder.
The batch
containing the
credit must still
be opened
(if there are no
other valid
credits)
Applicable only to successfully authorized
orders.
deposit
Payment of an order
Request to pay (to account for) an order. It is
used to mark an order for further processing
after which a request for the accounting for of
the financial transaction is sent to the acquirer
bank.
The accounting for of the transaction is the
responsibility of the acquirer bank.
Applicable only to successfully authorized
orders.
depositReversal
Making a payment for
the order invalid
Request to make the payment of an order
invalid.
Applicable only to paid orders that have not yet
been processed. The money will not be
transferred from the card holder to the
merchant.
credit
creditReversal
Return of an order
Making the return of an
order invalid
CREDITED
closeOrder
Closing of an order
Request to close an order
DEPOSITED
CLOSED
PROCESSED
CREDITED
delete
Deleting of an order
Request to delete an order
DECLINED
DELETED
UNAPPROVED
REVERSED
CLOSED
batchClose
Closing of a batch of
orders
Request to close a batch containing orders
marked for further processing.
This request does not necessarily need to be
sent.
Batches are closed automatically before they
are processed.
22 / 25
6.3 Return codes
The system provides merchants feedback in the form of return codes. Two return codes are always
returned:
1. PRCODE (PrimaryReturnCode) – main information about error status
2. SRCODE (SecondaryReturnCode) – additional information about error status
6.3.1 PRCODE - primary return code
Value
Meaning in Czech
Meaning in English
0
OK
OK
1
Pole příliš dlouhé
Field too long
2
Pole příliš krátké
Field too short
3
Chybný obsah pole
Incorrect content of field
4
Pole je prázdné
Field is null
5
Chybí povinné pole
Missing required field
11
Neznámý obchodník
Unknown merchant
14
Duplikátní číslo objednávky
Duplicate order number
15
Objekt nenalezen
Object not found
17
Částka k úhradě překročila autorizovanou částku
Amount to deposit exceeds approved amount
18
Součet kreditovaných částek překročil uhrazenou
částku
Total sum of credited amounts exceeded deposited
amount
20
Objekt není ve stavu odpovídajícím této operaci
Object not in valid state for operation
Info: Pokud v případě vytváření objednávky
(CREATE_ORDER) obdrží obchodník tento návratový
kód, vytvoření objednávky již proběhlo a objednávka
je v určitém stavu – tento návratový kód je zapříčiněn
aktivitou držitele karty (například pokusem o přechod
zpět, použití refresh…).
25
Uživatel není oprávněn k provedení operace
Operation not allowed for user
26
Technický problém při spojení s autorizačním centrem
Technical problem in connection to authorization
center
27
Chybný typ objednávky
Incorrect order type
28
Zamítnuto v 3D
Info: důvod zamítnutí udává SRCODE
Declined in 3D
30
Zamítnuto v autorizačním centru
Info: Důvod zamítnutí udává SRCODE
Declined in AC
31
Chybný podpis
Wrong digest
35
Expirovaná session
Session expired
Nastává při vypršení webové session při zadávání
karty
50
Držitel karty zrušil platbu
The cardholder canceled the payment
200
Žádost o doplňující informace
Additional info request
1000
Technický problém
Technical problem
23 / 25
6.3.2 SRCODE - secondary return code
Value
0
Meaning in Czech
Bez významu
Meaning in English
No meaning
If PRCODE is 1 to 5, 15 and 20, the following SRCODE may return
1
ORDERNUMBER
ORDERNUMBER
2
MERCHANTNUMBER
MERCHANTNUMBER
6
AMOUNT
AMOUNT
7
CURRENCY
CURRENCY
8
DEPOSITFLAG
DEPOSITFLAG
10
MERORDERNUM
MERORDERNUM
11
CREDITNUMBER
CREDITNUMBER
12
OPERATION
OPERATION
18
BATCH
BATCH
22
ORDER
ORDER
24
URL
URL
25
MD
MD
26
DESC
DESC
34
DIGEST
DIGEST
If PRCODE is 28, the following SRCODE may return
3000
Neověřeno v 3D. Vydavatel karty není zapojen do 3D
nebo karta nebyla aktivována.
Info: Ověření držitele karty bylo neúspěšné (neplatně
zadané údaje, stornování autentikace, uzavření okna pro
autentikaci držitele karty se zpětnou vazbou…).
Declined in 3D. Cardholder not authenticated in 3D.
Note: Cardholder authentication failed (wrong password,
transaction canceled, authentication window was
closed…).
Transaction Declined.
V transakci se nesmí pokračovat.
3001
3002
3004
Držitel karty ověřen.
Authenticated
Info: Ověření držitele karty v 3D systémech proběhlo
úspěšně. Pokračuje se autorizací objednávky.
Note: Cardholder was successfully authenticated –
transaction continue with authorization.
Neověřeno v 3D. Vydavatel karty nebo karta není
zapojena do 3D.
Not Authenticated in 3D. Issuer or Cardholder not
participating in 3D.
Info: V 3D systémech nebylo možné ověřit držitele karty –
karta, nebo její vydavatel, není zapojen do 3D.
Note: Cardholder wasn’t authenticated – Issuer or
Cardholder not participating in 3D.
V transakci se pokračuje.
Transaction can continue.
Neověřeno v 3D. Vydavatel karty není zapojen do 3D
nebo karta nebyla aktivována.
Not Authenticated in 3D. Issuer not participating or
Cardholder not enrolled.
karta není aktivována, nebo její vydavatel, není zapojen do
3D.
Note: Cardholder wasn’t authenticated – Cardholder not
enrolled or Issuer or not participating in 3D.
Transaction can continue.
V transakci je možné pokračovat.
3005
Zamítnuto v 3D.Technický problém při ověření držitele
karty.
Declined in 3D. Technical problem during Cardholder
authentication.
vydavatel karty nepodporuje 3D, nebo technický problém
v komunikaci s 3D systémy finančních asociací, či
vydavatele karty.
Note: Cardholder authentication unavailable – issuer not
supporting 3D or technical problem in communication
between associations and Issuer 3D systems.
Transaction cannot continue.
V transakci není možné pokračovat, povoleno z důvodu
zabezpečení obchodníka před případnou reklamací
transakce držitelem karty.
24 / 25
3006
Zamítnuto v 3D. Technický problém při ověření držitele
karty.
Declined in 3D. Technical problem during Cardholder
authentication.
technický problém ověření obchodníka v 3D systémech,
anebo v komunikaci s 3D systémy finančních asociací, či
vydavatele karty.
Note: Technical problem during cardholder authentication –
merchant authentication failed or technical problem in
communication between association and acquirer.
V transakci není možné pokračovat.
3007
3008
Zamítnuto v 3D. Technický problém v systému zúčtující
banky. Kontaktujte obchodníka.
Declined in 3D. Acquirer technical problem. Contact
the merchant.
technický problém v 3D systémech.
Note: Technical problem during cardholder authentication –
3D systems technical problem.
Zamítnuto v 3D. Použit nepodporovaný karetní produkt.
Declined in 3D. Unsupported card product.
Info: Byla použita karta, která není v 3D systémech
podporována.
Note: Card not supported in 3D.
If PRCODE is 30, the following SRCODE may return
1001
Zamitnuto v autorizacnim centru, karta blokovana2
Zahrnuje důvody, které naznačují zneužití platební karty –
kradená karta, podezření na podvod, ztracená karta apod.
1002
Declined in AC, Card blocked
Většinou pokus o podvodnou transakci.
Includes the reasons implying that the card ha been
misused – a stolen card, suspected card fraud, a lost card,
etc.
Zamitnuto v autorizacnim centru, autorizace zamítnuta
Declined in AC, Declined
Z autorizace se vrátil důvod zamítnutí “Do not honor“.
1003
Vydavatel, nebo finanční asociace zamítla autorizaci BEZ
udání důvodu.
Reason:
Zamitnuto v autorizacnim centru, problem karty
Declined in AC, Card problem
Card Issuer or financial association rejected authorization
(Do Not Honor)
Zahrnuje důvody:
1004
expirovaná karta, chybné číslo karty, nastavení karty - pro
kartu není povoleno použití na internetu, nepovolená karta,
expirovaná karta, neplatná karta, neplatné číslo karty, částka
přesahuje maximální limit karty, neplatné CVC/CVV,
neplatná délka čísla karty, neplatná expirační doba, pro
kartu je požadována kontrola PIN.
Possible reasons:
Zamitnuto v autorizacnim centru, technicky problem
Declined in AC, Technical problem in authorization
process
Autorizaci není možné provést z technických důvodů –
technické problémy v systému vydavatele karty, nebo
finančních asociací a finančních procesorů.
Expired card, wrong card number, Internet transaction not
permitted to Cardholder, invalid card, invalid card number,
amount over card maximum limit, wrong CVC/CVV, invalid
card number length, invalid expiry date, PIN control is
required for used card
Authorization rejected – technical problem
Technical problem in card Issuer systems or financial
associations systems (Card Issuer unavailable)
1005
Zamitnuto v autorizacnim centru, Problem uctu
Důvody: nedostatek prostředků na účtu, překročeny limity,
překročen max. povolený počet použití…
Declined in AC, Account problem
Possible reasons: finance absence, over account limit, over
daily limit
2
Only the bold part in this and the following cells of this column will be included in the RESULTTEXT field (optional field) in a response
sent to the merchant. Other text is only the explanation for merchants.
25 / 25

GP webpay - system administration

Transkript

Podobné dokumenty

Časté dotazy - VISA Silver Business Cards FAQ - VISA