KR20140133068A - Apparatus and method for providing remittance-based payment service - Google Patents

Apparatus and method for providing remittance-based payment service Download PDF

Info

Publication number
KR20140133068A
KR20140133068A KR20130052621A KR20130052621A KR20140133068A KR 20140133068 A KR20140133068 A KR 20140133068A KR 20130052621 A KR20130052621 A KR 20130052621A KR 20130052621 A KR20130052621 A KR 20130052621A KR 20140133068 A KR20140133068 A KR 20140133068A
Authority
KR
South Korea
Prior art keywords
payment
settlement
merchant
history
information
Prior art date
Application number
KR20130052621A
Other languages
Korean (ko)
Inventor
이상범
박영철
Original Assignee
주식회사 케이티
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 주식회사 케이티 filed Critical 주식회사 케이티
Priority to KR20130052621A priority Critical patent/KR20140133068A/en
Publication of KR20140133068A publication Critical patent/KR20140133068A/en

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/085Payment architectures involving remote charge determination or related payment systems
    • G06Q20/0855Payment architectures involving remote charge determination or related payment systems involving a third party
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/108Remote banking, e.g. home banking
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3223Realising banking transactions through M-devices

Abstract

The present invention relates to a remittance-based payment service apparatus and method, and more particularly, to an apparatus and method for performing settlement through remittance from a customer's account when a customer performs a mobile settlement using a mobile terminal.
The payment-based payment service apparatus according to the present invention includes a payment history DB for storing payment history information received from one or more banking systems, a settlement history DB for storing settlement history information received from the one or more banking systems, A payment request received from the mobile terminal, the payment request including a merchant code of a merchant requesting settlement, a payment amount and payment account information, to the bank system associated with the account information, A payment relay module for receiving information from the bank system and storing the received information in the payment history DB, and transmitting a payment completion message including at least a part of the payment history information to at least one of the merchant terminal and the mobile terminal of the merchant; The settlement history information received from the bank system is stored in the settlement history DB And a settlement relay module for transmitting a settlement request for each merchant based on the settlement history information of the settlement history DB to a representative merchant system (Payment Gateway).

Figure P1020130052621

Description

[0001] APPARATUS AND METHOD FOR PROVIDING REMITTANCE-BASED PAYMENT SERVICE [0002]

The present invention relates to a remittance-based payment service apparatus and method, and more particularly, to a remittance-based payment service apparatus and method for remittance from a customer's account when a customer makes a mobile settlement using a mobile terminal.

Recently, as the spread of smartphones has expanded, mobile payments have become active in online and offline shops using smartphones.

Most of the mobile payment systems currently in use are mostly credit card-based payment systems or postpaid payment systems, which are added to the communication charges of mobile communication companies.

However, in recent years, the financial authorities have been trying to curb the use of credit cards to reduce consumers' indiscriminate consumption. In order to consume the right amount of money within the scope of their own assets, need.

