EP4200779A2 - Method for safe use of certified secure mobile payment acceptance application by third party applications - Google Patents

Method for safe use of certified secure mobile payment acceptance application by third party applications

Info

Publication number
EP4200779A2
EP4200779A2 EP21898839.2A EP21898839A EP4200779A2 EP 4200779 A2 EP4200779 A2 EP 4200779A2 EP 21898839 A EP21898839 A EP 21898839A EP 4200779 A2 EP4200779 A2 EP 4200779A2
Authority
EP
European Patent Office
Prior art keywords
application
payment
mobile payment
mobile
payment acceptance
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP21898839.2A
Other languages
German (de)
French (fr)
Other versions
EP4200779A4 (en
Inventor
Ibrahim Durak
Ahmet AKGÜN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Yazara Payment Solutions Inc
Original Assignee
Kartek Kart ve Bilisim Teknolojileri Ticaret AS
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Kartek Kart ve Bilisim Teknolojileri Ticaret AS filed Critical Kartek Kart ve Bilisim Teknolojileri Ticaret AS
Publication of EP4200779A2 publication Critical patent/EP4200779A2/en
Publication of EP4200779A4 publication Critical patent/EP4200779A4/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/606—Protecting data by securing the transmission between two devices or processes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/45—Structures or tools for the administration of authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/326—Payment applications installed on the mobile devices

Definitions

  • the present invention relates to a system and method which allows secure mobile payment acceptance application approved or certified by institutions that are in the position of rule-making in the field of payment systems to be used safely by any third party application (bank applications, merchant applications, etc.) so as to receive payments.
  • Payment acceptance applications generally consist of two components called user interface and SDK. Both components pass security assessment.
  • the payment acceptance application has these functions by being integrated with its SDK when third-party institutions desire to add payment acceptance functionality to their existing applications. However, in this case, they have to undergo a security assessment again.
  • Today there are no structures that enable the payment-acceptance application, whose security evaluation has been completed, to communicate with the existing applications of third-party institutions by talking over a secure channel. For this reason, there is a need for continuous improvement on the existing application and a security assessment process is initiated again. This causes both time and cost disadvantages.
  • the invention aims to solve the abovementioned disadvantages by being inspired from the current conditions.
  • the aim of the present invention is to provide a system and method which allows secure mobile payment acceptance application approved or certified by institutions that are in the position of rule-making in the field of payment systems to be used safely by any third party application (bank applications, merchant applications, etc.) so as to receive payments.
  • Figure 1 is a schematic view of the inventive system.
  • Figure 2 is a flow chart of the inventive method.
  • the present invention relates to a system (1) and a method (1000) that enables secure mobile payment acceptance application (3) approved or certified by the regulatory institutions in the field of payment systems, to be used safely by any third party application (4) (bank applications, merchant applications, etc.) so as to receive payments.
  • the payment for the shopping basket created through a third party application (4) of the merchant is securely transmitted to the mobile payment acceptance application (3).
  • the user does not have to leave the existing merchant third party application (4) during this transmission, does not perform a different operation.
  • the user does not have to add the functions of the mobile payment acceptance application (3) to the existing third party application (4).
  • the inventive system (1) and method (1000) have been developed in accordance with the regulations of the rule makers in the payment world; it prioritizes security during data exchange between the mobile payment acceptance application (3) and the third party application (4).
  • a secure communication channel (5) is established and data exchange is provided during data transmission to the mobile payment receiving application (3).
  • the inventive system (1) whose schematic representation is presented in Figure 1 comprises the following;
  • ⁇ secure mobile payment acceptance application (3) which is downloaded on the mobile device (2), is used to make contactless payments by bringing the bank card closer to the mobile device (2) using NFC technology and prepares the payment tags (tag) required for the authorization for the contactless payment transaction desired to be made,
  • ⁇ third party application (4) which is downloaded on the mobile device (2), belongs to a merchant, bank or any institution, generates data and sends the same to the mobile payment acceptance application (3), receives information from the mobile payment application (3), which is used for making the payment transaction through the mobile payment acceptance application (3) and whether the payment has been made or not by means of this sent data,
  • ⁇ back office unit (6) which manages the mobile payment acceptance application (3), Receiving the payment labels required for authorization in the contactless payment transaction made from the mobile payment acceptance application (3) and forwards the reply generated for the requested authorization request back to the mobile payment acceptance application (3),
  • ⁇ receiver unit (7) which operates for the completion of the operations regarding the authorization request, which belongs to the bank or institution that owns the secure payment application and reaches the back office unit (6) and
  • ⁇ approval unit (8) which is owned by the bank or institution that owns the payment card, performs the transactions regarding the authorization request received by the receiver unit (7) and creates an approval or rejection reply for this request, transmits the answer it has created to the receiver unit (6), thus allowing the replies to be delivered from the receiver unit (7) to the back office unit (6) and from the back office unit (6) to the mobile payment acceptance application (3).
  • the inventive method (1000) whose flow diagram is presented in Figure 2, uses the elements in the system (1), and it performs the following process steps with these elements;
  • first of all mobile payment acceptance application (3) and third party application (4) is downloaded and installed on the same mobile device (2).
  • the user does not perform any operation in the mobile payment acceptance application (3) either in secure payment.
  • Data is transmitted to the mobile payment acceptance application (3) by means of the third party application (4).
  • a shopping basket is created on the third party application (4).
  • a secure app2app communication channel (5) is created between the third party application (4) and the mobile payment acceptance application (3) using the messenger service.
  • Transaction amount, member workplace number, terminal number and activation code are transmitted to the mobile payment acceptance application (3) via the communication channel (5).
  • the user does not make any physical intervention to start the mobile payment acceptance application (3) during this process.
  • the mobile payment acceptance application (3) is triggered by the third party application (4) via the messenger service over the communication channel (5).
  • the mobile payment application (3) allows payment transactions after checking the merchant number, terminal number and activation code information received from the third party application (4) as a result of the data transmitted to it.
  • the interface of the mobile payment acceptance application (3) which allows the user to read the card contactless, is opened. The user is asked to make their card read to complete the transaction. The user reads his/her card to the mobile payment acceptance application (3).
  • Contactless EMV payment transaction is performed by the mobile payment acceptance application (3) and EMV payment tags required for authorization are prepared.
  • the transaction confirmation request is transmitted to the back office unit (6) of the mobile payment acceptance application (3).
  • the back office unit (6) transmits the authorization request message to the receiver unit (7).
  • the authorization request message received by the receiver unit (7) is transmitted to the approval unit (8) of the issuer bank.
  • the approval unit (8) controls the authorization message, generates the approval or rejection reply and transmits this reply to the receiver unit (7).
  • the reply message received by the receiving unit (7) is sent to the back office unit (6).
  • the back office unit (6) sends this response to the mobile payment acceptance application (3).
  • the mobile payment acceptance application (3) transmits the message regarding the completion of the transaction to the third party application (3) by means of the communication channel (5).

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

The present invention relates to a system (1) and method (1000) which allows secure mobile payment acceptance application approved or certified by institutions that are in the position of rule-making in the field of payment systems to be used safely by any third party application (bank applications, merchant applications, etc.) so as to receive payments. The inventive system (1) and method (1000) have been developed in accordance with the regulations of the rule makers in the payment world, it prioritizes security during data exchange between the mobile payment acceptance application (3) and the third party application (4). A secure communication channel (5) is established and data exchange is provided during data transmission to the mobile payment acceptance application (3).

Description

Method for safe use of Certified Secure Mobile Payment Acceptance Application by third party applications
Field of the Invention
The present invention relates to a system and method which allows secure mobile payment acceptance application approved or certified by institutions that are in the position of rule-making in the field of payment systems to be used safely by any third party application (bank applications, merchant applications, etc.) so as to receive payments.
State of the Art
Existing applications that perform payment processing are developed in accordance with the requirements provided by the rule makers however they are evaluated by independent laboratories in terms of security. Applications that fail the security assessment cannot be used in the field. These evaluations impose a great burden on institutions in terms of both time and cost.
Payment acceptance applications generally consist of two components called user interface and SDK. Both components pass security assessment. The payment acceptance application has these functions by being integrated with its SDK when third-party institutions desire to add payment acceptance functionality to their existing applications. However, in this case, they have to undergo a security assessment again. Today, there are no structures that enable the payment-acceptance application, whose security evaluation has been completed, to communicate with the existing applications of third-party institutions by talking over a secure channel. For this reason, there is a need for continuous improvement on the existing application and a security assessment process is initiated again. This causes both time and cost disadvantages.
In the patent application document numbered TR2017/11495 of the state of the art, a payment system is disclosed which enables an EMV transaction to be authorized between the user device and the point-of-sale terminal, in cases where the payment application installed on the user device is not made available, A structure that ensures that an approved or certified secure mobile payment application, can be used safely by any third party application to receive payments is not stated in the relevant document.
As a result, due to the abovementioned disadvantages and the insufficiency of the current solutions regarding the subject matter, a development is required to be made in the relevant technical field.
Aim of the Invention
The invention aims to solve the abovementioned disadvantages by being inspired from the current conditions.
The aim of the present invention is to provide a system and method which allows secure mobile payment acceptance application approved or certified by institutions that are in the position of rule-making in the field of payment systems to be used safely by any third party application (bank applications, merchant applications, etc.) so as to receive payments.
The structural and characteristic features of the present invention will be understood clearly by the following drawings and the detailed description made with reference to these drawings and therefore the evaluation shall be made by taking these figures and the detailed description into consideration.
Figures Clarifying the Invention
Figure 1 is a schematic view of the inventive system.
Figure 2 is a flow chart of the inventive method.
Description of the Part References
1 . System
2. Mobile device
3. Mobile payment acceptance application
4. Third party application
5. Communication Channel 6. Back office unit
7. Receiver unit
8. Approval unit
1000. Method
1001. Downloading and installing mobile payment acceptance application and third party application on the same mobile device
1002. Generating secure payment data via third party application
1003. Triggering the mobile payment acceptance application by transmitting the generated secure payment data to the mobile payment acceptance application via the communication channel
1004. Getting the mobile payment application ready to receive payments
1005. The mobile payment acceptance application starts the payment process and creates the payment labels required for authorization
1006. Transmitting the authorization request for the payment transaction from the mobile payment acceptance application to the back office unit
1007. Forwarding the authorization request from the back office unit to the receiving unit (acquirer bank host) for completion
1008. Forwarding the authorization request received by the receiving unit (acquirer bank host) to the approval unit (issuer bank) and delivering the reply from the approval unit (issuer bank) to the back office unit
1009. Transmitting the answer received by the back office unit to the mobile payment acceptance application.
1010. Notifying the third party application about whether the mobile payment application can make the payment according to the reply or not and the result of the payment transaction through the communication channel.
Detailed Description of the Invention In this detailed description, the preferred embodiments of the inventive system (1) and method (1000) is described by means of examples only for clarifying the subject matter.
The present invention relates to a system (1) and a method (1000) that enables secure mobile payment acceptance application (3) approved or certified by the regulatory institutions in the field of payment systems, to be used safely by any third party application (4) (bank applications, merchant applications, etc.) so as to receive payments.
For example, the payment for the shopping basket created through a third party application (4) of the merchant is securely transmitted to the mobile payment acceptance application (3). The user does not have to leave the existing merchant third party application (4) during this transmission, does not perform a different operation. At the same time, the user does not have to add the functions of the mobile payment acceptance application (3) to the existing third party application (4).
The inventive system (1) and method (1000) have been developed in accordance with the regulations of the rule makers in the payment world; it prioritizes security during data exchange between the mobile payment acceptance application (3) and the third party application (4). A secure communication channel (5) is established and data exchange is provided during data transmission to the mobile payment receiving application (3).
The inventive system (1) whose schematic representation is presented in Figure 1 comprises the following;
❖ tablet, mobile phone and similar mobile device (2) of the user,
❖ secure mobile payment acceptance application (3) which is downloaded on the mobile device (2), is used to make contactless payments by bringing the bank card closer to the mobile device (2) using NFC technology and prepares the payment tags (tag) required for the authorization for the contactless payment transaction desired to be made,
❖ third party application (4) which is downloaded on the mobile device (2), belongs to a merchant, bank or any institution, generates data and sends the same to the mobile payment acceptance application (3), receives information from the mobile payment application (3), which is used for making the payment transaction through the mobile payment acceptance application (3) and whether the payment has been made or not by means of this sent data,
❖ communication channel (5) that provides a secure data exchange between the mobile payment acceptance application (3) and the third party application (4),
❖ back office unit (6) which manages the mobile payment acceptance application (3), Receiving the payment labels required for authorization in the contactless payment transaction made from the mobile payment acceptance application (3) and forwards the reply generated for the requested authorization request back to the mobile payment acceptance application (3),
❖ receiver unit (7) which operates for the completion of the operations regarding the authorization request, which belongs to the bank or institution that owns the secure payment application and reaches the back office unit (6) and
❖ approval unit (8) which is owned by the bank or institution that owns the payment card, performs the transactions regarding the authorization request received by the receiver unit (7) and creates an approval or rejection reply for this request, transmits the answer it has created to the receiver unit (6), thus allowing the replies to be delivered from the receiver unit (7) to the back office unit (6) and from the back office unit (6) to the mobile payment acceptance application (3).
The inventive method (1000) whose flow diagram is presented in Figure 2, uses the elements in the system (1), and it performs the following process steps with these elements;
❖ downloading and installing mobile payment acceptance application (3) and third party application (4) on the same mobile device (2) (1001),
❖ generating secure payment data via third party application (4) (1002),
❖ triggering the mobile payment acceptance application (3) by transmitting the generated secure payment data to the mobile payment acceptance application (3) via the communication channel (5) (1003), ❖ getting the mobile payment acceptance application (3) ready to receive payments (1004),
❖ starting the payment process and creating the payment labels required for authorization by means of the mobile payment acceptance application (3) (1005),
❖ transmitting the authorization request for the payment transaction from the mobile payment acceptance application (3) to the back office unit (6) (1006),
❖ forwarding the authorization request from the back office unit (6) to the receiving unit (7) for completion (1007),
❖ forwarding the authorization request received by the receiving unit (7) to the approval unit (8) and delivering the reply from the approval unit (8) to the back office unit (6) (1008),
❖ transmitting the answer received by the back office unit (6) to the mobile payment acceptance application (3) (1009) and
❖ notifying the third party application about whether the mobile payment acceptance application (3) can make the payment according to the reply or not and the result of the payment transaction through the communication channel (5) (1010).
In the inventive system (1) and method (1000) first of all mobile payment acceptance application (3) and third party application (4) is downloaded and installed on the same mobile device (2). The user does not perform any operation in the mobile payment acceptance application (3) either in secure payment. Data is transmitted to the mobile payment acceptance application (3) by means of the third party application (4). For example, a shopping basket is created on the third party application (4). When the complete payment button is pressed in the shopping basket, a secure app2app communication channel (5) is created between the third party application (4) and the mobile payment acceptance application (3) using the messenger service. Transaction amount, member workplace number, terminal number and activation code are transmitted to the mobile payment acceptance application (3) via the communication channel (5). The user does not make any physical intervention to start the mobile payment acceptance application (3) during this process. The mobile payment acceptance application (3) is triggered by the third party application (4) via the messenger service over the communication channel (5). The mobile payment application (3) allows payment transactions after checking the merchant number, terminal number and activation code information received from the third party application (4) as a result of the data transmitted to it. The interface of the mobile payment acceptance application (3), which allows the user to read the card contactless, is opened. The user is asked to make their card read to complete the transaction. The user reads his/her card to the mobile payment acceptance application (3). Contactless EMV payment transaction is performed by the mobile payment acceptance application (3) and EMV payment tags required for authorization are prepared. The transaction confirmation request is transmitted to the back office unit (6) of the mobile payment acceptance application (3). The back office unit (6) transmits the authorization request message to the receiver unit (7). The authorization request message received by the receiver unit (7) is transmitted to the approval unit (8) of the issuer bank. The approval unit (8) controls the authorization message, generates the approval or rejection reply and transmits this reply to the receiver unit (7). The reply message received by the receiving unit (7) is sent to the back office unit (6). The back office unit (6) sends this response to the mobile payment acceptance application (3). The mobile payment acceptance application (3) transmits the message regarding the completion of the transaction to the third party application (3) by means of the communication channel (5).

Claims

1. A system (1) that enables secure mobile payment acceptance application (3) approved or certified by the regulatory institutions in the field of payment systems, to be used safely by any third party application (4) (bank applications, merchant applications, etc.) so as to receive payments, characterized by comprising; the following;
❖ tablet, mobile phone and similar a mobile device (2) of the user,
❖ secure mobile payment acceptance application (3) which is downloaded on the mobile device (2), is used to make contactless payments by bringing the bank closer to the mobile device (2) using NFC technology and prepares the payment tags (tag) required for the authorization for the contactless payment transaction desired to be made,
❖ third party application (4) which is downloaded on the mobile device (2), belongs to a merchant, bank or any institution, generates data and sends the same to the mobile payment acceptance application (3), receives information from the mobile payment application (3), which is used for making the payment transaction through the mobile payment acceptance application (3) and whether the payment has been made or not by means of this sent data,
❖ a communication channel (5) that provides a secure data exchange between the mobile payment acceptance application (3) and the third party application (4),
❖ a back office unit (6) which manages the mobile payment acceptance application (3), Receiving the payment tags required for authorization in the contactless payment transaction made from the mobile payment acceptance application (3) and forwards the reply generated for the requested authorization request back to the mobile payment acceptance application (3),
❖ a receiver unit (7) which operates for the completion of the operations regarding the authorization request, which belongs to the bank or institution that owns the secure payment application and reaches the back office unit (6) and ❖ an approval unit (8) which is owned by the bank or institution that owns the payment card, performs the transactions regarding the authorization request received by the receiver unit (7) and creates an approval or rejection reply for this request, transmits the answer it has created to the receiver unit (6), thus allowing the replies to be delivered from the receiver unit (7) to the back office unit (6) and from the back office unit (6) to the mobile payment acceptance application (3).
2. A method (1000) that enables secure mobile payment acceptance application (3) approved or certified by the regulatory institutions in the field of payment systems, to be used safely by any third party application (4) (bank applications, merchant applications, etc.) so as to receive payments, characterized by comprising; the following process steps;
❖ downloading and installing mobile payment acceptance application (3) and third party application (4) on the same mobile device (2) (1001),
❖ generating secure payment data via third party application (4) (1002),
❖ triggering the mobile payment acceptance application (3) by transmitting the generated secure payment data to the mobile payment acceptance application (3) via the communication channel (5) (1003),
❖ getting the mobile payment acceptance application (3) ready to receive payments (1004),
❖ starting the payment process and creating the payment tags required for authorization by means of the mobile payment acceptance application (3) (1005),
❖ transmitting the authorization request for the payment transaction from the mobile payment acceptance application (3) to the back office unit (6) (1006),
❖ forwarding the authorization request from the back office unit (6) to the receiving unit (7) for completion (1007),
❖ forwarding the authorization request received by the receiving unit (7) to the approval unit (8) and delivering the reply from the approval unit (8) to the back office unit (6) (1008), ❖ transmitting the answer received by the back office unit (6) to the mobile payment acceptance application (3) (1009) and
❖ notifying the third party application about whether the mobile payment acceptance application (3) can make the payment according to the reply or not and the result of the payment transaction through the communication channel (5) (1010).
EP21898839.2A 2020-11-26 2021-11-15 Method for safe use of certified secure mobile payment acceptance application by third party applications Pending EP4200779A4 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
TR2020/19057A TR202019057A2 (en) 2020-11-26 2020-11-26 A SYSTEM AND METHOD FOR SECURE PAYMENTS
PCT/TR2021/051210 WO2022115079A2 (en) 2020-11-26 2021-11-15 Method for safe use of certified secure mobile payment acceptance application by third party applications

Publications (2)

Publication Number Publication Date
EP4200779A2 true EP4200779A2 (en) 2023-06-28
EP4200779A4 EP4200779A4 (en) 2024-01-17

Family

ID=76373306

Family Applications (1)

Application Number Title Priority Date Filing Date
EP21898839.2A Pending EP4200779A4 (en) 2020-11-26 2021-11-15 Method for safe use of certified secure mobile payment acceptance application by third party applications

Country Status (3)

Country Link
EP (1) EP4200779A4 (en)
TR (1) TR202019057A2 (en)
WO (1) WO2022115079A2 (en)

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050108104A1 (en) * 2003-11-14 2005-05-19 Katherine Woo Integrating third party shopping cart applications with an online payment service
US20140317637A1 (en) * 2012-09-02 2014-10-23 Mpayme Ltd. Method and System for Conducting Mobile Application to Mobile Application Data Exchange
CN105556553B (en) * 2013-07-15 2020-10-16 维萨国际服务协会 Secure remote payment transaction processing
TWI703521B (en) * 2014-09-30 2020-09-01 美商蘋果公司 Recommendation of payment credential to be used based on merchant information
US10783517B2 (en) * 2016-12-30 2020-09-22 Square, Inc. Third-party access to secure hardware

Also Published As

Publication number Publication date
WO2022115079A2 (en) 2022-06-02
WO2022115079A3 (en) 2022-09-01
TR202019057A2 (en) 2021-03-22
EP4200779A4 (en) 2024-01-17

Similar Documents

Publication Publication Date Title
US11216803B2 (en) Authentication token for wallet based transactions
US9978059B2 (en) Systems, apparatus and methods for mobile companion prepaid card
KR101561428B1 (en) Contactless transaction
CN103778533B (en) System for performing payment on mobile terminal
CN103093340B (en) Based on dynamic payment system and the method for asynchronous communication technology
JP4711970B2 (en) Transaction device with expected pre-treatment
US20100317318A1 (en) Methods and apparatus for providing pre-paid payment capability on mobile telephone
JP2014021974A (en) Method for online payment, and system and electronic device for executing the same
US20210004806A1 (en) Transaction Device Management
KR20130132252A (en) Mobile card payment system using near field communication, mobile communication terminal having mobile card payment function and the method thereof
EP4200779A2 (en) Method for safe use of certified secure mobile payment acceptance application by third party applications
KR20180081702A (en) System and method for payment
EP3340139A1 (en) Amount confirmation for visually impaired users
RU2642360C1 (en) Method of initializing bank transactions without using pos-terminals and system for its implementation
WO2014074022A1 (en) Method for the secure use of bank cards (variants)
KR20010091827A (en) A remittance system via telecommunication terminal number and remittance method using the same
US20220374873A1 (en) Systems, Methods and Computer Program Products for Asynchronous Authentication of Digital Wallet Based Payment Transactions
KR20180018153A (en) System and method for payment
AU2013249994A1 (en) Method and system for conducting a money transfer and/or payment transaction
EP3474208A1 (en) System and method for performing transactions
KR20100103759A (en) System for providing card settlement using usim characteristics information
WO2014051469A1 (en) System for confirming a payment card holder's intention to carry out a payment
PH12013000006A1 (en) Mobile device attachment (pos device) for credit/debit card payment processing
KR20160129926A (en) Systemand method for providing settlement service

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20230320

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

A4 Supplementary search report drawn up and despatched

Effective date: 20231215

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 21/60 20130101ALI20231211BHEP

Ipc: G06F 21/45 20130101ALI20231211BHEP

Ipc: G06Q 20/38 20120101ALI20231211BHEP

Ipc: H04L 67/53 20220101ALI20231211BHEP

Ipc: G06Q 20/32 20120101AFI20231211BHEP

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: YAZARA PAYMENT SOLUTIONS INC.

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)