• Features
  • Shop
  • Pricing
  • User Guide
  • Support
 0 Kč
Login / Registration
  • CS
  • RO
  • DE
  • SK
  • HU
  • PL
  • EL
  • Features
  • Shop
  • Pricing
  • User Guide
  • Support
  • CS
  • RO
  • DE
  • SK
  • HU
  • PL
  • EL
BUY

Introduction

  • Before you begin
  • Receipt visual
  • Download
  • Legal Disclaimer
  • Integration support
  • Certification & Test Scenarios

app2app API

  • Introduction to app2app API
  • 1. Transaction registration
  • 2. Payment Request [transactionRequestV2]
  • 3. Get the status of the transaction
  • 4. Get transaction details
  • Code examples
  • Return codes
  • Check the installed application
  • Client ID
  • Settings in Android
  • Release notes
  • Get status method

Cloud API

  • Introduction to Cloud API
  • Transaction flow
  • Transaction sale
  • Transaction cancellation
  • Close batch
  • Master API account

iOS API

  • Transaction Sales (iOS)
  • Transaction Cancellation (iOS)
  • Day close execution (iOS)
  • Introduction to iOS API
View Categories
  • Main page
  • User Guide
  • API
  • API
  • Transaction Sales (iOS)

Transaction Sales (iOS)

A sales transaction is a basic payment operation that provides for the transfer of a specified amount from the cardholder's bank account to the merchant's account.

As for the payment process, the procedure is as follows:

Creating a transaction

The transaction can be initiated by calling:

gptom://transaction/create?…

where the following parameters are used to build the report:

Variable/Field
Format/Format
Description/Description
Example
amount
MANDATORY
long
CZ: Transaction amount with two decimal places.
EN: Transaction amount with two decimal places.
1000 (=10CZK/EURO)
Variable/Field
Format/Format
Description/Description
Example
clientID
String
Variable/Field
Format/Format
Description/Description
Example
originReferenceNum
String
CZ: Reference number up to 20 characters - suitable for invoice number, payment - can be used for your payment matching to sales or orders.
Reference number up to 20 characters - suitable for invoice number, payment - can be used for your matching of payments to sales or orders.
Variable/Field
Format/Format
Description/Description
Example
printByPaymentApp
bool
EN: Defines whether the receipt is passed to the client by your application or by GP tom. The default value is true (i.e. GP tom will offer the method of passing the receipt to the client). If you send a value of "false", we will return the user to your application immediately after the transaction and it is up to you to hand over the receipt.
Defines whether the receipt is passed to the client by your application or GP tom. The default value is true (i.e. GP will offer a way to pass the receipt to the client). If you send a value of "false", we return the user to your app immediately after the transaction and it's up to you to pass the receipt.
true/false
Variable/Field
Format/Format
Description/Description
Example
tipAmount
long
CZ: In restaurants, you can ask the customer to add a tip where the tip is entered from your system. This amount is then added to the original amount entered by the merchant.
EN: In restaurants, you can ask the customer to add a tip, where the tip is entered in your system. This amount is then added to the original amount entered by the merchant.
1000 (=10CZK/EURO)
Variable/Field
Format/Format
Description/Description
Example
redirectUrl
String
CZ: URL of your application to which we redirect the client after the payment is completed.
EN: The URL of your application to which we will redirect the client after completing the payment.
fb://success
Variable/Field
Format/Format
Description/Description
Example
TipCollect
bool
CZ: Optional field that brings up the tip entry screen in the GP tom application. After entering the tip in the app, the screen for attaching the card is then displayed. You must also have tipping enabled in the app to bring up this screen.
EN: An optional field that brings up the tip entry screen in the GP tom application. After entering the tip in the application, a screen for attaching the card will be displayed. You also need to have tipping enabled in the app to bring up this screen.
true / false
Variable/Field
Format/Format
Description/Description
Example
preferableReceiptType
enum (sms,email,qr,print)
CZ: In case of sending a receipt from the GP tom application, it is possible to predefine the method of sending the receipt via API . Possible values are:
EN: In the case of sending a receipt from the GP tom application, it is possible to predefine the method of sending the receipt via the API. Possible values are:
PHONE
EMAIL
QR
PRINT
text
Variable/Field
Format/Format
Description/Description
Example
clientPhone
String
CZ: Client's phone number.
EN: Client phone number.
+420606505404
Variable/Field
Format/Format
Description/Description
Example
clientEmail
String
CZ: Client's email address.
EN: Client email address.
info@gptom.com
Variable/Field
Format/Format
Description/Description
Example
transactionType
String
EN: Transaction type defines the type of transaction you want to initiate. Available values are:
EN:Transaction Type defines the type of transaction you want to initiate. Available values are:
CASH
CARD
CASH/CARD/ACCOUNT

Example call: 

gptom://transaction/create?originReferenceNum=12345&amount=2&clientID=123&tipCollect=true&preferableReceiptType=QR&redirectUrl=gp://transaction/create&printByPaymentApp=true&clientPhone=+420606505404&clientEmail=info@gptom.com&tipAmount=1