Although there are a few prepayment electronic money based micro settlement services (eg, KT's pocket service) through virtual account charging, as the bank managing the account clears the payment to the merchant according to the settlement period designated by the bank The payment service is dependent on the settlement policy of a particular bank.

In order for the remittance-based payment method to become more popular, both the customer and the merchant need a convenient and advantageous payment system.

SUMMARY OF THE INVENTION Accordingly, the present invention has been made to solve the above-mentioned problems occurring in the prior art, and it is an object of the present invention to provide a remittance-based payment service apparatus and method in which a payment process and a merchant settlement process are performed individually.

In addition, the present invention provides a remittance-based payment system, apparatus, and method that can reflect a settlement method of a settlement service provider rather than a settlement method of a bank by independently performing a settlement process and a merchant settlement process.

The present invention also provides a remittance-based payment system, an apparatus, and a method that allow a user to easily cancel a payment even after the settlement is performed.

According to one aspect of the present invention, a remittance-based payment service apparatus includes a settlement history DB for storing settlement history information received from one or more banking systems, settlement history information for storing settlement history information received from the one or more banking systems, DB and a settlement request received from the mobile terminal, the settlement request including a merchant code, a settlement amount and settlement account information of a merchant requesting settlement to a bank system associated with the account information, And transmits the settlement completion message including at least a part of the settlement history information to at least one of the merchant terminal of the merchant and the mobile terminal, Module, and the settlement history information received from the bank system, Store and includes a module for transmitting the clearing relay on behalf of the merchant system, the merchant by settlement request (Payment Gateway) based on the settlement history information of the settlement history DB.

A remittance-based payment service method according to one aspect of the present invention is a remittance-based payment service method performed in an apparatus for providing a payment service in cooperation with at least one bank system and a representative merchant point system, And a settlement history DB for storing settlement history information received from the bank system, the method comprising the steps of: receiving a settlement request from a mobile terminal; Receiving the payment request including the merchant code of the merchant, the payment amount, and the payment account information of the payment request; transmitting the received payment request to the bank system associated with the account information; Receiving from the system and storing in the payment history DB, The method comprising: transmitting a payment completion message including at least a part of the payment history information to at least one of the mobile terminals; requesting the banking system to periodically make a payment history information; A step of transmitting the settlement request to the representative merchant point system based on the settlement history information of the settlement history database to the representative merchant point system; And reflecting the received data in the settlement history DB.

According to the present invention, since the payment process and the settlement process for the merchant are independently performed, it is possible to reflect the settlement policy of the settlement service provider without being dependent on the settlement policy of the bank. Therefore, Based payment service.

In addition, according to the present invention, when a payment cancellation occurs, a settlement cancellation process can be divided into pre-payment and post-settlement of the merchant, thereby providing a simplified payment cancellation service to the user.

1 is a block diagram illustrating a configuration of a remittance-based payment service apparatus according to an embodiment of the present invention.
FIG. 2 illustrates a remittance-based payment process performed in the remittance-based payment service apparatus according to an embodiment of the present invention.
FIG. 3 illustrates a bank settlement process performed in the remittance-based payment service apparatus according to an embodiment of the present invention.
FIG. 4 illustrates a merchant information providing process performed in the remittance-based payment service apparatus according to an embodiment of the present invention.
FIG. 5 illustrates a settlement request process performed in the remittance-based payment service apparatus according to an embodiment of the present invention.
FIG. 6 illustrates a settlement process for each merchant performed in the remittance-based payment service apparatus according to an embodiment of the present invention.
FIG. 7 illustrates a pre-settlement cancellation process performed in the remittance-based payment service apparatus according to an embodiment of the present invention.
FIG. 8 illustrates a settlement cancellation process performed by the remittance-based payment service apparatus according to an embodiment of the present invention.
FIG. 9 illustrates a configuration of a remittance-based payment service system according to an embodiment of the present invention.
FIG. 10 illustrates a method of providing a remittance-based payment service according to an embodiment of the present invention.

While the present invention has been described in connection with certain exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, is intended to cover various modifications and similarities. It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

In addition, the singular phrases used in the present specification and claims should be interpreted generally to mean "one or more " unless otherwise stated.

Also, the terms "module,""part,"" interface ", and the like used in the present specification generally mean a computer-related object and may mean, for example, hardware, software and combinations thereof.

1 is a block diagram illustrating a configuration of a remittance-based payment service apparatus according to an embodiment of the present invention.

The remittance-based payment service apparatus according to an embodiment of the present invention can perform settlement in such a manner that a user transfers a settlement amount from his or her actual account or a virtual account at the time of purchasing a product or service online or offline through the merchant 1000 . To this end, the remittance-based payment service apparatus 1200 includes at least one banking system (e.g., 1300a, 1300b, 1300c) for managing a user's account and at least one representative merchant system , 1400a, 1400b, and 1400c to provide a remittance-based payment service. The representative merchant system 1400a, 1400b, 1400c has a PG account for receiving the amount of payment from the customer account, and each merchant (merchant A, B, ... Z) receives merchandise from the representative merchant And the remittance-based payment service apparatus 1200 may have a relay account for remitting the canceled payment amount to the customer account at the time of canceling the payment, and for remitting the payment amount at the representative merchant point at a later time.

Specifically, in one embodiment, the remittance-based payment service apparatus 1200 includes a payment history DB 1210, a settlement history DB 1220, a merchant information DB 1230, a payment relay module 1240, a settlement relay module 1250, an affiliate store information management module 1260, a PG interface 1270, and a bank interface 1280. It is to be understood, however, that these are merely illustrative and that it is fully understandable to those skilled in the art that some of these elements may be excluded or other elements may be added to the embodiments without departing from the scope of the present invention.

In one embodiment, the payment history DB 1210 stores payment history information received from the banking systems 1300a, 1300b, and 1300c. Although one payment history DB 1210 is shown in the drawing, the remittance-based payment service apparatus 1200 may include a payment history DB for each bank separately. In one embodiment, the payment history information received from the bank system may include at least one of a transaction number, a merchant code, a payment date, a payment amount, payment account information, a balance, and a reward.

The settlement history DB 1220 stores settlement history information received from the bank systems 1300a, 1300b, and 1300c. In this specification, the term 'settlement details' refers to the details of settlement of settlement amount through the account server 1350 of the banking system 1300. In one embodiment, the settlement particulars information received from the banking system may include at least one of a transaction number, settlement account information, a payment amount, a merchant code, a settlement date (remittance date), a settlement amount (remittance amount), and a bank fee. Here, the settlement amount may be an amount obtained by subtracting the bank fee from the settlement amount.

The merchant information DB 1230 may store information on the merchant subscribing to the remittance-based payment service. In one embodiment, the merchant information may include one or more of merchant code, merchant account information, commission rate, settling period and merchant terminal information (e.g., whether the merchant terminal has a billing app installed or a billing web service subscription, etc.) have. In one embodiment, the settling period can be set to daily, weekly, or monthly according to the merchant, which can be changed according to the policy of the remittance-based payment service provider. On the other hand, when there are a plurality of representative merchant systems, the merchant information DB 1230 may be provided for each representative merchant store to manage information of the merchant stores associated with the representative merchant store.

When the payment request is received from the mobile terminal 1100, the payment relay module 1240 delivers the payment request to the bank system 1300a, 1300b, or 1300c associated with the payment account, From the banking system 1300a, 1300b or 1300c and stores it in the payment history DB 1210 and transmits a payment completion message including at least a part of payment history information to at least one of the merchant 1000 and the mobile terminal 1100 Lt; / RTI >

In addition, the payment relay module 1240 can process payment cancellation when a payment cancellation request is received from the merchant. In one embodiment, the payment relay module 1240 sends a payment cancellation request to the banking system 1300 to cause it to delete the payment history in the payment history DB 1310 of the banking system 1300, The settlement history DB 1210 in the remittance-based payment service apparatus 1200 deletes the payment history to cancel the settlement. If the payment cancellation request is before the settlement, the payment cancellation can be completed through the above procedure. However, if the payment cancellation request has been settled from the customer account to the PG account of the representative merchant, need. If the payment cancellation request is received after the settlement, the payment relay module 1240 sends a settlement cancellation request to the bank system 1300 in the same manner as the settlement cancellation request before settlement, In addition to deleting the payment history in the payment history DB 1210 in the remittance-based payment service apparatus 1200, the banking system 1300 may send a remittance-based payment service to the remittance- The customer can be instructed to pay the settlement amount included in the canceled payment history from the relay account of the customer. The payment amount refunded from the relay account to the customer's payment account will be subsequently deposited in the PG account according to the instruction of the representative merchant system 1400.

In one embodiment, the settlement relay module 1250 may periodically request the banking system 1300a, 1300b, 1300c for the settlement detail information. In another embodiment, the settlement relay module 1250 may request the settlement detail information for each representative merchant when there are a plurality of representative merchant systems. The settlement relay module 1250 stores the settlement detail information received from the bank systems 1300a, 1300b, and 1300c in the settlement history DB 1220 in response to the settlement detail information request, 1400b, and 1400c to the representative merchant system 1400a, 1400b, and 1400c.

Meanwhile, the settlement relay module 1250 can receive the final settlement history corresponding to the merchant point settlement request from the representative merchant system 1400a, 1400b, 1400c, and update the related settlement history stored in the settlement history DB 1220 .

The merchant information management module 1260 is a module for managing information on the merchant subscribing to the remittance-based payment service, and can perform update, addition, deletion, and the like of the merchant information stored in the merchant information DB 1230. The merchant information management module 1260 transfers the information of the merchant information DB 1230 to the representative merchant (PG) system 1400 every time the information of the merchant information DB 1230 is changed through renewal, addition, deletion or the like such that the representative merchant system 1400a And / or 1400c.

The bank interface 1270 communicates with the plurality of bank systems 1300a, 1300b, and 1300c to exchange information between the remittance-based payment service apparatus 1200 and the bank system.

The PG interface 1280 can communicate with the representative merchant system 1400 to exchange information between the remittance-based payment service apparatus 1200 and the representative merchant point system

Hereinafter, with reference to FIG. 2 to FIG. 10, the processes performed by the remittance-based payment service apparatus shown in FIG. 1 to provide a remittance-based payment service in cooperation with the bank system and the representative merchant point system will be sequentially described.

A. Billing Process

In one embodiment, the payment process includes receiving, from a mobile terminal of the user, a payment request including payment information, to the bank system, receiving the payment response, and transmitting payment history information included in the payment response to the remittance-based payment service apparatus 1200 In the payment history DB 1310 of the banking system 1300 by storing them in the payment history DB 1210 of the banking system 1300.

Referring to FIG. 2, a remittance-based payment process according to an embodiment of the present invention will be described.

1. Receipt of payment information from the merchant terminal

When a user purchases goods or services from the online / offline merchant 1000 using a payment application installed in the mobile terminal 1100, payment information including the merchant code and payment amount is transmitted from the merchant terminal to the mobile terminal 1100 / RTI > The payment information may be provided through various methods such as QR code scan and NFC communication, and the present invention is not limited to a specific providing method.

2. Payment Request / 3. Payment Request / 4. Payment Request / 5. Payment request

Upon receiving the payment information from the merchant terminal, the mobile terminal 1100 transmits a payment request including the merchant code, payment amount, and payment account information of the user to the remittance-based payment service apparatus 1200.

The payment relay module 1240 of the remittance-based payment service apparatus 1200 delivers the payment request received from the mobile terminal 1100 to the bank system 1300 through the bank interface 1280. [

The large-area server 1330 in the banking system 1300 transfers the settlement request received from the remitting-based settlement service apparatus 1200 to the remitting-based settlement module 1340.

6. Creating and Saving Payment History

The remittance-based payment module 1340 generates payment history information corresponding to the payment request and stores the payment history information in the payment history DB 1310. In one embodiment, the payment history information may include at least one of a transaction number, a merchant code, a payment date, a payment amount, payment account information, balance, and a reward.

7. Payment Response / 8. Payment Response / 9. Payment Response

The remittance-based payment module 1340 transmits the settlement response including the settlement history information stored in the settlement history DB 1310 to the remittance-based settlement service apparatus 1200 via the extranet server 1330.

10. Sync payment history

The payment relay module 1240 stores the payment history information included in the payment response received through the bank interface 1290 in the payment history DB 1210 to thereby generate payment history DB 1210 in the remittance- And the settlement history DB 1310 in the bank system.

11. Payment Response

When the payment response is received via the bank interface 1290, the payment relay module 1240 generates a payment completion message including at least a part of the payment history information and transmits the payment completion message to the merchant terminal and / Lt; / RTI >

B. Bank settlement process

The bank settlement process is a process in which the banking system 1300 refers to the settlement record DB 1310 of its own and settles the amount of the settlement amount excluding the bank fee from the settlement account of the user included in the settlement record through the remittance method, , The settlement amount is transferred to the representative merchant account, not to each merchant account.

3, a bank settlement process according to an embodiment of the present invention will be described.

1. View your payment history

The remittance-based payment module 1340 of the banking system 1300 inquires payment details for each merchant in the payment history DB 1310. In one embodiment, the banking system 1300 may query the payment history for a predetermined period or merchant according to the settling period designated by the bank.

2. Creating and Saving Settlement Details

The remittance-based payment module 1340 generates a settlement breakdown based on the inquired settlement breakdown and stores it in the settlement breakdown DB 1320. In one embodiment, the settlement detail information may include at least one of a transaction number, settlement account information, payment amount, merchant code, representative merchant account information, settlement date (remittance date), settlement amount (remittance amount), and bank fee.

3. Request a Wire Transfer

The remittance-based payment module 1340 requests the account server 1350 to transfer the payment from the user's payment account to the account of the representative merchant based on the account details. According to an embodiment of the present invention, in the settlement amount remittance process, instead of remitting directly from the settlement account of the customer to the corresponding merchant account, the transaction is remitted to the representative merchant account, The provider can independently apply the settlement commission and the settlement period related to the settlement service to the bank and smoothly respond to the cancellation of the customer's settlement.

4. Remittance Processing

The account system server 1350 deducts the payment amount from the customer's settlement account and sends it to the representative merchant account.

5. Remittance Completed Response

The account system server 1350 informs the remittance-based payment module 1340 that the remittance has been completed.

C. Merchant Information Process

The representative merchant system 1400 should receive the merchant information from the remittance-based payment service device 1300 to deposit the payment amount to the merchants where the actual payment has been made. The merchant information providing process according to an embodiment of the present invention will be described with reference to FIG.

1. View merchant information

The merchant information management module 1270 of the remittance-based payment service apparatus 1200 inquires and extracts merchant information in the merchant information DB 1230. In one embodiment, the merchant information may include one or more of merchant code, merchant account information, commission rate, settling period and merchant terminal information (e.g., whether the merchant terminal has a billing app installed or a billing web service subscription, etc.) have. In one embodiment, the settlement period can be designated daily, weekly, or monthly according to the merchant, which can be changed according to the policy of the remittance-based payment service provider.

2. Merchant information delivery

The merchant information management module 1270 delivers the merchant information in the merchant information DB 1230 to the representative merchant system 1400 through the PG interface 1280. [

3. Store merchant information

The merchant information transmitted to the representative merchant system 1400 is stored in the merchant information DB 1430 of the representative merchant system 1400.

In one embodiment, when the merchant information is added, deleted and / or updated in the merchant information DB 1230 of the remittance-based payment service apparatus 1200, the merchant information management module 1270 stores the merchant information To the representative merchant point system 1400 so that the merchant point information DB between the remittance-based payment service apparatus 1200 and the representative merchant point system 1400 can be synchronized.

D. Settlement Request Process

The remittance-based payment service apparatus 1200 receives the settlement details from the bank, and transmits settlement details for each merchant to the representative merchant system 1400, thereby requesting settlement for each merchant. Referring to FIG. 5, a settlement request process according to an embodiment of the present invention will be described.

1. Request for settlement / 2. Request for settlement / 3. Request settlement history

The settlement relay module 1250 of the remittance-based payment service apparatus 1200 requests the settlement details made for a predetermined period to the large-scale server 1330 of the bank system 1300 through the bank interface 129, 1330 transmits the request to the remittance-based payment module 1340. [ In one embodiment, when there are a plurality of representative franchisees, the settling relay module 1250 can request a settled account for a predetermined period for each representative franchisee.

4. View settlement history

The remittance-based payment module 1340 inquires the settlement history DB 1320 of the banking system 1300 and calculates a settlement breakdown requested by the remittance-based settlement service device 1200.

5. Settlement record response / 6. Settlement breakdown response / 7. Settlement breakdown response

The remittance-based payment module 1340 transmits the calculated settlement details to the remittance-based payment service device 1200, and the remittance-based payment service device 1200 transmits the calculated settlement details to the remittance-based payment service device 1200 via the bank interface 1280 Lt; / RTI >

8. Saving Settlement Details

The settlement relay module 1250 stores the settlement details for each merchant in the settlement account DB 1220.

9. Request for settlement by merchant / 11. Request settlement by merchant

Then, the settling relay module 1250 inquires of the settlement details DB 1220 of the settlement details for each merchant, generates a settlement request for each merchant including the settlement details for each merchant via the PG interface 1270, Lt; / RTI > In one embodiment, the settlement relay module 1250 can generate a settlement request for each merchant according to a settling period determined for each merchant and transmit the settlement request to the representative merchant system 1400.

12. Save your payment history

The settlement module 1440 of the representative merchant system 1400 that received the settlement request per merchant store stores the settlement details per merchant included in the request in the payment history DB 1410 of the representative merchant system 1400.

E. Settlement Process by Merchant

The representative merchant system 1400 performs settlement for each merchant considering the settlement period and / or fee for each merchant. The settling cycle and fee for each merchant can be set according to the contract between the merchant and the representative merchant, or between the merchant and the merchant operating the remittance-based payment service device. Referring to FIG. 6, the process of setting up an affiliate shop according to an embodiment of the present invention will be described.

1. Extracting payment history

The settlement module 1440 of the representative merchant system 1400 extracts the settlement history from the settlement history DB 1410. At this time, the account details can be extracted to perform the settlement by the merchant at the determined merchant settlement cycle.

2. Create settlement history

The settlement module 1440 reflects the merchant commission in the settlement history extracted from the settlement history DB 1410 and stores it in the settlement history DB 1430.

3. Payment deposit request

The settlement module 1440 transmits a settlement amount deposit request to the account server 1350 of the bank system 1300 based on the settlement details stored in the settlement account DB 1430.

4. Settlement of deposits by merchant

The account system server 1350 deposits the settlement amount in the merchant account in response to the deposit request of the merchant settlement amount.

5. Request for settlement / 6. Request settlement history

The settlement relay module 1250 of the remittance-based payment service apparatus 1200 requests the representative merchant system 1400 for settlement details through the PG interface 1280. [ In one embodiment, the settlement relay module 1250 can request a settlement breakdown at a predetermined time each day.

7. Settlement record response / 8. Account settlement response

The settlement module 1440 extracts the settlement history stored in the settlement history DB 1430 and transmits it to the remittance-based settlement service apparatus 1200.

7. Reflecting final settlement history

The settlement relay module 1250 of the remittance-based payment service apparatus 1200 receives the settlement details from the representative merchant system 1400 and updates the corresponding settlement details in the settlement history DB 1220 to the final settlement details.

F. Payment Cancellation Process Before Settlement

The remittance-based payment service apparatus 1200 receives the payment cancellation request before the settlement, and transmits the settlement cancellation information to the bank system 1300 to perform the settlement cancellation process.

7, the settlement cancellation process before settlement according to an embodiment of the present invention will be described.

1. Request Cancellation of Merchant's Payment

The payment relay module 1240 of the remittance-based payment service apparatus 1200 receives a payment cancellation request from the merchant (710). In one embodiment, the payment cancellation request may include merchant code, payment amount, and customer payment account information.

2. Request to cancel payment before settlement / 3. Request to cancel payment before settlement / 4. Cancel payment before settlement

Upon receiving the payment cancellation request, the payment relay module 1240 determines whether the payment cancellation request is received before the settlement with the representative merchant system 1400. If the settlement amount is not transferred to the account of the representative merchant system at the time of canceling the payment, the payment history DB 1310 of the bank system 1300 and the payment history DB 1210 of the remittance-based payment service apparatus 1200, The payment can be canceled.

If it is determined that the payment history related to the payment cancellation request is before settlement, the payment relay module 1240 transmits a settlement cancellation request before settlement to the bank system 1300 through the bank interface 1290. [

5. Cancellation of payment in bank system (1300)

The remittance-based payment module 1340 of the bank system 1300 receiving the payment cancellation request processes the payment cancellation by deleting the payment history information corresponding to the payment cancellation request from the payment history DB 1310. [

6. Payment Cancellation Response / 7. Payment Cancellation Response / 8. Payment Cancellation Response

The remittance-based payment module 1340 of the bank system 1300 transmits a settlement cancellation response to the settlement cancellation module 1240 of the remittance-based settlement service apparatus 1200 via the extranet server 1330 after completing the settlement cancellation process do.

9. Payment clearing process of the remittance-based payment service apparatus 1200

Upon receiving the payment cancellation response from the banking system 1300, the payment relaying module 1240 deletes the payment history information from the payment history DB 1220. [ Accordingly, the payment history DB 1310 of the bank system 1300 and the payment history DB 1210 of the remittance-based payment service apparatus 1200 are synchronized.

10. Payment cancellation response

The payment relay module 1240 notifies the merchant that the payment cancellation has been completed.

G. Payment cancellation process after settlement

Hereinafter, a settlement cancellation process according to an embodiment of the present invention will be described with reference to FIG.

1. Request Cancellation of Merchant's Payment

The payment relay module 1240 of the remittance-based payment service apparatus 1200 receives a payment cancellation request from the merchant. In one embodiment, the payment cancellation request may include merchant code, payment amount, and customer payment account information.

2. Request payment cancellation after settlement / 3. Request payment cancellation after settlement / 4. Cancel payment after settlement

Upon receiving the payment cancellation request, the payment relay module 1240 determines whether the payment cancellation request is received before the settlement with the representative merchant system 1400. If the payment has already been transferred to the account of the representative merchant system at the time of cancellation of payment, it is necessary to process the refund of the payment amount to the customer account. Accordingly, when it is determined that the payment history related to the payment cancellation request is after the settlement, the payment relay module 1240 delivers the payment cancellation request after the settlement to the bank system 1300 through the bank interface 1290. [

5. Refund Processing

Upon receiving the payment cancellation request after settlement, the remittance-based payment module 1340 cancels the payment by re-depositing the payment amount from the relay account to the payment account of the customer. In one embodiment, the relay account is an account managed by a provider that provides a remittance-based payment service. According to the present invention, in order to provide an immediate payment cancellation to the customer, the refund processing is first performed on the customer account from the relay account of the payment service provider, and then the payment is transferred from the representative merchant account to the relay account do.

6. Payment Cancellation Response after Settlement / 7. Payment Cancellation Response After Settlement / 8. Payment cancellation response after settlement

The remittance-based payment module 1340 sends a cancellation response after settlement through the large-scale server 1330 of the banking system 1300 when the settlement cancellation is completed after the settlement, 1240 receive a cancellation response after settlement via the bank interface 1290. [

9. Payment Cancellation Processing / 10. Payment Cancellation Response

The payment relay module 1240 of the remittance-based payment service apparatus 1200 that has received the cancellation response after the settlement deletes the payment history from the payment history DB 1210 and informs the merchant that the payment cancellation is completed.

11. Transmit payment history / 12. Transmit payment history

The settlement relay module 1250 of the remittance-based payment service apparatus 1200 delivers the canceled (deleted) payment history to the representative merchant system 1400 through the PG interface 1270.

13. Save Cancellation History

The settlement module 1440 of the representative merchant system 1400 is connected to the settlement module 1440 through the PG interface 1270 of the remittance-based payment service apparatus 1200

Receives the canceled payment details, and reflects the canceled payment details in the account details DB 1420.

14. Cancellation amount after settlement

The settlement module 1440 of the representative merchant system 1400 requests the account server 1350 of the bank system 1300 to deposit the cancellation amount after the cancellation.

15. Payment Processing

The account system server 1350 deposits the canceled payment amount from the representative merchant account to the relay account of the remittance-based payment service provider.

16. Confirmation of settlement amount deposit processing

The account system server 1350 delivers the settlement amount deposit process confirmation contents to the representative merchant system 1400.

FIG. 9 illustrates a configuration of a remittance-based payment service system according to an embodiment of the present invention. As shown in the figure, the remittance-based payment service system according to an embodiment of the present invention includes, in addition to the remittance-based payment service apparatus 1200 described in FIGS. 1 to 8, And a payment app (web) server 1500 that receives and processes payment history display / payment cancellation requests through the mobile web.

In one embodiment, the payment app (web) server 1500 may include a payment history lookup module 1510 and a payment cancellation start module 1520.

The settlement history inquiry module 1510 inquires the payment history DB 1210 of the remittance-based payment service device 1200 in response to receiving a payment history inquiry request from the mobile terminal 1100, (1100).

The payment cancellation start module 1520 may transmit a payment cancellation request received from the mobile terminal 1100 to the merchant terminal and cause the merchant terminal to transmit a payment cancellation request to the remitting payment settlement service apparatus 1200. [ The payment cancellation start module 1520 can transmit a payment cancellation request in various ways according to whether the merchant terminal exists in the merchant's terminal. In one embodiment, when the merchant application exists in the merchant terminal, the payment cancellation start module 1520 may push the payment cancellation request to the merchant terminal using a push server. Upon receipt of the payment cancellation request to the merchant terminal, the merchant terminal will send a settlement cancellation request to the remittance-based payment service device 1200 after confirmation of the merchant's carrier. The settlement cancellation process in the remittance-based payment service apparatus 1200 has already been described with reference to FIGS. 7 and 8, and will not be described here.

In another embodiment, the payment cancellation start module 1520 may transmit an SMS / MMS based payment cancellation request to the merchant terminal through the SMS / MMS server when the merchant mobile web exists instead of the merchant application in the merchant terminal. Upon receipt of the payment cancellation request to the merchant terminal, the merchant terminal will send a settlement cancellation request to the remittance-based payment service device 1200 after confirmation of the merchant's carrier.

In yet another embodiment, the payment cancellation initiation module 1520 may forward a payment cancellation request to a merchant terminal via a hot key server or an ARS (Automatic Response Service) server. At this time, when the hotkey server or the ARS server receives the cancellation acknowledgment from the merchant terminal, it can directly send a settlement cancellation request to the remittance-based payment service apparatus 1200.

10 is a flowchart illustrating a remittance-based payment service method according to an embodiment of the present invention.

In one embodiment, the remittance-based payment service method is performed in an apparatus for providing a payment service in cooperation with one or more banking systems and a representative merchant point system, the apparatus comprising: a payment history DB for storing payment history information received from the bank system; And a settlement history DB that stores settlement history information also received from the banking system.

First, in step 1010, a payment request is received from the mobile terminal. In one embodiment, the payment request may include the merchant code, payment amount and payment account information of the merchant requesting payment.

At step 1020, the payment request is transmitted to the banking system associated with the payment account information. After receiving the payment request, the banking system generates and stores a payment history corresponding to the payment request in its payment history DB, and then transmits a payment response including the payment details generated. In one embodiment, the payment history information may include at least one of a transaction number, a merchant code, a payment date, a payment amount, a billing account number, a balance, and a reward.

In step 1030, the payment history information corresponding to the payment request is received from the bank system and stored in the payment history DB.

In step 1040, a payment completion message including at least a portion of the payment history information received in step 1130 is transmitted to at least one of the merchant and the mobile terminal.

In step 1050, the banking system periodically requests the settlement history information, and in response, stores the settlement history information received from the banking system in the settlement history DB.

The details of the settlement are the information that is generated as a result of settlement in accordance with the settlement details in the banking system, that is, the settlement amount excluding the bank commission from the settlement amount from the customer's settlement account to the representative merchant. The bank system performs settlement by transferring the settlement amount from the settlement account included in the settlement history information to the representative merchant account, and accordingly, at least one of the transaction number, settlement account information, payment amount, merchant code, settlement date, settlement amount, You can create a breakdown of the included accounting.

In step 1060, a settlement request for each merchant is transmitted to the representative merchant system based on the settlement history information of the settlement history DB. The representative merchant system receiving the settlement request by the merchant will generate the settlement details for each merchant based on the settlement period and fee for each merchant and request the bank system to transfer the settlement from the representative merchant account to the merchant account.

In step 1070, the final settlement history corresponding to the merchant point settlement request is received from the representative merchant system and reflected in the settlement history DB.

In one embodiment, when a payment cancellation request for payment details stored in the payment details DB is received, the payment cancellation request is transmitted to the bank system and the payment details are deleted from the payment history DB.

On the other hand, if the payment cancellation request is received after payment has been transferred to the representative merchant account, the payment system may request the bank system to transfer the payment from the relay account associated with the device to the payment account.

The remittance-based payment service method according to the embodiment of the present invention may be implemented in the form of a program command which can be executed through various computer means and recorded in a computer-readable medium. The computer readable medium may include program instructions, data files, data structures, and the like, alone or in combination.

Program instructions to be recorded on a computer-readable medium may be those specially designed and constructed for the present invention or may be available to those skilled in the computer software arts. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Includes hardware devices specifically configured to store and execute program instructions such as magneto-optical media and ROM, RAM, flash memory, and the like. The above-mentioned medium may also be a transmission medium such as a light or metal wire, wave guide, etc., including a carrier wave for transmitting a signal designating a program command, a data structure and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like.

The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

The embodiments of the present invention have been described above. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. Therefore, the disclosed embodiments should be considered in an illustrative rather than a restrictive sense. The scope of the present invention is defined by the appended claims rather than by the foregoing description, and all differences within the scope of equivalents thereof should be construed as being included in the present invention.

Claims (15)

A payment history DB for storing payment history information received from one or more bank systems,
A settlement history DB for storing settlement history information received from the one or more banking systems,
A payment request received from the mobile terminal, the payment request including a merchant code of a merchant requesting settlement, a payment amount and payment account information, to the bank system associated with the account information, A payment relay module for receiving information from the bank system and storing the received information in the payment history DB, and transmitting a payment completion message including at least a part of the payment history information to at least one of the merchant terminal and the mobile terminal of the merchant;
A settlement relay module that stores settlement detail information received from the bank system in the settlement history DB and transmits a settlement request by a merchant based on settlement details of the settlement history DB to a representative merchant system
Based payment service apparatus.
A bank interface for communicating with each of the one or more banking systems, and
A PG interface for communicating with the representative merchant system
Based payment service apparatus.
The settlement system according to claim 1, wherein the payment history information received from the bank system includes at least one of a transaction number, a merchant code, a payment date, a payment amount, payment account information, balance, and a reward. The bank system according to claim 1, wherein the bank system transfers the settlement amount from the settlement account included in the settlement record to the representative merchant account based on the settlement history information, and the settlement detail information includes information on the transaction number, A payment amount, a merchant code, a settlement date, a settlement amount, and a bank fee. The remittance-based payment service apparatus according to claim 1, wherein the settlement relaying module periodically requests settlement detail information to the banking system and stores the settlement detail information in the settlement history DB. The system according to claim 1, wherein the representative merchant system receiving the request for settlement by merchant point generates a settlement breakdown for each merchant based on the settlement period and commission for each merchant, and requests the bank system to send the settlement amount from the representative merchant bank account to the merchant account Based payment service apparatus. The remittance-based payment service apparatus according to claim 1, wherein the settling relay module receives final settlement details information corresponding to the merchant point-based settlement request from the representative merchant point system and reflects the information on the settlement history DB. The payment relay system of claim 1, wherein when the payment cancellation request for the payment details stored in the payment history DB is received, the payment relay module transmits the payment cancellation request to the bank system and deletes the payment history from the payment history DB Remittance - based payment service device. The settlement system according to claim 8, wherein when the settlement cancellation request is received after the settlement amount is transferred to the representative merchant account, the settlement relay module transmits the settlement amount from the relay account associated with the remittance-based settlement service apparatus to the settlement account A remittance-based payment service device requesting to the banking system. The remittance-based payment service apparatus according to claim 1, further comprising: an affiliated store information DB storing merchant store information including at least one of merchant code, merchant account information, fee policy, settlement period, and merchant terminal information, And the information is also stored in the representative merchant system. A payment-based payment service method performed in an apparatus for providing a payment service in cooperation with one or more banking systems and a representative merchant point system, the apparatus comprising: a payment history DB for storing payment history information received from the bank system; And a settlement history DB for storing settlement history information received from the bank system,
A payment request from a mobile terminal, the payment request including a merchant code of a merchant requesting settlement, a payment amount and payment account information;
Sending the received payment request to a banking system associated with the account information;
Receiving the payment history information corresponding to the payment request from the bank system and storing the received payment history information in the payment history DB;
Transmitting a payment completion message including at least a part of the payment history information to at least one of the merchant and the mobile terminal;
Requesting the banking system periodically for settlement detail information and storing the settlement detail information received from the banking system in the settlement history DB,
Transmitting to the representative merchant system a settlement request for each merchant based on the settlement history information of the settlement history DB;
Receiving the final settlement history corresponding to the merchant point settlement request from the representative merchant system and reflecting the final settlement history in the settlement history DB
Based payment service method.
The method according to claim 11, wherein the payment history information received from the bank system includes at least one of a transaction number, a merchant code, a payment date, a payment amount, payment account information, balance, and a reward. 12. The settlement service method according to claim 11, wherein the settlement detail information received from the bank system includes at least one of a transaction number, settlement account information, settlement amount, merchant code, settlement date, settlement amount, and bank fee. 12. The method as claimed in claim 11, further comprising the step of transferring the payment cancellation request to the banking system and deleting the payment history from the payment history DB when a payment cancellation request for payment details stored in the payment history DB is received Based payment service method. 15. The method of claim 14, further comprising: requesting the bank system to remit payment from the relay account associated with the device to the payment account if the payment cancellation request is received after the payment has been transferred to the representative merchant account Based payment service method.
KR20130052621A 2013-05-09 2013-05-09 Apparatus and method for providing remittance-based payment service KR20140133068A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR20130052621A KR20140133068A (en) 2013-05-09 2013-05-09 Apparatus and method for providing remittance-based payment service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR20130052621A KR20140133068A (en) 2013-05-09 2013-05-09 Apparatus and method for providing remittance-based payment service

Publications (1)

Publication Number Publication Date
KR20140133068A true KR20140133068A (en) 2014-11-19

Family

ID=52453825

Family Applications (1)

Application Number Title Priority Date Filing Date
KR20130052621A KR20140133068A (en) 2013-05-09 2013-05-09 Apparatus and method for providing remittance-based payment service

Country Status (1)

Country Link
KR (1) KR20140133068A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101635469B1 (en) * 2015-09-16 2016-07-08 (주)핀테크솔루션 System, apparatus and method for providing service of remittances payment
WO2019004786A1 (en) * 2017-06-30 2019-01-03 주식회사 하렉스인포텍 System for providing account-based payment and settlement service

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101635469B1 (en) * 2015-09-16 2016-07-08 (주)핀테크솔루션 System, apparatus and method for providing service of remittances payment
WO2017090966A1 (en) * 2015-09-16 2017-06-01 김의준 Remittance payment service providing system, device, and method
WO2019004786A1 (en) * 2017-06-30 2019-01-03 주식회사 하렉스인포텍 System for providing account-based payment and settlement service

Similar Documents

Publication Publication Date Title
KR101652840B1 (en) Information processing server, information processing method, recording medium containing information processing program, handheld terminal, information processing method using handheld computer, and recording medium containing handheld-computer program
US20120330744A1 (en) Real-Time Multi-Merchant Multi-Payer Multi-Bucket Open Loop Debit Card, Credit Card or Mobile Payment Device Value Tracking and Discount Processing Systems and Related Methods
CN102257524A (en) Systems, methods, and computer readable media for payment and non-payment virtual card transfer between mobile devices
KR101404719B1 (en) System for international prepaid card payment using national bank identification number
KR101729162B1 (en) Apparatus, method and computer program for managing advanced payment based on financial open platform
KR20070026939A (en) System and method of the integrated payment for milage points, electronic cash, electronic gift-certificates, pre-paid cards, debit cards and other credit cards by using one card number
KR102166931B1 (en) Method of managing card sales data of affiliate store using electronic device and electronic device thereof
KR20140133068A (en) Apparatus and method for providing remittance-based payment service
CN109003163A (en) A kind of store method for running and system
KR101258831B1 (en) Method for providing deferred type payment using prepaid type moile card
KR101709438B1 (en) Method for providing deferred type payment using prepaid type moile card
KR101851325B1 (en) Method for providing deferred type payment using prepaid type moile card
KR101572860B1 (en) Method for providing deferred type payment using prepaid type moile card
KR101852455B1 (en) A prepayment traffic card and a traffic card payment system comprising the same
KR102309652B1 (en) A method for providing membership services corresponding to a money transfer transaction based on limited code information and an apparatus using it
KR102181317B1 (en) Method for providing settlement service for payment amount and payment gateway server thereof
JP2005317040A (en) Ic card, and electronic money receiving system
KR102273891B1 (en) Method for providing settlement service for payment amount and payment gateway server thereof
KR101759974B1 (en) Micropayment linkage based anonymous prepaid card payment assistive device and method
KR20210037247A (en) Purchasing goods relay system and method based on blockchain
KR20100107366A (en) System and method for managing medical expenses settlement by installments using phone bill and recording medium
KR101697850B1 (en) Server of providing service of micro payment in offline shop and method of the same
KR101486913B1 (en) System for international prepaid card payment using mapping of national bank identification number
KR20150130724A (en) Payment intermediating server using virtual account and method thereof
KR20150076785A (en) Method and server for cash rewards with automatic redemption for credit cards issued abroad

Legal Events

Date Code Title Description
A201 Request for examination
E902 Notification of reason for refusal
E601 Decision to refuse application
J201 Request for trial against refusal decision
J301 Trial decision

Free format text: TRIAL NUMBER: 2015101006292; TRIAL DECISION FOR APPEAL AGAINST DECISION TO DECLINE REFUSAL REQUESTED 20151023

Effective date: 20170706