Payments through Virtualization of a Physical Point of Sale (POS) Terminal and Money Transfer Using Mobile Device

The invention relates to financial technology, mobile banking and mobile money transfer service industries. The current problem is that it is expensive to install credit/debit card readers at local stores. There is also the issue of risk of exposing card details to skimmers during POS transactions and during filling of forms in online transactions. The present invention simplifies the transaction and allows a user to pay for goods/services at a physical or online store without exposing their card details and without the merchant installing card reader. It also allows for a convenient global mobile-initiated bank to bank transfer of money. The invention may be used for money transfer between accounts that authenticate user's phone number or email addresses. The invention may also be used in the field of security technology to provide access to resources from a mobile device by use of pre-stored access credentials.

Not Applicable

BACKGROUND OF THE INVENTION

Regular physical Point of Sale (POS) terminals require a physical credit/debit card reader to read card information from a physical card. This has a huge costs implication to the merchants who also require their clients have with them; their credit/debit cards for the transaction to be processed, which pose a security risk (physical theft as well as credit card information theft using skimmers), susceptibility to loss, defacing through ‘wear and tear’ as well as issues simply forgetting to carry the card.

Explicit input of payment card details on online payment forms also creates a security problem as hackers may ‘sniff-out’ the card details for fraudulent re-use.

Regular mobile-based payment systems do not provide for convenient money transfer from card issuing bank account to a recipient/acquiring bank account through mobile devices. This results to high overhead costs and inconvenience while trying to move money from one account to a receiving account.

BRIEF SUMMARY OF THE INVENTION

The invention allows a merchant at a physical Point of Sale (POS) terminal to accept credit/debit/ATM card payments without having to physically swipe their client's credit/debit/ATM cards and without the need of installing a physical card reader/machine. The only ‘requirement’ being registration and linking of their business and account details (into which they will receive payments). An identifier such as a Merchant ID number is linked to their receiving bank account. This greatly reduces the cost, increases security as card details are not explicitly exposed and also reduces the excess baggage of having to always carry your debit/credit card which may be exposed to loss/defacement.

The invention also allows a payee to receive money from a payer who previously links their credit/debit (ATM) card information to their mobile device unique identifier (such as phone number) and authorizes transfer to a recipient unique identifier-linked account using a mobile device. The transfer is through an online gateway as directed by commands and input from the mobile device. The only ‘requirement’ being pre-registration and linking of the payee/recipient identifier to recipient account, without which, the server auto-generates a virtual currency worth that amount, such as virtual debit/credit card and automatically links it to the recipient identifier.

The invention may also be implemented in the computerized security field as a security/resource access feature that allows an authorized mobile device holder, access to pre-store their access credentials, which thereafter may be used to grant them remote access to a secured resource via mobile device.

DETAILED DESCRIPTION AND BEST MODE OF IMPLEMENTATION

FIG. 2shows how initially a payer may register with the system, this is one-time registration event where the user initiates the service32, adds and links38their payment instrument , such as credit/debit card information34, to their mobile device identifier38such as their phone number to the system. This added/linked information34may include the type of credit/debit card, card number, card expiry date and security code/CVV. This may be done from a mobile device using a user-specific communication protocol such as USSD/SMS/IP over a GPRS/GSM or IP-Based USSD and authentication via PIN and/or an authentication36, Call/SMS sent via a GPRS/GSM/IP network or through a Personal Identification Number (PIN)36. Optionally, the registration, adding and linking may be done automatically on generation of a virtual debit/credit card or directly at the card issuing bank. The registration/linking here means associating card information or account information to a mobile device identifier such as a device number, phone number or IMEI. This information is securely stored on a cloud server/database40for later use during actual payment. A notification42may be sent to the potential payer/sender indicating the registration status.

FIG. 1shows how initially a merchant may launch the service20and register with the system, this is ideally a one-time event that includes adding and linking of their recipient account details22to an assigned identifier such as merchant ID24. Registration may be done via the mobile device, through email request or directly by the virtualization service provider. The registration/linking26, here means associating the merchant/recipient's account information22, or receiving account information to a payee identifier24, such as a merchant number or phone number. This information may be securely stored on a cloud server/database28for later use during actual payment. A notification30may be sent to the payee indicating the registration status.

FIG. 3shows how a registered payer can make payments. The user may initiate payment by launching the service44. Authentication46, via PIN/Identifier or a combination may be done at this point or later depending on the security requirements. The payer then inputs the receiving entity's identifier48, such as the merchant ID/code or phone number. The system may check50for the identifier48, in the system database52, to ascertain recipient registration status54and if registered, it sets the receiving account as the account linked to the identifier48. If not available on the system database, the amount to be paid may be specified62, and a virtual card generated64, and auto-linked to the identifier48and notifications60, sent out to both payer/payee or sending and receiving parties about the transaction status. However, should the identifier48, be found in the system, the amount to be paid/sent56, may be input by the user on their mobile device and sent to the system for further processing.

At this point, we have all that is required to complete an online transaction through an online gateway58, depending on the availability of funds in the issuing account. We have the pre-stored/pre-linked card information that is linked and defined by the payer's identifier initiating/making the payment request, which includes the card type, card number, expiry and CVV code and the necessary authentication as shown inFIG. 2. This can be conceptually viewed or thought of, as shown inFIG. 4, as a pre-filled online check out form3. Pre-filled by the earlier linked card information from the payer's identifier-linked card information. This automatically executes action by the online payment gateway4, to transfer funds from the issuing bank account to the set merchant account5as defined and linked by the payee/recipient identifier6. Once the transaction is complete both the payer and payee2receive confirmation notifications on the status of the transaction on the mobile device1.

Preferably, during user authentication, native USSD should be used as GPRS/GSM inherently provides authentication/security as there can be only one unique phone number in the GPRS/GSM network. Optionally, IP-based USSD may be used together with an IMEI and/or GSM communication method such as phone call or SMS to validate authenticity of the session initiator. The latter being suitable for implementation through smart mobile device application.

The present invention may also be implemented on online payment platforms, where instead of having users expose their card details online when inputting them in a payment form, an identifier (such as a numerical merchant ID or QR merchant code) for the online merchant is assigned and displayed on the checkout form and the user pays using mobile device to the identifier.

The method may also be used for money transfer between social media and other online accounts (including email) that authenticate users using their mobile phone numbers. As the mobile phone numbers may have card information/account linked to them.

The present invention may also link an email account to the device identifier such as the phone number to allow money transfer and payments through payment gateways that authenticate users using their email addresses.

The invention may also be implemented in the computerized security field as a security/resource access feature that allows an authorized mobile device holder access to pre-store their access credentials, which thereafter may grant them remote access to a secured resource via mobile device.