Sale request
An overview of the Sale request message for Android.
Overview
👉 The Sale request is used to prompt payment from the customer for a specific amount, including the desired tip amount. Once the customer has attempted or completed payment, a related transaction (either successful or unsuccessful) will be created.
This request allows for multimerchant functionality with the ISV schema. For multimerchant functionality without the ISV schema, please see Multimerchant Sale request
The client app must implement a mechanism to send messages using Android intents and URI calls and to receive the result in a custom URI callback.
- Sale request originating from the client app to initiate a request for a new Sale transaction.
- Sale response originating from the ‘Viva.com Terminal’ application to return the result of a Sale transaction.
Sale request
For a typical Sale request, the client app must provide the following information:
Field | Description | Example | Required | Card terminal support | Character limit | Type |
---|---|---|---|---|---|---|
scheme | The Viva custom URL scheme, the host and the version. | 'vivapayclient://pay/v1' | ✅ | |||
appId | The client app ID. For successful validation, should not be empty. | 'com.example.myapp' | ✅ | |||
action | Sale transaction. For successful validation, should not be empty. | 'sale' | ✅ | |||
clientTransactionId | A unique transaction ID transmitted to the host for storage with the transaction. Note that this value will be provided in the Merchant Reference field provided in the sales export response. | '12345678901234567890123456789012' | 2048 | String | ||
amount | Amount in cents without any decimal digits. This value must not be empty and must be an integer larger than zero. | '1200' = 12 euro | ✅ | 10 | integer (int32) | |
tipAmount | The tip that will be added on top of the amount. This must be less than or equal to the amount. | '200' = 2 euro | 10 | integer (int32) | ||
sourceCode | The store/source code that will be linked to the transaction.
|
[A payment source (physical store) that is associated with the transaction] How to create a payment source for CP payments |
20 | integer (int32) | ||
withInstallments | Enable card installments. Only in Greek Merchants | 'true' | Boolean | |||
preferredInstallments | Number of preferred card installments. Only in Greek Merchants. If the number is between the allowed range and the card supports installments then the flow complete without any prompt for installments. If the number is 0 or > max allowed number of installments then the user will be prompt to enter the number in the app. If the card does not support installments then the app will request from the user how to proceed with the flow. If withInstallments is true preferredInstallments must be integer and not empty. | '10' | Required if withInstallments is set | 2 | integer (int32) | |
callback | The URI callback that will handle the result. For successful validation, should not be empty. | 'mycallbackscheme://result' | ✅ | |||
show_receipt | A flag indicating if the receipt and transaction result will be shown. If true both transaction result and receipt will be shown. If false receipt will not be shown and result will be shown if show_transaction_result is true. | 'false' | ||||
show_transaction_result | A flag indicating whether transaction result will be shown. | 'true' | Boolean | |||
show_rating | A flag indicating if the rating flow will be shown. | 'true' | Boolean | |||
ISV_amount | The amount the ISV charges. Only for ISV Partners | '100' = 1€ | Required for ISV integration | 10 | integer (int32) | |
ISV_clientId | The ID of the ISV client. It is mandatory that if client ID is provided the ISV_amount and ISV_clientSecret parameters should be provided too. Only for ISV PartnersRefer to note below. |
kf7fpz4c4gkc6ch03u4415o8acipq9xdefzuto4b6by94.apps.vivapayments.com | Required for ISV integration | |||
ISV_clientSecret | The secret of the ISV client. Only for ISV PartnersRefer to note below. |
SY5Nt33019xdyagX85Ct6DQwpTiZhG | Required for ISV integration | |||
ISV_sourceCode | The source code of the ISV. Only for ISV PartnersRefer to note below. |
[A payment source (physical store) that is associated with a terminal] How to create a payment source for ISV |
4 | integer (int32) | ||
ISV_merchantId | Support for merchant switching via the inter-app while utilizing ISV feature. | 8d40824a-a5d3-4639-819c-6e8bddb99477 | Required for multimerchant integration | |||
ISV_currencyCode | Currency used for the given merchant when ISV is being used.You may find all the currency codes here. |
978 | Required for ISV integration | 3 | integer (int32) | |
ISV_merchantSourceCode | The source code of the merchant. | [A payment source (physical store) that is associated with a terminal] How to create a payment source for stores |
4 | integer (int32) | ||
ISV_customerTrns | The ISV transaction description for customer. | Description of items/services (up to 2048 characters). |
2048 | String | ||
ISV_clientTransactionId | A unique transaction ID transmitted to the host for storage with the transaction of the ISV. Note that this value will be provided in the Merchant Reference field provided in the sales export response. | 2600679 (up to 2048 characters). |
||||
paymentMethod | The payment method to be presented first to the user. The same time, the user is able to select another payment method |
Choose one of the following values:
|
||||
aadeProviderId [*] | 👉 Integration with Provider (ΥΠΑΗΕΣ) Set the Unique Number to identify your Provider 👉 Integration with ΦΗΜΑΣ (Φορολογικός Ηλεκτρονικός Μηχανισμός Ασφαλείας) For integration through ΦΗΜΑΣ, please specify as `aadeProviderId' the value 800 |
Integration with Provider (ΥΠΑΗΕΣ) 999 Integration with ΦΗΜΑΣ (Φορολογικός Ηλεκτρονικός Μηχανισμός Ασφαλείας) 800 |
3 | Numeric | ||
aadeProviderSignatureData [*] | 👉 Integration with Provider (ΥΠΑΗΕΣ) The unencrypted signature that includes the fields below with semicolon as a delimiter “;”: 👉 Integration with ΦΗΜΑΣ (Φορολογικός Ηλεκτρονικός Μηχανισμός Ασφαλείας) Use ECR TOKEN as in A.1098/2023 Request A/S< session number>/F< amount>:978:2 /D< datetime>/R< ecr-id>/H< operator-number>/T0 /M/Q< mac>} Result R/S< session number>/R< ecr-id>/T< receipt-number> /Μ/C00/D< trans-data>{/P< prn-data>}} |
Integration with Provider (ΥΠΑΗΕΣ) AD33729F4ED749928AAFA00B90EE4EA91551BAC1;;20231204080313;1051;10000;2400;12400;POS_1 |
200 | Alphanumeric | ||
aadeProviderSignature [*] | 👉 Integration with Provider (ΥΠΑΗΕΣ) The fields of providerSignatureFields encrypted using a public key and the Elliptic Curve Digital Signature Algorithm (ECDSA): 👉 Integration with ΦΗΜΑΣ (Φορολογικός Ηλεκτρονικός Μηχανισμός Ασφαλείας) Use SessionKey as in A.1098/2023 |
Integration with Provider (ΥΠΑΗΕΣ) o0094r3Yk3KTqASLkW3evlDsnIg/ZAdUUf6UCXDtjqpI/dquzAT4WNX3yzS/GLciVNbT75H4pj8hLOV0EpHtzw==" |
Alphanumeric | |||
protocol | The protocol used. | Always pass this value: int_default | Required for Paydroid devices |
[*] These parameters are only applicable in Greece
ISV parameter info:
- ISV_amount is only for ISV partners and is required for ISV integration. This value is set during an API call.
- ISV_clientId can be found under Settings > API access in the viva banking app
- ISV_clientSecret as above.
- ISV_sourceCode is the payment source for ISV set up under Sales > Physical Payments > Stores.
The above parameters must be used to create a URI call. Please see the below examples:
Intent payIntent = new Intent(Intent.ACTION_VIEW, Uri.parse(
"vivapayclient://pay/v1"
+ "?appId=com.example.myapp"
+ "&action=sale"
+ "&clientTransactionId=1234567801234"
+ "&amount=1200"
+ "&tipAmount=200"
+ "&show_receipt=true"
+ "&show_transaction_result=true"
+ "&show_rating=true"
+ "&ISV_amount=100"
+ "&ISV_clientId=kf7fpz4c4gkc6ch03u4415o8acipq9xdefzuto4b6by94.apps.vivapayments.com"
+ "&ISV_clientSecret=SY5Nt33019xdyagX85Ct6DQwpTiZhG"
+ "&ISV_sourceCode=Default"
+ "&ISV_currencyCode=978"
+ "&ISV_customerTrns=ItemDescription"
+ "&ISV_clientTransactionId=12345678901234567890123456789012"
+ "&ISV_merchantId=1234567890"
+ "&ISV_merchantSourceCode=9090"
+ "&paymentMethod=CardPresent"
+ "&callback=mycallbackscheme://result"));
payIntent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
payIntent.addFlags(Intent.FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS);
startActivity(payIntent);
Intent payIntent = new Intent(Intent.ACTION_VIEW, Uri.parse(
"vivapayclient://pay/v1"
+ "?appId=com.example.myapp"
+ "&action=sale"
+ "&clientTransactionId=1234567801234"
+ "&amount=1200"
+ "&tipAmount=200"
+ "&show_receipt=true"
+ "&show_transaction_result=true"
+ "&show_rating=true"
+ "&withInstallments=true"
+ "&preferredInstallments=10"
+ "&ISV_amount=100"
+ "&ISV_clientId=kf7fpz4c4gkc6ch03u4415o8acipq9xdefzuto4b6by94.apps.vivapayments.com"
+ "&ISV_clientSecret=SY5Nt33019xdyagX85Ct6DQwpTiZhG"
+ "&ISV_sourceCode=Default"
+ "&ISV_currencyCode=978"
+ "&ISV_customerTrns=ItemDescription"
+ "&ISV_clientTransactionId=12345678901234567890123456789012"
+ "&callback=mycallbackscheme://result"));
payIntent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
payIntent.addFlags(Intent.FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS);
startActivity(payIntent);
Intent payIntent = new Intent(Intent.ACTION_VIEW, Uri.parse(
"vivapayclient://pay/v1"
+ "?appId=com.example.myapp"
+ "&action=sale"
+ "&clientTransactionId=1234567801234"
+ "&amount=1200"
+ "&tipAmount=200"
+ "&show_receipt=true"
+ "&show_transaction_result=true"
+ "&show_rating=true"
+ "&aadeProviderId=999"
+ "&aadeProviderSignatureData=AD33729F4ED749928AAFA00B90EE4EA91551BAC1;;20231204080313;1051;10000;2400;12400;POS_1"
+ "&aadeProviderSignature=o0094r3Yk3KTqASLkW3evlDsnIg/ZAdUUf6UCXDtjqpI/dquzAT4WNX3yzS/GLciVNbT75H4pj8hLOV0EpHtzw=="
+ "&callback=mycallbackscheme://result"));
payIntent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
payIntent.addFlags(Intent.FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS);
startActivity(payIntent);
Intent payIntent = new Intent(Intent.ACTION_VIEW, Uri.parse(
"vivapayclient://pay/v1"
+ "?appId=com.example.myapp"
+ "&action=sale"
+ "&clientTransactionId=1234567801234"
+ "&amount=1200"
+ "&tipAmount=200"
+ "&show_receipt=true"
+ "&show_transaction_result=true"
+ "&show_rating=true"
+ "&withInstallments=true"
+ "&preferredInstallments=10"
+ "&callback=mycallbackscheme://result"));
payIntent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
payIntent.addFlags(Intent.FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS);
startActivity(payIntent);
Sale response
After executing a Sale transaction the ‘Viva.com Terminal’ application responds with a Sale response result to indicate if the transaction has been approved or not.
The result is received as a URI in the callback activity intent:
Uri result = getIntent().getData()`
The table below summarises the contents of an approved response.
Field | Description | Example | Card terminal support |
---|---|---|---|
callback | The URI callback that will handle the result. | 'mycallbackscheme://result' | |
status | The status of the transaction. | 'success' | |
message | A string containing information about the transaction status. | 'Transaction successful' | |
action | Sale transaction. | 'sale' | |
clientTransactionId | The client transaction ID. | '12345678901234567890123456789012' | |
amount | The amount in cents without any decimal digits. If action is cancel and amount is not empty must be integer and bigger than zero. (Used in successful and declined receipts) |
'1200' = 12 euro | |
tipAmount | How much of the amount in cents is considered as tip without any decimal digits. (Used in successful and declined receipts) |
'200' = 2 euro | |
verificationMethod | The verification method used. Possible values: CHIP, CONTACTLESS, MAGNETIC, MANUAL ENTRY |
'CHIP' | |
rrn | The Retrieval Reference Number of the transaction RRN. (Used in successful and declined receipts) |
'123456833121' | |
cardType | The card type. | 'VISA' | |
accountNumber | The card number masked. Note that only the 6 first and the 4 last digits are provided. All other digits are masked with stars. (Used in successful and declined receipts) |
'479275\*\*\*\*\*\*9999' | |
referenceNumber | A 6-digit number indicating the transaction's STAN number. | '833121' | |
authorisationCode | A 6-digit number indicating the transaction's Authorisation code provided by the host. | '690882' | |
tid | A 12 character string indicating the terminal's TID number. | ' 16016684' | |
orderCode | The order code. | ' 9256110059000200' | |
shortOrderCode | 10-digit integer. | '1234567890' | |
merchantApproved | This field is returned only if the terminal is in offline mode. It indicates that the transaction is completed in offline mode. (offline mode only) |
'true' | |
installments | Number of card installments. | ' 10' | |
transactionDate | The transaction date in ISO 8601 format. (Used in successful and declined receipts) |
'2019-09-13T12:14:19.8703452+03:00' | |
transactionId | A unique identifier for the transaction. | 'a78e045c-49c3-4743-9071-f1e0ed71810c' | |
paymentMethod | Payment method used for the payment. | 'CARD_PRESENT' | |
ISV_amount | The amount that the ISV charges. | '100' = 1€ | |
ISV_clientId | The ID of the ISV client. | 'qwerty123456' | |
ISV_clientSecret | The secret of the ISV client. | 'qwerty123456' | |
sourceCode | The source code attributed to the merchant and associated with the transaction. | '2412' | |
ISV_sourceCode | The reseller source code of the ISV. | 'qwerty123456' | |
aid | A string indicating the AID of the card. (Used in successful receipts) |
'A000000003101001' | |
vatNumber | The VAT number of merchant. (if print VAT is enabled in the 'Viva.com Terminal' application settings) (Used in successful and declined receipts) |
'123412341' | |
address | The address of merchant (if print address is enabled in the 'Viva.com Terminal' application settings) (Used in successful receipts) |
‘Main St 123, 12312 Anytown’ | |
businessDescription | Merchant’s Business/Trade/Store name (depending on what option is selected in the 'Viva.com Terminal' application settings), (Used in successful receipts) |
'Wonka Industries' | |
printLogoOnMerchantReceipt | A boolean indicating weather the VivaWallet logo should be printed on merchant receipt. (Used in successful receipts) |
'false' | |
merchantReceiptPAN | This field contains the value of the PAN (and additional clipping) that should be printed in merchant receipt. If is empty, then apply the default clipping. (Used in successful receipts) |
'629914XXXXXXXXX6770' | |
cardholderReceiptPAN | This field contains the value of the PAN (and additional clipping) that should be printed in customer receipt. If is empty, then apply the default clipping. | '629914XXXXXXXXX6770' | |
transactionReceiptAcquirerZone | If it is not empty then this value should be printed at the end of the customer receipt. (Used in successful receipts) |
'qwerty123456' | |
cardholderReceiptText | If is not empty then this value should be printed at the end of the customer receipt. (Used in successful receipts) |
'qwerty123456' | |
merchantReceiptText | If is not empty then this value should be printed at the end of the customer receipt. (Used in successful receipts) |
'qwerty123456' | |
cardholderName | Name of the cardholder. (Used in successful receipts) |
'JOHN DOE' | |
cardExpirationDate | Expiration date of the card (YYMM). (Used in successful receipts) |
'2212' | |
cardholderNameExpirationDateFlags | Each char may be 0 (false) or 1 (true) and indicates if the cardholder name and the expiration date should be printed on the merchant/cardholder receipts) 1st char: if 1 then the Cardholder Name should be printed in the merchant's receipt. If 0, then it should not. 2nd char: if 1 then the Cardholder Name should be printed in the cardholder's receipt. If 0, then it should not. 3rd char: if 1 then the Expiration Date should be printed in the merchant's receipt. If 0, then it should not. 4rd char: if 1 then the Expiration Date should be printed in the cardholder's receipt. If 0, then it should not. (Used in successful receipts) |
'1010' | |
needsSignature | A boolean indicating if the receipt needs a signature section. (Used in successful receipts) |
false | |
addQRCode | A boolean indicating if the order code should be printed as a QR. (Used in successful receipts) |
false | |
terminalSerialNumber | The serial number of the terminal. (Used in successful receipts) |
“1234567891“ | |
currency | The currency of the transaction. (Used in successful receipts) |
“EUR“ | |
errorText | Text to print on the receipt stating the error description and the error ccode. (Used in declined receipts) |
“Transaction failed - Z-3“ | |
applicationVersion | The version off the application. (Used in declined receipts) |
'v3.7.0(1956)' | |
oldBalance | The old balance of the cardholder. (Used in successful receipts) |
'200' = 2 euro | |
newBalance | The new balance of the cardholder. (Used in successful receipts) |
'200' = 2 euro | |
entryMode | Indicates the method used for PAN entry to initiate a transaction. You may find all the POS Entry Modes here. | '07' | |
loyaltyMerchant | Merchant id | ‘12345678901234567890123456789012’ | |
loyaltyTerminal | Terminal id | '12345678901234567890123456789012' | |
loyaltyPacketNo | Batch number | '12345678901234567890123456789012' | |
loyaltyTransactionNo | Sequence number | '12345678901234567890123456789012' | |
loyaltyPaymentAmount | Amount to be paid. Measured in cents. | '200' = 2 euro | |
loyaltyRedemptionAmount | Redeemed amount. Measured in cents. | '50 = '0.5 euro | |
loyaltyFinalAmount | The final amount after the calculation of (initial Amount - redemption amount). Measured in cents. | '100' = 1 euro | |
loyaltyPointsCollected | The points collected for the current transaction. Measured in points. | 500 | |
loyaltyPointsRedeemed | The points calculated for the selected amount to be redeemed. Measured in points. | 250 | |
loyaltyPointsPrevBalance | The previous balance of the customer’s points. Measured in points. | 750 | |
loyaltyPointsNewBalance | The new balance of the customer’s points. Measured in points. | 1000 | |
loyaltyExtraMessage | Extra messages sent by the loyalty provider | 'loyalty message' | |
loyaltyProgramId | The id which indicates the loyalty program for the current transaction. The mapping of values in this field is shown in the table ‘Loyalty Programs Enumeration’ below. Please note: Loyalty bonus schemes are supported in Greece only |
||
loyaltyLogoUrl | Url to get the loyalty’s logo | 'http://logo.com' | |
aadeTransactionId | An AADE-specific transaction ID. Format: Acquirer Unique code + RRN + Authorization code. Example: ‘116’ + ‘123456833121’ + ‘690882’ = '116123456833121690882' |
'116123456833121690882' |
Please see sample responses below for transactions made with the ‘Viva.com Terminal’ application for Android.
Parameters may vary for transactions made with Paydroid card terminals.
A sale response for an approved transaction looks as follows:
mycallbackscheme://result?aid=A0000000031010&status=success&message=Transaction successful&action=sale&clientTransactionId=1234567890&amount=146&tipAmount=23&rrn=121343565787&verificationMethod=CHIP&cardType=Debit Mastercard&accountNumber=515876******4490&referenceNumber=174010&authorisationCode=174010&tid=16109900&orderCode=3050112220001919
&transactionDat=e=2023-06-13T11:22:33.1234567+03:00&transactionId=a12e1ba8-6153-7754-a6a8-e3d2654872c8
&paymentMethod=CARD_PRESENT&shortOrderCode=3050112220&sourceCode=6532
A sale response for an offline mode transaction looks as follows. Please note, offline payment functionality is not supported within ISV integrations:
mycallbackscheme://result?aid=A0000000031010&status=success&message=Transaction successful&action=sale&clientTransactionId=1234567890&amount=146&tipAmount=23&verificationMethod=CONTACTLESS - NO CVM&cardType=Debit Mastercard&accountNumber=515876******4490&tid=16109900&orderCode=3050112220001919&transactionDate=2024-01-13T11:12:33.1234567+03:00&paymentMethod=CARD_PRESENT&merchantApproved=true&shortOrderCode=3050112220
A sale response for a failed transaction looks as follows:
mycallbackscheme://result?status=fail&message=(-12) TRANSACTION_DECLINED_BY_SERVER&action=sale&clientTransactionId=1234567801234&amount=101&tipAmount=0&verificationMethod=CHIP
&rrn=107715996469&cardType=Debit Mastercard&referenceNumber=996469&accountNumber=537488******9666&tid=16000223&orderCode=1077172696000223
&shortOrderCode=1077172696&transactionDate=2021-03-18T17:09:13.1917889+02:00&transactionId=3ca278e7-0679-411e-8279-ebb29ee519b2&sourceCode=6532
Note: transactions may fail for various reasons. Additionally, the structure of a failed message is the same as in the case of an approved transaction. Fields such as referenceNumber
and authorisationCode
may not have values since there is no STAN code available, nor an authorisation code.
A sale response for a successful sale transaction using AADE parameters looks as follows:
mycallbackscheme://result?aid=A0000000031010&status=success&message=Transaction successful&action=sale&clientTransactionId=1234567890&amount=146&tipAmount=23&rrn=121343565787&verificationMethod=CONTACTLESS - NO CVM&cardType=MASTERCARD&accountNumber=515876******4490&referenceNumber=174010&authorisationCode=174010&tid=16109900&orderCode=3050112220001919 &transactionDate=2024-02-13T11:22:33.1234567+03:00&transactionId=a12e1ba8-6153-7754-a6a8-e3d2654872c8 &paymentMethod=CARD_PRESENT&shortOrderCode=3050112220&aadeTransactionId=116407412859062859062&sourceCode=6532
You may find below the response samples per loyalty Greek schemes (Alpha Bank Loyalty, Eurobank €πιστροφή , NBG Go4More)
Alpha Bank Loyalty
mycallbackscheme://result?aid=A0000000031010&accountNumber=450903******9004&action=sale&amount=1000&authorisationCode=052583&cardType=VISA&clientTransactionId=&loyaltyFinalAmount=700
&loyaltyMerchant=0023127384&loyaltyPaymentAmount=1000&loyaltyProgramId=3&loyaltyRedemptionAmount=300&loyaltyTerminal=79504090&
message=Transaction successful&orderCode=3303152717031763&paymentMethod=CARD_PRESENT&referenceNumber=52583&rrn=330313052583&
shortOrderCode=3303152717&status=success&tid=16031763&tipAmount=&transactionDate=2023-10-30T15:40:58.8633674+02:00&
transactionId=d316ba3a-e3fb-4627-8140-936ffe17c003&verificationMethod=CONTACTLESS - NO CVM&sourceCode=6532
Eurobank
mycallbackscheme://result?aid=A0000000031010&accountNumber=516732******7639&action=sale&amount=1000&authorisationCode=052597&cardType=Debit Mastercard&clientTransactionId=&loyaltyFinalAmount=500&loyaltyLogoUrl=LogoURL&loyaltyMerchant=16720306118&loyaltyPaymentAmount=1000
&loyaltyProgramId=1&loyaltyRedemptionAmount=500&loyaltyTerminal=86031763&message=Transaction successful&orderCode=3303152721031763&paymentMethod=CARD_PRESENT&referenceNumber=52597&rrn=330313052597&shortOrderCode=3303152721
&status=success&tid=16031763&tipAmount=&transactionDate=2023-10-30T15:49:58.1147019+02:00&transactionId=804949db-01bc-43d5-a00b-8de245cb9e24&verificationMethod=CONTACTLESS - NO CVM&sourceCode=6532
NBG
mycallbackscheme://result?aid=A0000000031010&accountNumber=516297******2475&action=sale&amount=1000&authorisationCode=052613&cardType=MASTERCARD&
clientTransactionId=&loyaltyFinalAmount=0&loyaltyLogoUrl=LogoURL&loyaltyMerchant=1235311&loyaltyPacketNo=303&loyaltyPaymentAmount=1000&
loyaltyPointsCollected=0&loyaltyPointsNewBalance=24,000&loyaltyPointsPrevBalance=8,000&loyaltyPointsRedeemed=4,000&loyaltyProgramId=2&
loyaltyRedemptionAmount=1000&loyaltyTerminal=96031763&loyaltyTransactionNo=140001&message=Transaction successful&orderCode=3303162723031763&paymentMethod=CARD_PRESENT&referenceNumber=52613&rrn=330334052613&shortOrderCode=3303162723&
status=success&tid=16031763&tipAmount=&transactionDate=2023-10-30T16:00:17.8932712+02:00&transactionId=d2838e80-e870-4913-8f8f-5d8c16a705be&verificationMethod=CONTACTLESS - NO CVM&sourceCode=6532
Loyalty Programs Enumeration
Loyalty Program | Value |
---|---|
Eurobank επιστροφή | 1 |
NBG Go4more | 2 |
ALPHA Bonus | 3 |
Key to card terminal product categories
To understand the icons used on the above tables, see the below table.
Product category | Terminal models | Icon |
---|---|---|
Android Card Terminals | Android Card Terminal Ethernet, Android Card Terminal 4G, Mobile Card Terminal Plus, Mobile Card Terminal. | |
'Viva.com Terminal' application for Android | Mini Card Reader, Pocket Card Terminal connected via Bluetooth or USB to the 'Viva.com Terminal' application for Android. | |
Linux Card Terminals | Countertop, IM20, S900, S800, D200. |
Get Support
If you would like to integrate with Viva, or if you have any queries about our products and solutions, please see our Contact & Support page to see how we can help!