The answer will contain the following fields:

Field/Field
Format
Description/Description
Example/Example
TASK STATUS
EN: Gives information in which state has your request ended.
EN: Gives information in which state has your request ended.
COMPLETED
CANCELED
ERROR
Field/Field
Format
Description/Description
Example/Example
terminalID
CZ: ID of the terminal on which the transactions are processed. Identifies the terminal in GP systems.
EN: Unique terminal ID, on which the transaction is processed.
12345678
Field/Field
Format
Description/Description
Example/Example
amount
CZ: The amount determines the volume of the transaction. This amount is calculated in the domestic currency used by the terminal. For a closing, it includes all card transactions, credited minus debited.
EN: The amount determines the volume of the transaction. This amount is calculated in the domestic currency used by the terminal. At close day, it contains all card transactions, credited minus debit.
10
Field/Field
Format
Description/Description
Example/Example
batchNumber
CZ: Identifies the closing number. To be filled in if a deadline is requested.
EN: Defines batch number. Present during the close batch transaction.
1
Field/Field
Format
Description/Description
Example/Example
emvAppLabel
CZ: The name of the EMV that was used in the payment.
EN: Card label of used card
Visa Debit
Field/Field
Format
Description/Description
Example/Example
amsID
CZ: Unique transaction number.
EN: Unique transaction number.
Field/Field
Format
Description/Description
Example/Example
emvaid
CZ: Identifies the EMV application used to process the transaction.
EN: Identifies the EMV app used for transaction processing.
A0000000031010
Field/Field
Format
Description/Description
Example/Example
referenceNumber
CZ: Reference number entered when requesting payment.
EN: Reference number entered during the payment request
ABC123
Field/Field
Format
Description/Description
Example/Example
sequenceNumber
CZ: Used for cancellation transactions. Use the received value that was part of the transaction you want to cancel.
EN: Used for transaction cancellation. Used the received value which was a part of transaction you want to cancel.
001000000
Field/Field
Format
Description/Description
Example/Example
cardType
CZ: Identifies the type of card used.
EN: Identifies used card type.
VISA
MASTER
Field/Field
Format
Description/Description
Example/Example
transactionType
EN: Defines the transaction type.
EN: Defines type of transaction.
CARD
Field/Field
Format
Description/Description
Example/Example
date
CZ: Indicates the time of the transaction.
EN: Give date of transaction.
2024-10-29T12:14:00.112Z
Field/Field
Format
Description/Description
Example/Example
currencyCode
CZ: Three-digit ISO currency codes - see the Wiki page for a list.
EN: Three chars currency ISO code.
EUR
Field/Field
Format
Description/Description
Example/Example
merchantID
CZ: Unique merchant ID, usually location ID.
EN: Unique merchant ID, usually location ID
Field/Field
Format
Description/Description
Example/Example
tipAmount
CZ: Tips. Filled in if it has been entered.
EN: Tip. Filled in if needed.
2
Field/Field
Format
Description/Description
Example/Example
totalAmount
CZ: Indicates the total amount of transaction (including tip)
EN: Indicates the total amount of transaction (including tip)
12
Field/Field
Format
Description/Description
Example/Example
result
CZ: Response to request.
EN: Result to the request.
0 - approved transaction
-1 - declined transaction
Field/Field
Format
Description/Description
Example/Example
cardEntryMode
CZ: Identifies how the card data was entered, such as chip, contactless, magstripe, etc.
EN: Defines how the card was read: magstripe, chip or contactless.
CONTACTLESS
Field/Field
Format
Description/Description
Example/Example
transactionID
CZ: To be filled in only if the transaction ends up being approved.
EN: Is present just if the transaction is processed.
123456
Field/Field
Format
Description/Description
Example/Example
authorizationCode
CZ: Unique ID generated by the payment application during the transaction registration process.
EN: Unique ID generated by payment app during the transaction registration process.
001000000
Field/Field
Format
Description/Description
Example/Example
pinOk
true/false
Field/Field
Format
Description/Description
Example/Example
cardNumber
CZ: Card number (PAN). It is present in masked form.
EN: Card Number (PAN). It is present in masked form.
0001
Field/Field
Format
Description/Description
Example/Example
CODE
CZ: Displays the result of the transaction on authorization.
EN: Shows transaction result on the authorization side.
accepted
How do you like this tutorial?
Content
  • Creating a transaction

About the product

  • Features
  • Install the app
  • Releases
  • Support
  • Blog

For developers

  • Introduction to integration
  • app2app API
  • Cloud API
  • Integration according to the type of terminal
  • Integrated companies
  • Download

About the company

  • Contact
  • Information Protection Statement
  • Site Terms of Use
  • General Terms and Conditions
  • GDPR

User Guide

  • Install the app
  • Run the application for the first time
  • Payment by card
  • Cancellation of payment
  • Biometrics
  • In-app support