Card-to-bank payment solution
Through automatic payment processing, payment is directly pushed from the purchaser's account to the supplier's account, solving the security and convenience problems in credit card transactions and achieving an efficient and secure payment process.
Patent Information
- Application Number
- CN202280090340.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-02-18
- Filing Date
- 2022-12-22
- Publication Date
- 2024-11-08
AI Technical Summary
In the prior art, there are security loopholes and inconveniences in credit card transactions, especially in ‘not presenting a card’ transactions, credit card numbers may be leaked, and the transmission and input processes are time-consuming and inconvenient, resulting in fraud risks and delays.
Adopt an automatic payment processing method to push payments directly from the purchaser's account to the supplier's account without the need to transmit a transaction account, pay the amount by debit and credit, and complete transactions in the back-end system, and generate a virtual account to enhance security , and choose automatic payment or virtual account processing according to supplier preferences.
Improves transaction security and efficiency, reduces opportunities for delays and errors, eliminates the transmission and manual entry of credit card information, and provides a fast and easy multiple payment methods.
Smart Images

Figure CN118922849A_ABST
Abstract
Description
background Technical Field
[0001] The field generally relates to methods of automated payment processing. Background Art
[0002] To complete the transaction, the credit card may be physically presented at the point of sale for swiping. When no physical credit card is present at the point of sale (i.e., a "card not present" transaction), such as with an online commercial transaction, the credit card number may be transmitted from the purchaser to the vendor via email or telephone for manual entry at the point of sale.
[0003] Using physical credit cards and transmitting credit card numbers to complete transactions at the point of sale can present security issues. Physical credit cards can be stolen or lost. Credit card numbers transmitted from the purchaser to the vendor during a "card not present" transaction can be compromised in a security breach. Because the same credit card number can be used to complete multiple transactions, unauthorized persons can use compromised credit card numbers to make fraudulent purchases. Additionally, the process of transmitting credit card numbers to be manually entered at the point of sale is time consuming and inconvenient. Vendors can receive multiple emails that include sensitive credit card information for various transactions, leading to confusion, delays, and human error. Summary of the invention
[0004] Disclosed herein are system, apparatus, device, method and / or computer program product embodiments, and / or combinations and sub-combinations thereof, for automated payment processing methods.
[0005] An automatic payment processing method can directly push a payment from a buyer's buyer account to a supplier's supplier account without transmitting a transaction account number linked to the buyer's account. The method can first receive a transaction request from a buyer for transferring a payment amount from the buyer's buyer account to a supplier account associated with a supplier. In some embodiments, the transaction request can allow the buyer to select a supplier or supplier account to which the payment amount is credited from an interface. In other embodiments, the transaction request can be an invoice transmitted from a supplier to a buyer, which specifies the payment amount and a supplier identification number identifying the supplier. In this example, after receiving the invoice, the buyer can enter a transaction request for paying the requested amount. Upon receiving a transaction request from the buyer to transfer the payment amount from the buyer's account to the supplier account, the method debits the payment amount from the buyer's account, identifies the supplier account based on the supplier identification number, and credits the payment amount to the identified supplier account. The buyer account is linked to a transaction card, which is used to pay the amount required in the transaction. The supplier account can be a merchant account that allows the supplier to accept payment from the transaction card linked to the buyer's account. The method may periodically reconcile the supplier account to deposit its balance into another bank account of the supplier, such as an external checking account. The reconciliation process may automatically settle the processed transaction request after a predetermined period of time. For example, to simplify the reconciliation process, the method may automatically reconcile the supplier account at the end of each business day.
[0006] The method is further configured to notify the supplier and the buyer after the requested transaction is completed. The supplier is notified after the payment amount is credited to the supplier's account, and the buyer is notified after the payment amount is debited to the buyer's account.
[0007] Although a single transaction request is described in the above description, the method can execute multiple transaction requests received simultaneously. One notification can be generated and used to check multiple transaction requests between a buyer and a supplier, thereby simplifying the payment process, improving efficiency, and reducing the chance of delays and errors.
[0008] In this method, the process of pushing the payment directly from the buyer's account to the supplier's account occurs substantially simultaneously with the receipt of the transaction request from the buyer. For example, the automatic payment processing can push the payment amount from the buyer's account to the supplier's account within seconds of receiving the transaction request. This provides a highly efficient and easy way for suppliers to quickly receive multiple payments from a variety of buyers. The method also eliminates the potential lag time between the buyer transmitting the credit card information to the supplier and the supplier manually entering the credit card information at the point of sale.
[0009] In some embodiments, the method is further configured to determine whether the supplier account is enrolled in the automatic payment process. If the method determines that the supplier account is enrolled in the automatic payment process, the method proceeds to debit the payment amount from the purchaser account, identify the supplier account based on the supplier identification number, and credit the payment amount to the identified supplier account. On the other hand, if the method determines that the supplier account is not enrolled in the automatic payment process, the method proceeds to generate a virtual account number unique to the specific transaction request from the purchaser. The virtual account number is then transmitted to the supplier for manual entry at the point of sale.
[0010] In some embodiments, a virtual account number is generated to enhance security during transmission of sensitive credit card information in "card not present" transactions. A virtual account number, also known as a token, is a one-time number generated for a specific payment transaction and transmitted to the vendor for manual entry at the point of sale. During a "card not present" transaction, one credit card number may be transmitted to complete multiple transaction requests. On the other hand, when a virtual account number is used to complete a transaction, a different virtual account number is generated and transmitted for each transaction request from the same credit card number.
[0011] In some embodiments, the method is further configured to determine whether the supplier wishes to use automatic payment processing or a virtual account number to complete a transaction request based on stored supplier preferences. Optionally, when registering in automatic payment processing, the supplier can specify whether they wish to use automatic payment processing, a virtual account number, or a combination of the two to process the transaction. Supplier preferences can indicate different methods used to process transactions based on the identity of the purchaser or the type of transaction. For example, a supplier can specify in the supplier preferences that automatic payment processing is used to process transactions for some purchasers, while virtual accounts are used for other purchasers. The supplier can also specify that automatic payment processing is used to process certain transaction types, while virtual accounts are used to process other transaction types. When registering in automatic payment processing via a website, mobile application, etc., the supplier can be provided with the opportunity to specify supplier preferences. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The accompanying drawings are incorporated herein and form a part of this specification.
[0013] Figure 1 A flow chart of a method for automated payment processing according to some embodiments is illustrated.
[0014] Figure 2 FIG. 1 illustrates a method for determining whether to execute Figure 1 The automatic payment processing shown is also a flow chart of a method for executing a token method by generating a virtual account number.
[0015] Figure 3A flow chart illustrating a method for executing multiple transaction requests to be reconciled via one notification is illustrated in accordance with some embodiments.
[0016] Figure 4 Illustrated is an example email notification sent to a supplier upon completion of a periodic reconciliation process in accordance with some embodiments.
[0017] Figure 5 A block diagram of an example computer system for implementing various embodiments is illustrated.
[0018] In the drawings, like reference numbers generally refer to the same or similar elements. Additionally, generally, the leftmost digit(s) of a reference number identifies the drawing in which the reference number first appears. DETAILED DESCRIPTION
[0019] Provided herein are system, apparatus, device, method and / or computer program product embodiments for methods of automating a virtual payment process, and / or combinations and sub-combinations thereof. Various embodiments of these features will now be discussed with reference to the corresponding drawings.
[0020] Figure 1 A flow chart of a method 100 for automatic payment processing according to some embodiments is illustrated. In step 110, a purchaser may provide a transaction request for initiating automatic payment processing and pushing a payment amount from the purchaser's purchaser account directly to a supplier account associated with a supplier. In some embodiments, the transaction request may allow the purchaser to select a supplier or supplier account to which the payment amount is to be credited from an interface. In other embodiments, the transaction request may be an invoice transmitted from the supplier to the purchaser. The invoice may include an invoice number identifying the invoice, a payment amount for a particular transaction, and a supplier identification number identifying the supplier, among other things. In this embodiment, the purchaser may initiate the transaction request by pressing a button labeled "Pay Amount" on the electronic invoice.
[0021] In response to receiving the transaction request, the method 100 performs steps 120-130. In step 120, the method 100 debits the payment amount from the purchaser's account. In some embodiments, the purchaser's account is linked to a transaction card, which can be a credit card used to pay the requested amount and complete the transaction. In these embodiments, the debit of the purchaser's account is equivalent to the purchaser paying the transaction amount using a credit card without ever presenting a credit card (as required during a physical card transaction) or providing sensitive credit card information to the vendor (as required during a "card not present" transaction). This "card not present" transaction allows the purchaser to conduct a quick and simple transaction, similar to directly wire money, while still providing the purchaser with credit card purchase protection. For example, in some embodiments, the transaction request can be protected by an available protection program implemented by a merchant acquiring bank that issues a transaction card that is linked to the purchaser's account and used to pay the payment amount.
[0022] In step 125, method 100 identifies a vendor account to receive the payment amount based on the vendor identification number. The vendor account can be a merchant account used to process and accept payments, such as using a point of sale. A merchant account is an account that allows a business to accept payments in a variety of ways, typically debit or credit cards. A merchant account is established based on an agreement between a recipient and a merchant acquiring bank for settlement of payment card transactions. In some embodiments, the merchant acquiring bank is the same entity that issues a transaction card that is linked to a purchaser's account and is used to pay the payment amount. In some cases, such as when a virtual card number is used to pay the payment amount and complete the transaction, a payment processor, an independent sales organization (ISO), or a member service provider (MSP) is also a party to the merchant agreement. The merchant agreement includes operating regulations established by a card association.
[0023] After obtaining a transaction card using a merchant acquiring bank, a unique supplier identification number is assigned to each supplier. In some embodiments, the supplier identification number can be used to identify the supplier when performing method 100. The supplier identification number can be assigned to each supplier regardless of whether the supplier is registered in the automatic payment processing. In some embodiments, the supplier identification number can be a randomly generated number for each supplier. Therefore, the supplier identification number only identifies the supplier within a system (such as the system described in the present disclosure) and does not contain sensitive information about the supplier. For example, the supplier identification number is not generated based on the account number of the supplier account.
[0024] In step 130, method 100 credits the payment amount debited from the buyer's account in step 120 to the identified supplier account associated with the supplier and the supplier identification number. The process of debiting the buyer's account, identifying the supplier account, and crediting the identified supplier account occurs without transmitting sensitive information of the buyer or supplier. For example, the execution of steps 120-130 does not include transmitting a transaction account number associated with the buyer's account, transmitting a transaction account number associated with the supplier account, or transmitting sensitive card information of a transaction card linked to the buyer's account. Steps 120-130 occur in the back-end system so that the buyer and supplier are unaware of steps 120-130 when completing the transaction. In addition, the process of pushing the payment amount directly from the buyer's account to the supplier account occurs substantially simultaneously with receiving the transaction request from the buyer. For example, in some embodiments, method 100 can push the payment amount from the buyer's account to the supplier account in steps 120-130 within a few seconds of receiving the transaction request in step 110. This provides an efficient and easy way for suppliers to quickly receive payments from buyers.
[0025] After the payment amount is transferred from the purchaser's account to the vendor's account, method 100 performs step 135 to reconcile the vendor's account. In some embodiments, the vendor's account is a merchant account that allows the vendor to accept payments from a transaction card linked to the purchaser's account. In step 135, the vendor's account is reconciled by depositing the balance of the vendor's account into another bank account of the vendor, such as an external checking account. In some embodiments, this reconciliation process may occur periodically, such as at the end of each business day. Figure 3 The periodic verification process is described in further detail.
[0026] Figure 2 FIG. 1 illustrates a method for determining whether to execute Figure 1 200 , or a flowchart of method 200 for executing a token method by generating a virtual account number. In some embodiments, method 200 begins similarly to method 100. In step 210, the purchaser provides a transaction request for transferring a payment amount from the purchaser's account to the supplier's account. In some embodiments, the transaction request may be an invoice transmitted from the supplier to the purchaser. The invoice may include, among other things, the payment amount for a particular transaction and a supplier identification number that identifies the supplier. A transaction card (such as a credit card) is linked to the purchaser's account and is used to pay the payment amount in the requested transaction. Next, method 200 executes decision 215 to determine whether to proceed with steps 220-230 similar to steps 120-130 of method 100, or to proceed with steps 240-260 of the token method.
[0027] In decision 215, method 200 determines whether the supplier account is enrolled in the automatic payment process. In some embodiments, method 200 may make this determination by searching for a supplier identification number associated with the supplier account of the supplier. Since a supplier identification number is generated and assigned to each supplier account when the supplier obtains a transaction card for executing the automatic payment process and paying the payment amount, the supplier's existing supplier identification number may be an indication that the associated supplier account is enrolled in the automatic payment process. In other embodiments, method 200 may make the determination in decision 215 by searching for the supplier's name or other personal information of the supplier. In other embodiments, method 200 may make the determination in decision 215 by directly searching for a supplier account associated with the supplier.
[0028] If method 200 determines in decision 215 that the supplier account is enrolled in the automatic payment process, then method 200 continues to perform the automatic payment process by debiting the purchaser account for the payment amount (step 220), identifying the supplier account based on the supplier identification number (step 225), and crediting the identified supplier account for the payment amount (step 230). In step 235, similar to the above reference to Figure 1 In step 135 described above, method 200 reconciles the supplier's account for the completed transaction. Steps 220-230 include reference to Figure 1 Steps 120-130 describe the automatic payment processing method.
[0029] On the other hand, if the method 200 determines in decision 215 that the supplier account is not enrolled in the automatic payment process, the method 200 continues to perform the token method of steps 240-260. In step 240, a virtual account number, also referred to as a token, is randomly generated for the received transaction request. Each virtual account number is randomly generated and does not contain any sensitive credit card information, such as the original credit card number on the transaction card used to pay the payment amount. The use of a virtual account number reduces exposure to the credit limit associated with the card. In addition, the virtual account number may have other restrictions, such as restrictions that limit it to a specific business. This enhances security compared to using encryption methods alone that still transmit the original sensitive credit card information about the transaction card, but relies on the encoding process before transmission and the decoding process when received at the point of sale to ensure the security of the transmission process. The encryption method may be reverse cracked to recover sensitive card information intercepted during transmission, while the virtual account number randomly generated for each transaction does not contain any sensitive card information at all. By generating and transmitting a unique virtual account number for each transaction, sensitive credit card information is no longer required to be transmitted, thereby reducing the possibility of credit card numbers being leaked and fraudulently reused. In some embodiments, in addition to the virtual card number, encryption methods can be used to protect transactions with payment amounts exceeding $25,000. In addition, multiple people sharing a single corporate credit card can avoid the errors and confusion of sharing a physical credit card, which in turn saves time and reduces the need for manual reconciliation to ensure accounting accuracy after the transaction is completed. However, the vendor still has to transmit and manually enter the virtual account number at the point of sale. This process is time-consuming, inconvenient, and prone to human error, making the token method less desirable than automated payment processing methods.
[0030] In some embodiments, the virtual account number may be a unique fifteen-digit number used to identify the received transaction request. The virtual account number is randomly generated, rather than being based on sensitive credit card information of a transaction card that is cryptographically linked to a purchaser's account used to pay the payment amount in the received transaction request. Thus, when the virtual account number is transmitted to the vendor in step 245, the original sensitive credit card information about the transaction card is not transmitted. This improves the security of processing the transaction request by protecting the transaction card used to pay the payment amount, even if the virtual account number is compromised or intercepted during transmission.
[0031] After receiving the virtual account number transmitted in step 245, the supplier can manually enter the virtual account number of the transaction request at the point of sale (step 250). Once entered, the method 200 proceeds to steps 255-260 - debiting the payment amount from the buyer's account (step 255) and crediting the payment amount to the supplier's account (step 260). Steps 255-260 are similar to common business methods that can be used to transfer money between two accounts, and therefore are not described in detail herein. After transferring the payment amount from the buyer's account to the supplier's account, the method 200 checks the supplier's account (step 265), similar to steps 135 and 235 explained above.
[0032] In some embodiments, decision 215 may also include determining the supplier's supplier preferences. The supplier preferences may include guidelines provided by the supplier when registering the automatic payment processing of method 100. In some embodiments, optionally, the supplier preferences may include instructions for using automatic payment processing (steps 220-230) to process transaction requests for certain buyers or transaction types, while using token methods (steps 240-260) for other buyers or transaction categories. For example, the supplier preferences may specify that automatic payment processing is used for the first buyer list, and the token method is used for the second buyer list. In this example, the transaction request provided by the buyer on the second list will be processed using the token method (steps 240-260), even if it is determined in decision 215 that the supplier is registered in the automatic payment processing. The supplier may further specify different supplier preferences for different buyers based on its relationship with the buyer or based on the transaction type with the buyer. For example, the supplier may specify in the supplier preferences that the automatic payment processing method is always used to complete the transaction request for the first buyer who has a long-term business relationship with the supplier, and the token method is always used to complete the transaction request for the second buyer who only occasionally conducts business with the supplier. Similarly, a vendor can specify in the vendor preferences that an automatic payment processing method is used to complete a first type of transaction request from a purchaser, and a token method is used to complete a second type of transaction request from the same purchaser. The ability to mix and match which method is used to complete each transaction request based on the specified category gives the vendor great flexibility and control over the transaction process.
[0033] Additionally, in some embodiments, the transaction card linked to the purchaser's account may be a closed loop card. A closed loop transaction card limits transaction requests to purchasers and suppliers that are both on a predefined list of acceptors. This closed loop system simplifies the process for suppliers when enrolling in the automatic payment processing. Smaller suppliers that may not have the resources to negotiate separate contracts with each purchaser to perform direct push payments from the purchaser's account to the supplier's account may be able to more easily and efficiently enroll in the automatic payment processing described in the present disclosure. As a result, suppliers enrolled in the automatic payment processing may achieve greater efficiency in transaction requests and greater buyer-to-buyer acceptance.
[0034] Figure 3 A flow chart illustrating a method 300 for executing multiple transaction requests to be reconciled through one notification according to some embodiments is illustrated. The method 300 begins similarly to the method 100. In step 310, the method 300 receives a transaction request initiated by a buyer for transferring a payment amount from a buyer account to a supplier account. In some embodiments, the transaction request may be an invoice including a payment amount for a particular transaction and a supplier identification number identifying the supplier. The payment amount is then debited from the buyer account (step 315), the supplier account is identified based on the supplier identification number (step 320), and the payment amount is credited to the identified supplier account (step 325). The method 300 then proceeds to decision 330 to determine whether a predetermined time period has passed.
[0035] If the predetermined time period has not passed, the method 300 repeats steps 310-325 to process another transaction request of another payment amount between the purchaser and the supplier. Therefore, multiple transaction requests can be completed between a purchaser and a supplier within a predetermined time period. If the predetermined time period has passed, the method 300 proceeds to step 335 to check the supplier account. In step 335, the method 300 checks all transaction requests completed during the predetermined time period by depositing the full balance of the supplier account into another bank account of the supplier. In this embodiment, the full balance of the supplier account includes all payment amounts received for each transaction request during the predetermined time period. Since the full balance of the supplier account is deposited into another bank account of the supplier at one time, only one notification is needed to check multiple transaction requests completed during the predetermined time period. This simplifies and facilitates the supplier's verification process, especially when trading with a buyer who often initiates multiple transaction requests with the supplier during the business process.
[0036] In some embodiments, the predetermined time period can be one day. In other embodiments, various predetermined time periods can be selected, such as two days or three days.
[0037] The method 300 then proceeds to step 340 and notifies the supplier of a notification including the multiple transaction requests completed during the predetermined time period. After completing the verification process in step 335, the method 300 sends a notification to the supplier, wherein the notification includes a bank receipt for verifying the multiple transaction requests completed during the predetermined time period. The notification provided can be any electronic notification, such as an email, a text message, a push notification on a mobile application, etc. An exemplary email notification sent to the supplier after completing the periodic verification process is as follows: Figure 4 shown.
[0038] Figure 4 An example email notification 400 is shown that is sent to a supplier upon completion of a periodic check-in process according to some embodiments. The periodic check-in process may be similar to that described above with reference to Figure 3 The method 300 is described. Figure 4 As shown, an example email notification 400 sent to a supplier includes a bank invoice for verifying multiple transaction requests during a predetermined time period. The email notification 400 may include a title portion 405, a salutation portion 410, a payment summary portion 415, a payment details portion 420, and a contact information portion 425.
[0039] In the header portion 405, the email notification 400 includes a brief subject and a preview. The header portion 405 lets the supplier know that the payment amount for at least one transaction request initiated by the buyer has been pushed from the buyer's account to the supplier's account. In the salutation portion 410, the supplier's name and the buyer's name are identified. In the payment summary portion 415, the total balance of the supplier's account reconciled by the bank invoice in the email notification 400 is shown. The total balance includes the payment amount for each transaction request completed during a predetermined time period before the reconciliation process began.
[0040] The balance details for up to 25 invoices may be listed in the payment details section 420, including the number of each transaction request ("Invoice Number"), the date each transaction request was processed ("Invoice Date"), and the payment amount of each transaction request ("Payment Amount"). For example, Figure 4 In the example provided in , the email notification 400 shows a bank invoice for two transaction requests: $900.00 pushed from the buyer's account to the supplier's account on May 15, 2019, and $1000.01 pushed from the buyer's account to the supplier's account on May 20, 2019. The contact information of the merchant acquiring bank that completed the multiple transaction requests is provided in the contact information section 425 to facilitate access to the merchant acquiring bank.
[0041] By providing one email notification 400 including one bank invoice for multiple transaction requests completed during a predetermined time period, suppliers can reconcile their supplier accounts more efficiently and accurately than receiving notifications after processing each individual transaction request from a buyer.
[0042] Figure 5 A block diagram of an example computer system 500 for implementing various embodiments of the above-described methods is illustrated. For example, one or more computer systems 500 may be used to implement any of the embodiments discussed herein, as well as combinations and sub-combinations thereof. Figure 1-4 3 and 4 to describe computer system 500; however, computer system 500 is not limited to the example embodiments described in the previous figures.
[0043] In some embodiments, the computer system 500 may receive power from an external power source 505. The computer system may include one or more processors (also referred to as central processing units or CPUs), such as processor 510. The computer system 500 may also include memory 515, such as random access memory (RAM). The memory 515 may include one or more levels of cache. The memory 515 may have control logic (i.e., computer software) and / or data stored therein. The processor 510 may execute program code using instructions stored in the memory 515 to perform operations that implement the various embodiments described herein.
[0044] Computer system 500 may include a transmitter / receiver 520 for transmitting and receiving communications between a purchaser 525 and a supplier 535. For example, referring to Figure 1 In method 100, according to some embodiments, transmitter 520 can transmit an invoice including a payment amount and a supplier identification number from supplier 535 to buyer 525. Transmitter / receiver 520 can also receive a transaction request from buyer 525 in step 110. Computer system 500 can also include a notification module 530 for providing notifications to buyer 525 and supplier 535. For example, referring to method 300 and Figure 3 and Figure 4 , the notification module 530 may provide an email notification 400 to the supplier 535 in step 340 so that the supplier 535 may check the multiple transaction requests completed during the predetermined time period in the decision 330 .
[0045] The computer system 500 further includes a payment routing module 540 and a virtual account number generator 545. In some embodiments, the payment routing module 540 is configured to implement the reference Figure 1-3The payment routing module 540 may store various information required to implement automatic payment processing, including, but not limited to, invoices 550, invoice numbers 555 assigned to each invoice 550, payment amounts 560 for each transaction request, supplier identification numbers 565 associated with each supplier 535, and supplier preferences 570. In some embodiments, the invoices 550 and invoice numbers 555 may be optional, and other methods of receiving payment amounts 560 and supplier identification numbers 565 may be used (e.g., the purchaser 525 may select payment amounts 560 or supplier identification numbers 566 from a drop-down menu in an online portal without having to receive invoices 550 or invoice numbers 555). The computer system 500 communicates with the purchaser account 575 and the supplier account 580 so that the payment amounts 560 for the invoices 550 may be pushed directly from the purchaser account 575 to the supplier account 580. The buyer account 575 can be linked to a transaction account number 585 identifying the buyer account 575 and a transaction card 590, such as a credit card used to pay the payment amount 560. The supplier account 580 can be linked to a supplier bank account 595, which can be a second bank account of the supplier, such as a checking account. In some embodiments, the balance of the supplier account 580 can be deposited into the external supplier bank account 595 to reconcile the supplier account 580.
[0046] The processor 510 of the computer system 500 may determine whether to perform an automatic payment processing method or a token method based on various considerations, including but not limited to instructions stored in the vendor preferences 570 or the existence of a vendor identification number 565 or a vendor account 580 associated with the vendor 535. For example, referring to Figure 2 In method 200 of the present invention, processor 510 of computer system 500 may determine whether to perform an automatic payment processing method or a token method in decision 215. If automatic payment processing is performed, payment routing module 540 performs steps 220-230, including debiting payment amount 560 from purchaser account 575 (step 220), identifying vendor account 580 based on vendor identification number 565 (step 225), and crediting payment amount 560 to identified vendor account 580 (230). If a token method is performed, virtual account number generator 545 generates a virtual account number in step 240. After the virtual account number is transmitted to vendor 535 (step 245) and vendor 535 enters the virtual account number at the point of sale (step 250), payment routing module 540 may then proceed to push payment amount 560 from purchaser account 575 directly to vendor account 580 (steps 255-260).
[0047] Computer system 500 may also be, to name a few non-limiting examples, any of a personal digital assistant (PDA), a desktop workstation, a laptop or notebook computer, a netbook, a tablet computer, a smartphone, a smart watch or other wearable device, part of the Internet of Things, and / or an embedded system, or any combination thereof.
[0048] Computer system 500 can be a client or server, accessing or hosting any applications and / or data through any delivery paradigm, including but not limited to remote or distributed cloud computing solutions; local or on-premise software ("on-premise" cloud-based solutions); "as a service" models (e.g., content as a service (CaaS), digital content as a service, software as a service, management software as a service (MSaaS), platform as a service (PaaS), desktop as a service (DaaS), framework as a service (FaaS), backend as a service (BaaS), mobile backend as a service (MBaaS), infrastructure as a service (IaaS), etc.); and / or a hybrid model including any combination of the foregoing examples or other services or delivery paradigms.
[0049] Any applicable data structures, file formats, and schemas in computer system 500 may be derived from standards including, but not limited to, JavaScript Object Notation (JSON), Extensible Markup Language (XML), another markup language (YAML), Extensible Hypertext Markup Language (XHTML), Wireless Markup Language (WML), MessagePack, XML User Interface Language (XUL), or any other functionally similar representations, alone or in combination. Alternatively, proprietary data structures, formats, or schemas may be used alone or in combination with known or open standards.
[0050] In some embodiments, a tangible, non-transitory apparatus or article of manufacture including a tangible, non-transitory computer-usable or readable medium having control logic (software) stored thereon may also be referred to herein as a computer program product or program storage device. This includes, but is not limited to, computer system 500, processor 510, memory 515, and tangible articles of manufacture embodying any combination of the foregoing. When executed by one or more data processing devices (such as computer system 500), such control logic may cause such data processing devices to operate as described herein.
[0051] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the relevant art(s) how to use the Figure 5It will be apparent that data processing devices, computer systems, and / or computer architectures other than those shown can be used to make and use the embodiments of the present disclosure. In particular, the embodiments can be operated using software, hardware, and / or operating system implementations different from those described herein.
[0052] It should be understood that the detailed description section, but not any other section, is intended to be used to interpret the claims. The other sections may set forth one or more but not all exemplary embodiments contemplated by the inventor(s), and therefore, are not intended to limit the present disclosure or the appended claims in any way.
[0053] Although the present disclosure describes exemplary embodiments of exemplary fields and applications, it should be understood that the present disclosure is not limited thereto. Other embodiments and modifications thereof are possible and are within the scope and spirit of the present disclosure. For example, without limiting the generality of this paragraph, the embodiments are not limited to the software, hardware, firmware, and / or entities shown in the figures and / or described herein. In addition, the embodiments (whether or not explicitly described herein) have significant utility for fields and applications beyond the examples described herein.
[0054] Embodiments are described herein by means of functional building blocks that illustrate implementations of specific functions and relationships thereof. For ease of description, the boundaries of these functional building blocks are arbitrarily defined herein. Alternative boundaries can be defined as long as the specified functions and relationships (or their equivalents) are properly performed. In addition, alternative embodiments can perform functional blocks, steps, operations, methods, etc., in an order different from that described herein.
[0055] References to "one embodiment", "embodiment" and "example embodiment" or similar phrases herein indicate that the described embodiments can include specific features, structures or characteristics, but each embodiment does not necessarily include specific features, structures or characteristics. In addition, such phrases do not necessarily refer to the same embodiment. In addition, when describing specific features, structures or characteristics in conjunction with an embodiment, it will be within the knowledge of the technician in the relevant (multiple) fields to combine such features, structures, or characteristics in other embodiments, regardless of whether it is explicitly mentioned or described herein. Additionally, some embodiments can be described using the expressions "coupled" and "connected" and their derivatives. These terms are not necessarily synonymous with each other. For example, some embodiments can be described using the terms "connected" and / or "coupled" to indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" can also refer to two or more elements that are not in direct contact with each other, but still cooperate or interact with each other.
[0056] The breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
Claims
1. A computer-implemented method for automated payment processing, comprising: (a) receiving a transaction request from a purchaser for transferring a payment amount from a purchaser account of the purchaser to a vendor account associated with a vendor, wherein the purchaser account is linked to a transaction card and a transaction account number; In response to the transaction request: (b) debiting the purchaser's account for the amount of the payment; (c) identifying the supplier account based on the supplier identification number; (d) crediting the payment amount to the vendor account associated with the vendor, the vendor account being a first bank account that allows the vendor to accept payment from a transaction card; and (e) regularly reconciling the supplier's account to deposit the balance of the supplier's account into the supplier's second bank account, The transaction request can be automatically paid without transmitting the transaction account to the supplier.
2. The method according to claim 1, further comprising: notifying said supplier of said credit of said payment amount to said supplier's account; as well as The purchaser is notified of the debit of the payment amount from the purchaser's account.
3. The method according to claim 1, further comprising: determining whether the supplier account is enrolled in the automatic payment process; If the supplier account is registered in the automatic payment process, performing steps (b)-(d); If the supplier account is not enrolled in the automatic payment process: generating a virtual account number unique to the transaction request; and The virtual account number is transmitted to the vendor for entry at a point of sale.
4. The method according to claim 1, wherein: The step (e) of regularly checking the supplier accounts comprises: The transaction request is automatically settled after a predetermined period of time.
5. The method according to claim 1, wherein: Steps (b)-(d) occur substantially simultaneously with receiving the transaction request from the purchaser.
6. The method according to claim 1, wherein: The transaction card is a credit card with credit card purchase protection.
7. The method according to claim 1, wherein: The transaction card is a closed loop card that limits the transaction request between the buyer and a predefined list of suppliers.
8. The method according to claim 1, wherein: The transaction request includes transmitting to the purchaser an invoice from the supplier, the invoice specifying the payment amount and the supplier identification number identifying the supplier.
9. The method according to claim 1, wherein: The transaction request includes allowing the purchaser to select the supplier or supplier account from an interface for crediting the payment amount.
10. The method according to claim 1, wherein: The automated payment process is configured to execute multiple transaction requests simultaneously.
11. The method according to claim 10, wherein: The step (e) of regularly checking the supplier accounts comprises: The plurality of transaction requests are automatically settled through one notification.
12. A system for automatic payment processing, comprising: Memory; as well as at least one processor coupled to the memory and configured to: (a) receiving a transaction request from a purchaser for transferring a payment amount from a purchaser account of the purchaser to a vendor account associated with a vendor, wherein the purchaser account is linked to a transaction card and a transaction account number; In response to the transaction request: (b) debiting the purchaser's account for the amount of the payment; (c) identifying the supplier account based on the supplier identification number; (d) crediting the payment amount to the vendor account associated with the vendor, the vendor account being a first bank account that allows the vendor to accept payment from a transaction card; and (e) regularly reconciling the supplier's account to deposit the balance of the supplier's account into the supplier's second bank account, The transaction request can be automatically paid without transmitting the transaction account to the supplier.
13. The system of claim 12, further comprising: notification circuit, the notification circuit being configured to notifying said supplier of said credit of said payment amount to said supplier's account; as well as The purchaser is notified of the debit of the payment amount from the purchaser's account.
14. The system according to claim 12, wherein: The at least one processor is further configured to: determining whether the supplier account is enrolled in the automatic payment process; If the supplier account is registered in the automatic payment process, performing steps (b)-(d); If the supplier account is not enrolled in the automatic payment process: generating a virtual account number unique to the transaction request; and The virtual account number is transmitted to the vendor for entry at a point of sale.
15. The system of claim 12, wherein: The transaction request includes transmitting to the purchaser an invoice from the supplier, the invoice specifying the payment amount and the supplier identification number identifying the supplier.
16. The system of claim 12, wherein: The step (e) of regularly checking the supplier accounts comprises: The transaction request is automatically settled after a predetermined period of time.
17. The system of claim 12, wherein: Steps (b)-(d) occur substantially simultaneously with receiving the transaction request from the purchaser.
18. A non-transitory computer readable medium having instructions stored thereon, which, when executed by at least one processor, cause the at least one processor to perform operations comprising: (a) receiving a transaction request from a purchaser to transfer a payment amount from a purchaser account of the purchaser to a supplier account associated with a supplier, wherein: The purchaser account is linked to a transaction card and a transaction account number; In response to the transaction request: (b) debiting the purchaser's account for the amount of the payment; (c) identifying the supplier account based on the supplier identification number; (d) crediting the payment amount to the vendor account associated with the vendor, the vendor account being a first bank account that allows the vendor to accept payment from a transaction card; as well as (e) regularly reconciling the supplier's account to deposit the balance of the supplier's account into the supplier's second bank account, The transaction request can be automatically paid without transmitting the transaction account to the supplier.
19. The non-transitory computer readable medium of claim 18, further comprising: notifying said supplier of said credit of said payment amount to said supplier's account; as well as The purchaser is notified of the debit of the payment amount from the purchaser's account.
20. The non-transitory computer readable medium of claim 18, further comprising: determining whether the supplier account is enrolled in the automatic payment process; If the supplier account is registered in the automatic payment process, performing steps (b)-(d); If the supplier account is not enrolled in the automatic payment process: generating a virtual account number unique to the transaction request; and The virtual account number is transmitted to the vendor for entry at a point of sale.
