• Virtual POS

Virtual POS

Filtrele

Virtual POS Transactions General Concepts

Garanti Virtual POS is a secure payment solution created to receive credit card payments for online sales.

Merchants can open an online branch in their stores and turn it into a sales platform that never closes with Garanti Virtual POS. This contributes to increasing both the number of customers and turnover.

The following transactions are generally performed under Garanti Virtual POS:

  • Sales Transactions
  • Common Payment Page Operations
  • Cancellation Procedures
  • Refund Procedures
  • Closing Operations
  • Inquiry Procedures

In this document, the steps required for member merchants to be able to provide non 3Ds Sales transactions under Garanti Virtual POS, the operations to be performed within each step, and the structures of the transaction requests sent and response messages received are explained.

Virtual POS Sales Transactions

The sub transaction types under Virtual POS Sales transactions are generally as follows:

  • Installment Sales: It is the transaction type that enables installment transactions.
  • Pre-Authorization: Preauth - Preauthorization process ensures that the amount to be taken from the card is blocked between 7 and 9 days by blocking an amount on the card. In this way, it is guaranteed that the card will not receive a limit error when the authorization is closed. During this period, pre-authorization closing process must be performed in order for the amount to be recognized. At the end of the pre-authorization blocking period, the amount block on the card is removed. In the pre-authorization closing requests sent after the end of this period, the transaction result is returned according to whether the card has a limit or not.
  • Point Sale: It is the transaction type that allows you to make a purchase with bonus. Total transaction amount is sent in the Amount field. In UsedAmount field, the bonus rate to be used is sent. Debit is passed to the card side as much as amount - usedbonus amount. Used bonus is deducted from card bonuses. Bonus utilization is reflected in the workplace accounting the next day regardless of the workplace working conditions.
  • Repeat Sales: The sales transaction is realized at regular intervals and goes to provisioning.
  • DCC: DCC (dynamic currency conversion) is a system that ensures that the amount to be reflected on the card side in transactions made to foreign bank cards is made at the exchange rate of the card. In this system, the transaction amount is reflected to the merchant side in TL. The card side is reflected with the selected exchange rate. In this way, the cardholder clearly knows the amount to be reflected on the statement. For this transaction, the merchant and the bank side earn commission. Before the DCC transaction, DCC query is performed to obtain the supported exchange rates and exchange rate values. These values are reflected on the screen and the customer is asked to select one of the TL or incoming exchange rate values. The transaction is realized at the selected exchange rate.
  • Multi Currency: Transactions in foreign currencies other than Turkish lira.
  • Common Card: The Common Card is a card payment system that regulates the cash and document flow that occurs in the sales made by companies to their customers and allows term shopping.
  • Term Sale: Receipt of the sales price on a specified date.

3D Concept

3D Secure is a version of the application on VirtualPoS where cardholders are verified with a password on PoS. The cardholder is directed to the verification screens of the card bank to use a password in the transaction. The cardholder enters the information requested by his/her bank on these screens and shows that the card actually used is his/her own card.

After verification, the verification status is returned to the merchant bank (merchant). Then, depending on the status of the 3D information, the authorization process is carried out or the transaction is terminated.

3D Secure is supported by Master, Visa and American Express (Amex) cards. Merchants using 3D model (information about merchant models is given below) are required to come directly to provisioning without performing 3D verification for cards other than Mastercard, Visa and Amex. Since 3D secure is not supported, the responsibility for Fraud in such transactions belongs to the merchant. The merchant must take measures to protect itself.

Virtual POS Transactions Non 3ds

This is when the transaction is concluded without touching any 3D secure stage during the authorization flow. In this type of transaction, the customer's "I didn't do it" objections turn into a chargeback request. The chargeback process is evaluated by requesting evidence from the merchant that the transaction was made by the customer. In 3D transactions with successful verification, "I did not do it" claims are terminated by the bank.

Test / Prod Environment Selections:

For Virtual POS Sales transactions, it is possible to proceed with 2 different methods by the merchant. If the merchant wishes, they can make all the improvements in the test environment. Alternatively, necessary improvements can be made for these transactions directly in the broadcast environment.

According to the method to be selected by the merchant, before starting Virtual POS sales transactions, the first transactions must be made according to the appropriate one of the following headings:

If the work to be done is carried out in a test environment, the following predefined values can be used as they are:

Parameter Value
MerchantID 7000679
ProvUserID PROVAUT / PROVRFN / PROVOOS
ProvisionPassword 123qweASD/
TerminalID 30691297
StoreKey 12345678

In the studies to be carried out in the test environment "https://sanalposprovtest.garantibbva.com.tr/VPServlet" url will be used.

A panel where the operations performed in the test environment can be monitored and displayed at this address you can access.

Variable Value
Kullanıcı Adı 99999999999
Passcode Destek04
Password 147852

Not: In the event of an error in the password process, please try a second time before making a second attempt. Send Us a Question Please provide information with the form.

List of all test cards that can be used in the test environment from this page you can reach.

When proceeding with this method, the passwords to be used by the merchant in the setup as the first step are (“PROVAUT”,“PROVOOS”, “PROVRFN” ve “3D” (storekey) passwords) Virtual POS First Steps virtual POS management panel as specified in the document.

Passwords and accounts created in this way will be used in the next steps.

In the studies to be carried out in PROD environment "https://sanalposprov.garanti.com.tr/VPServlet" url will be used.

Hash Algorithm

This document explains step by step how to create the data required for the <HashData> tag in the request message, which is used under many transaction types.

The <HashData> tag in the request messages is the field that allows the password verification of the user. Hash creation details are explained separately below.

In the new VirtualPoS application, the HASH structure is used to prevent the password of the terminal from circulating openly.

Hash account:

1. SHA1 in the calculation of hashedpassword information

2. SHA512 algorithm is used to calculate the hashvalue.

In the hash calculation, a two-part HASH structure is used. In the first stage, the hashedpassword value will be obtained using the SHA1 algorithm by juxtaposing the provisioning password with the terminal number.

The operations required to generate hash are presented below for different programming languages:

public static string Sha1(string text) {\n var provider = CodePagesEncodingProvider.Instance;\n Encoding.RegisterProvider(provider);\n\n var cryptoServiceProvider = new SHA1CryptoServiceProvider();\n var inputbytes = cryptoServiceProvider.ComputeHash(Encoding.GetEncoding(\"ISO-8859-9\").GetBytes(text));\n\n var builder = new StringBuilder();\n for (int i = 0; i < inputbytes.Length; i++) {\n builder.Append(string.Format(\"{0,2:x}\", inputbytes[i]).Replace(\" \", \"0\"));\n }\n\n return builder.ToString().ToUpper();\n}\n\npublic static string Sha512(string text) {\n var provider = CodePagesEncodingProvider.Instance;\n Encoding.RegisterProvider(provider);\n\n var cryptoServiceProvider = new SHA512CryptoServiceProvider();\n var inputbytes = cryptoServiceProvider.ComputeHash(Encoding.GetEncoding(\"ISO-8859-9\").GetBytes(text));\n\n var builder = new StringBuilder();\n for (int i = 0; i < inputbytes.Length; i++) {\n builder.Append(string.Format(\"{0,2:x}\", inputbytes[i]).Replace(\" \", \"0\"));\n }\n\n return builder.ToString().ToUpper();\n}\n\npublic static string GetHashData(string userPassword, string terminalId, string orderId, string cardNumber, ulong amount, int currencyCode) {\n var hashedPassword = Sha1(userPassword + \"0\" + terminalId);\n return Sha512(orderId + terminalId + cardNumber + amount + currencyCode + hashedPassword).ToUpper();\n}
Public Shared Function Sha1(ByVal text As String) As String\n Dim provider = CodePagesEncodingProvider.Instance\n Encoding.RegisterProvider(provider)\n Dim cryptoServiceProvider = New SHA1CryptoServiceProvider()\n Dim inputbytes = cryptoServiceProvider.ComputeHash(Encoding.GetEncoding(\"ISO-8859-9\").GetBytes(text))\n Dim builder = New StringBuilder()\n\n For i As Integer = 0 To inputbytes.Length - 1\n builder.Append(String.Format(\"{0,2:x}\", inputbytes(i)).Replace(\" \", \"0\"))\n Next\n\n Return builder.ToString().ToUpper()\nEnd Function\n\nPublic Shared Function Sha512(ByVal text As String) As String\n Dim provider = CodePagesEncodingProvider.Instance\n Encoding.RegisterProvider(provider)\n Dim cryptoServiceProvider = New SHA512CryptoServiceProvider()\n Dim inputbytes = cryptoServiceProvider.ComputeHash(Encoding.GetEncoding(\"ISO-8859-9\").GetBytes(text))\n Dim builder = New StringBuilder()\n\n For i As Integer = 0 To inputbytes.Length - 1\n builder.Append(String.Format(\"{0,2:x}\", inputbytes(i)).Replace(\" \", \"0\"))\n Next\n\n Return builder.ToString().ToUpper()\nEnd Function\n\nPublic Shared Function GetHashData(ByVal userPassword As String, ByVal terminalId As String, ByVal orderId As String, ByVal cardNumber As String, ByVal amount As ULong, ByVal currencyCode As Integer) As String\n Dim hashedPassword = Sha1(userPassword & \"0\" & terminalId)\n Return Sha512(orderId & terminalId & cardNumber & amount & currencyCode & hashedPassword).ToUpper()\nEnd Function
public static String calculateHash(String data, String algorithm, String charset) throws UnsupportedEncodingException, NoSuchAlgorithmException {\n\tMessageDigest md = MessageDigest.getInstance(algorithm);\n\tbyte[] databytes = data.getBytes(charset);\n\t\n\tmd.update(databytes);\n byte[] hashBytes = md.digest();\n \n return byteArray2HexaDecimal(hashBytes);\n}\n\npublic static String sha1(String data) throws UnsupportedEncodingException, NoSuchAlgorithmException { \n return calculateHash(data, \"SHA-1\", \"ISO-8859-9\").toUpperCase();\n}\n\npublic static String sha512(String data) throws UnsupportedEncodingException, NoSuchAlgorithmException { \n return calculateHash(data, \"SHA-512\", \"ISO-8859-9\").toUpperCase();\n}\n\npublic static String getHashData(String userPassword, String terminalId, String orderId, String cardNumber, Long amount, int currencyCode) {\n var hashedPassword = sha1(userPassword + \"0\" + terminalId);\n return sha512(orderId + terminalId + cardNumber + amount + currencyCode + hashedPassword);\n}
private function GenerateSecurityData($terminalId)\n {\n $password = \"password\";\n\n $data = [\n $password,\n str_pad((int)$terminalId, 9, 0, STR_PAD_LEFT)\n ];\n\n $shaData = sha1(implode('', $data));\n\n return strtoupper($shaData);\n }\n\n public function GenerateHashData()\n {\n $orderId = \"order_id\"; //must be uniqe\n $terminalId = \"terminal_id\"; //must be integer\n $cardNumber = \"1234123412341234\"; //card number\n $amount = \"100\"; //amount\n $currencyCode = \"currency_code\"; //must be int\n\n $hashedPassword = GenerateSecurityData($terminalId);\n\n $data = [\n $orderId, $terminalId, $cardNumber, $amount, $currencyCode, $hashedPassword\n ];\n \n $shaData = strtoupper(hash(\"sha512\", implode('', $data)));\n\n return strtoupper($shaData);\n }

Request Structure

The request structure required for Variable Amount Repeat Sales transactions without Virtual POS 3D is specified in the table below. The information and explanations required for each tag under the main tag in the first column in the table should be examined and the request message should be provided according to the rules specified in this table:

<?xml version=\"1.0\" encoding=\"iso-8859-9\"?>\n<GVPSRequest>\n\t<Mode></Mode>\n\t<Version></Version>\n\t<Terminal>\n\t\t<ProvUserID></ProvUserID>\n\t\t<HashData></HashData>\n\t\t<UserID></UserID>\n\t\t<ID></ID>\n\t\t<MerchantID></MerchantID>\n\t</Terminal>\n\t<Customer>\n\t\t<IPAddress></IPAddress>\n\t\t<EmailAddress></EmailAddress>\n\t</Customer>\n\t<Card>\n\t\t<Number></Number>\n\t\t<ExpireDate></ExpireDate>\n\t\t<CVV2></CVV2>\n\t</Card>\n\t<Order>\n\t\t<OrderID></OrderID>\n\t\t<GroupID />\n\t\t<Recurring>\n\t\t\t<Type>R</Type>\n\t\t\t<TotalPaymentNum></TotalPaymentNum>\n\t\t\t<FrequencyType></FrequencyType>\n\t\t\t<FrequencyInterval></FrequencyInterval>\n\t\t\t<StartDate></StartDate>\n\t\t\t<PaymentList>\n\t\t\t\t<Payment>\n\t\t\t\t\t<Amount></Amount>\n\t\t\t\t\t<PaymentNum></PaymentNum>\n\t\t\t\t</Payment>\n\t\t\t\t<Payment>\n\t\t\t\t\t<Amount></Amount>\n\t\t\t\t\t<PaymentNum></PaymentNum>\n\t\t\t\t</Payment>\n\t\t\t</PaymentList>\n\t\t</Recurring>\n\t</Order>\n\t<Transaction>\n\t\t<Type></Type>\n\t\t<ListPageNum></ListPageNum>\n\t\t<Amount></Amount>\n\t\t<CurrencyCode></CurrencyCode>\n\t\t<CardholderPresentCode></CardholderPresentCode>\n\t\t<MotoInd></MotoInd>\n\t</Transaction>\n</GVPSRequest>

Within this structure, many tags contain sub-tags within themselves. Under the relevant heading where each tag is described, the usage rules of tags without subtags and the details of tags with subtags are presented in a separate heading.

Bottom Label Max Size Data Writing Format Description and notes
<Mode> PROD This is the field where the process mode is written
<Version> 16 byte No format requirement This is the field where the Api version used is written. Within the scope of hash calculation as Sha512, 512 value must be sent in this field.
<Terminal>  This tag contains sub tags. The tags it contains and their rules are given in the following headings.
<Customer>  This tag contains sub tags. The tags it contains and their rules are given in the following headings.
<Card>  This tag contains sub tags. The tags it contains and their rules are given in the following headings.
<Order>  This tag contains sub tags. The tags it contains and their rules are given in the following headings.
<Transaction>  This tag contains sub tags. The tags it contains and their rules are given in the following headings.

<Terminal> Tag and the Tag to be placed under it and its Details

Virtual such as virtual pos number user information to ensure pos verification parameters are sent.

<Terminal>\n\t<ProvUserID></ProvUserID>\n\t<HashData></HashData>\n\t<UserID></UserID>\n\t<ID></ID>\n\t<MerchantID></MerchantID>\n</Terminal>

The sub-tags within this tag and their details are given below:

Bottom Label Max Size Data Writing Format Description and notes
<ProvUserID> 32 byte No format requirement This is the field where the provision user code of the terminal is sent. Prov user, Cancel refund user or OOS user can be found here
<HashData>  32 byte Hash algorithm SHA512 format. After hash conversion, lower case letters must be converted to upper case. Details are given below. This is the field where the user's password verification is performed. Hash creation details are explained separately in this document.
<UserID> No format requirement This is the field where the user who made the transaction (Agent - Sales Representative) is sent.
<ID>  9 byte Nümerik The field where the terminal number is sent
<MerchatID>  9 byte Nümerik This is the field where the workplace number is sent.

<Customer> Tag and Rules for the <Customer> Tag and Tags Below it

This is the field where Customer Information is sent. It is mandatory to send the information in the tag.

<Customer>\n <IPAddress></IPAddress>\n <EmailAddress></EmailAddress>\n</Customer>
Bottom Label Max Size Data Writing Format Description and notes
<IPAdress> 20 byte No format requirement This is the field where the IP address of the customer who made the transaction is sent. It must be sent compulsorily in order to ensure fraud controls.
<EmailAddress> 64 byte This is the field where the E-Mail address of the customer who made the transaction is sent.

<Card> Label and Rules for the <Card> Label and the Label to be placed under it

This is the field where card information is sent. Credit card information is a mandatory field except for some transaction types.

Note: Unlike other credit cards, American Express cards consist of 15 digit numbers instead of 16, so your card information entry screens must be arranged to accept 15 digits. Unlike other credit cards, the CVV, i.e. security codes of American Express cards have 4 digits instead of 3 and are located on the front of the card. Your security code entry screens must be configured to accept 4-digit codes.

<Card>\n\t<Number></Number>\n\t<ExpireDate></ExpireDate>\n\t<CVV2></CVV2>\n</Card>
Bottom Label Max Size  Data Writing Format Data Writing Format Description and notes
<Number> Min: 15 - Max : 19 Nümeric This is the field where the card number is sent.
<ExpireDate> 4 byte MMYY (Last 2 digits of Month and Year) This is the field where the expiration date of the card is sent.
<CVV2> Min : 3 Max : 4 (Amex) Nümeric This is the field where CVV information of the card is sent.

<Order> Label and Rules for the <Order> Label

<Order>\n <OrderID></OrderID>\n <GroupID />\n <Recurring>\n <Type>R</Type>\n <TotalPaymentNum></TotalPaymentNum>\n\t <FrequencyType></FrequencyType>\n\t <FrequencyInterval></FrequencyInterval>\n\t <StartDate></StartDate>\n\t <PaymentList>\n\t <Payment>\n\t <Amount></Amount>\n\t <PaymentNum></PaymentNum>\n\t </Payment>\n\t <Payment>\n\t <Amount></Amount>\n\t <PaymentNum></PaymentNum>\n\t </Payment>\n </PaymentList>\n </Recurring>\n</Order>
Bottom Label Data Writing Format Description and notes
<OrderID> No format requirement. Maximum 36 bytes This is the field where the Order Number is sent. Order based must be unique. It must be produced by companies.
<GroupID> No format requirement. Maximum 36 bytes This field is used to categorize (group) orders. For example: Orders sent with campaigns can be separated with an information written to GroupID.
<Recurring> This tag contains sub tags within itself. Details are given in the headings below.

<Recurring> Tag and Details

This is the field where repetitive transaction information is sent. The label structure is as follows:

<Recurring>\n <Type></Type>\n <TotalPaymentNum></TotalPaymentNum>\n <FrequencyType></FrequencyType>\n <FrequencyInterval></FrequencyInterval>\n <StartDate></StartDate>\n <PaymentList>\n\t<Payment>\n\t <Amount></Amount>\n\t <PaymentNum></PaymentNum>\n\t</Payment>\n\t<Payment>\n\t <Amount></Amount>\n\t <PaymentNum></PaymentNum>\n\t</Payment>\n </PaymentList>\n</Recurring>
Bottom Label Max Size Data Writing Format Description and notes
<Type> 1 byte R This is the field where the repetitive transaction type is sent.
<TotalPaymentNum>  3 byte Alfanümerik This is the field where the repetition number is entered.
<FrequencyType> 1 byte D, W, M ve Y değerlerini alabilir.  This is the field where the repeat type is entered. D :daily W: weekly (weekly) M : Mountly (monthly) Y Yearly (yearly).
<FrequencyInterval> 3 byte Alfanümerik This is the field where the repetition frequency is entered. For example, if 2 is entered for type W, shooting will occur every 2 weeks.
<StartDate> 8 byte YYYYMMDD This is the field where the date on which the first fee will be charged is entered. This day is taken into account for repetitions.
<PaymentList> This tag contains sub tags. The tags it contains and their rules are given in the following headings.

<PaymentList> Tag and Details

This is the field where due dates and amounts are sent.

Bottom Label Description and notes
<Payment> This tag contains sub tags. The tags it contains and their rules are given in the following headings.

<Payment> Tag and Details

This is the field where due dates and amounts are sent.

Bottom Label Max Size Data Writing Format Description and notes
<PaymentNum>  3 byte Alphanumeric It is the field that shows how many recurrent payments. Starting from 1, it is increased one by one.
<Amount>  17,2 number The numeric is sent as LLLLLLKK. The last 2 digits represent cents. 1,00 TL -> 100 11,22 TL->1122 0,01TL -> 1 It is the field where the amount information is entered.

<Transaction> Tag and its Rules

This is the field where transaction information and financial information are sent.

<Transaction>\n <Type></Type>\n <ListPageNum></ListPageNum>\n <Amount></Amount>\n <CurrencyCode></CurrencyCode>\n <CardholderPresentCode></CardholderPresentCode>\n <MotoInd></MotoInd>\n</Transaction>\n
Bottom Label Maks Size Data Writing Format Description and notes
<Type> 32 byte Alfanümerik This is the field where the Transaction Type is sent. Details about transaction types will be given separately in the document. Attention should be paid to the use of other fields according to the transaction type.
<Amount> 17,2 number The numeric is sent as LLLLLLKK. The last 2 digits represent cents. 1,00 TL -> 100 11,22 TL->1122 0,01TL -> 1 This is the field where the amount information is entered. If the transaction is a "Partial Refund" transaction, the amount entered in this field is refunded.
<CurrencyCode>  3 byte Nümerik This is the field where exchange rate information is sent. 949 -> TL will be informed for other exchange rates according to your authorization.
<CardholderPresentCode>  2 byte Nümerik Enter 0 for normal transactions and 13 for 3D transactions.
<MotoInd> 1 byte Alfanümerik It takes Y and N values. N is sent for Ecommerce transactions. Y is sent for transactions with Moto transaction status.
<InstallmentCnt> 2 byte Nümerik Taksit sayısının girildiği alandır.

Response Structure

For Fixed Amount Repeat Sales transactions without Virtual POS 3D, the response structure returned from the service after the request sent in the previous topics is specified in the table below. The information and explanations required for each tag under the main tag in the first column in the table should be examined and the request message should be provided according to the rules specified in this table:

In the Virtual POS repeat sales transaction, the response structure is generally as follows:

<GVPSResponse>\n\t<Mode></Mode>\n\t<Terminal>\n\t\t<ProvUserID></ProvUserID>\n\t\t<UserID></UserID>\n\t\t<ID></ID>\n\t\t<MerchantID></MerchantID>\n\t</Terminal>\n\t<Customer>\n\t\t<IPAddress></IPAddress>\n\t\t<EmailAddress></EmailAddress>\n\t</Customer>\n\t<Order>\n\t\t<OrderID></OrderID>\n\t\t<GroupID></GroupID>\n\t</Order>\n\t<Transaction>\n\t\t<Response>\n\t\t\t<Source></Source>\n\t\t\t<Code></Code>\n\t\t\t<ReasonCode></ReasonCode>\n\t\t\t<Message></Message>\n\t\t\t<ErrorMsg></ErrorMsg>\n\t\t\t<SysErrMsg></SysErrMsg>\n\t\t</Response>\n\t\t<RetrefNum></RetrefNum>\n\t\t<AuthCode></AuthCode>\n\t\t<BatchNum></BatchNum>\n\t\t<SequenceNum></SequenceNum>\n\t\t<ProvDate></ProvDate>\n\t\t<CardNumberMasked></CardNumberMasked>\n\t\t<CardHolderName></CardHolderName>\n\t\t<CardType>BONUS</CardType>\n\t\t<HashData></HashData>\n\t\t<HostMsgList>\n\t\t\t<HostMsg></HostMsg>\n\t\t\t<HostMsg></HostMsg>\n\t\t</HostMsgList>\n\t\t<RewardInqResult>\n\t\t\t<RewardList></RewardList>\n\t\t\t<ChequeList></ChequeList>\n\t\t</RewardInqResult>\n\t\t<CampaignChooseLink></CampaignChooseLink>\n\t\t<GarantiCardInd>Y</GarantiCardInd>\n\t</Transaction>\n</GVPSResponse>

The tags in the answer structure given above and the sub tags under these tags are given in the heading below:

Bottom Labels Data Writing Format Description and notes
<Mode> PROD - TEST This is the field where the process mode is written
<Terminal> In order to provide virtual pos verification, parameters such as virtual pos number user information are sent. This tag contains sub tags within itself. The sub tags it contains are given in the following headings.
<Customer> It is the area where the information of the customer sent in the request structure is sent back for verification purposes. This tag contains sub tags within itself. The sub tags it contains are given in the following headings.
<Order> This is the area where the information and details of the order are sent. This tag contains sub tags within itself. The sub tags it contains are given in the following headings.
<Transaction>  This is the area where transaction and financial information is sent. This tag contains sub tags within itself. The sub tags it contains are given in the following headings.

<Terminal> Tag and the Tag to be placed under it and its Details

It is the field where the parameters sent in the request, such as virtual pos number user information, are returned in the response in the same way in order to provide virtual pos verification.

<Terminal>\n\t<ProvUserID></ProvUserID>\n\t<UserID></UserID>\n\t<ID></ID>\n\t<MerchantID></MerchantID>\n</Terminal>

The sub-tags within this tag and their details are given below:

Bottom Label Maks Size Data Writing Format Description and notes
<ProvUserID> 32 byte No format requirement This is the field where the provision user code of the terminal is sent. Prov user, Cancel refund user or OOS user can be found here
<UserID> No format requirement This is the field where the user who made the transaction (Agent - Sales Representative) is sent.
<ID>  9 byte Nümerik The field where the terminal number is sent
<MerchatID>  9 byte Nümerik This is the field where the workplace number is sent.

<Customer> Tag and Rules for the <Customer> Tag and Tags Below it

This is the field where the customer information sent in the request is returned in the same way in the response.

<Customer>\n\t<IPAddress></IPAddress>\n\t<EmailAddress></EmailAddress>\n</Customer>
Bottom Label Maks Size Data Writing Format Description and notes
<IPAdress> 20 byte No format requirement This is the field where the IP address of the customer who made the transaction is sent. It must be sent compulsorily in order to ensure fraud controls.
<EmailAddress> 64 byte This is the field where the E-Mail address of the customer who made the transaction is sent.

<Order> Tag Label and Rules for the <Order> Tag

This is the field where the order information sent in the request is returned in the same way in the response.

<Order>\n <OrderID></OrderID>\n <GroupID></GroupID>\n</Order>
Bottom Label Data Writing Format Description and notes
<OrderID> Alfanümerik This is the field where the order number is returned.
<GroupID> Alfanümerik The field where the GroupID number is returned. This tag contains sub tags. Details about the sub tags are given in the headings below.

<Transaction> Tag Label and Rules of the <Transaction> Tag

<Transaction>\n <Response></Response>\n <RetrefNum></RetrefNum>\n <AuthCode></AuthCode>\n <BatchNum></BatchNum>\n <SequenceNum></SequenceNum>\n <ProvDate></ProvDate>\n <CardNumberMasked></CardNumberMasked>\n <CardHolderName></CardHolderName>\n <CardType></CardType>\n <HashData></HashData>\n <HostMsgList></HostMsgList>\n <RewardInqResult></RewardInqResult>\n <CampaignChooseLink></CampaignChooseLink>\n <GarantiCardInd></GarantiCardInd>\n</Transaction>
Bottom Tags Data Writing Format Description and notes
<Response>  This tag contains sub tags. Details about the sub-tags are given in the headings below.
<RetrefNum> Nümerik The transaction number generated by Virtualpos is returned
<AuthCode>  Nümerik This is the field where the confirmation code is returned.
<BatchNum>  This is the field that returns which batche the transactions will enter.
 <SequenceNum>  This is the field where the name of the cardholder is sent.
<ProvDate>  YYYYMMDD This is the field where the provision date is returned.
<CardNumberMasked> This is the field where the first 6 and last 4 digits of the card number and the fields in between are returned with *.
<CardHolderName> This is the field where the name of the cardholder is sent.
<CardType>  This is the field where the type of card processed is returned.
<HashData> This is the field where the HashData information of the transaction is returned.
<HostMsgList>  This tag contains sub tags. Details about the sub-tags are given in the headings below.
<RewardInqResult>  This tag contains sub tags. Details about the sub-tags are given in the headings below.
<GarantiCardInd>
<CampaignChooseLink>

<Response> Alt Tags and Descriptions

<Response>\n <Source></Source>\n <Code></Code>\n <ReasonCode></ReasonCode>\n <Message></Message>\n <ErrorMsg></ErrorMsg>\n <SysErrMsg></SysErrMsg>\n</Response>
Alt Tags Description and notes
<Source> This is the field where the source information is returned.
<Code> This is the field where Approved - declined information is returned.
<ReasonCode> This is the field where the answer code is returned.
<Message>  This is the field where the message information is returned.
<ErrorMsg>  This is the field where the error message is returned.
<SysErrMsg> This is the field where the system error message is returned.

<HostMsgList> Tag, Subtags and Descriptions

<HostMsgList>\n <HostMsg></HostMsg>\n <HostMsg></HostMsg>\n</HostMsgList>
Bottom Labels Data Writing Format Description and notes
<HostMsg> This is the field where campaign messages are returned.

<RewardInqResult> Tag, Subtags and Descriptions

<RewardInqResult>\n<RewardList></RewardList>\n<ChequeList></ChequeList>\n</RewardInqResult>
Bottom Labels Data Writing Format Description and notes
<RewardList> This tag contains sub tags. Details about the sub-tags are given in the headings below.
<ChequeList> This tag contains sub tags. Details about the sub-tags are given in the headings below.

Code Examples

Below are github repo links to virtual POS Advance Sales transaction examples written in different software languages. You can review the codes written with predefined values via the link of your preferred programming language. 

Code Examples

Below are the github repo links for custom code examples written in different programming languages, including this transaction type. You can examine the codes written with predefined values through the link of your preferred programming language.

Error Codes

Error codes from this page you can reach.

Test Cards

List of test cards from this page you can reach.

Sales >> Fixed Amount Repeat Sales (3D) Sales >> Variable Amount Repeat Sales(3D)

We would love to hear from you. Do you have problems/questions about services ? Send us detailed email about it ?

Send Us a Question Send Us a Question