WO2015120420A2 - Système et procédé de transaction financière - Google Patents

Système et procédé de transaction financière Download PDF

Info

Publication number
WO2015120420A2
WO2015120420A2 PCT/US2015/015079 US2015015079W WO2015120420A2 WO 2015120420 A2 WO2015120420 A2 WO 2015120420A2 US 2015015079 W US2015015079 W US 2015015079W WO 2015120420 A2 WO2015120420 A2 WO 2015120420A2
Authority
WO
WIPO (PCT)
Prior art keywords
account
transaction
transactions
party
pins
Prior art date
Application number
PCT/US2015/015079
Other languages
English (en)
Other versions
WO2015120420A3 (fr
Inventor
Walter STEELMAN
Kristopher BARNINGS
Matthew Carpenter
John Brewer
Original Assignee
Steelman Walter
Barnings Kristopher
Matthew Carpenter
John Brewer
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 Steelman Walter, Barnings Kristopher, Matthew Carpenter, John Brewer filed Critical Steelman Walter
Publication of WO2015120420A2 publication Critical patent/WO2015120420A2/fr
Publication of WO2015120420A3 publication Critical patent/WO2015120420A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4015—Transaction verification using location information
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4012—Verifying personal identification numbers [PIN]

Definitions

  • An account transaction processing system comprising an account having an account number stored in a data storage. Said account number associated with an account holder having an account holder information and a one or more PINs. Said account number being managed by a third party. Said account holder information and said one or more PINs stored in said data storage. Said one or more PINs associated with a one or more transaction groups. Said one or more transaction groups associated with a one or more issuer accounts associated with said account holder. Said one or more issuer accounts each being funded and managed by a one or more issuers. A one or more transaction data associated with said one or more transactions and each at least comprising a transaction amount, said account number and a one among said one or more PINs.
  • Said one or more transactions authorized between said account holder and a merchant by submitting and requesting an authorization of said transaction data from said merchant to said third party, looking up said one among said one or more PINs and said account number in said data storage by said third party, authorizing said transaction data with said issuer associated with said transaction groups, sending an authorization approval back to said third party and to said merchant, characterizing said transaction data according said association between said one or more PINs associated and said one or more transaction groups in said data storage.
  • Figure 1 illustrates a first network configuration 101 of a financial transaction system 100.
  • Figures 2A, 2B and 2C illustrate a perspective overview of a mobile phone 201a, a personal computer 201b and a tablet 201c.
  • Figure 3 illustrates an address space 302 within said one or more computers.
  • Figures 4A and 4B illustrate two embodiments for collecting and storing data with said financial transaction system 100; a first embodiment with a flow diagram between said first computer 102a and said server 108, and a second embodiment comprising of just said first computer 102a.
  • Figures 5 A and 5B illustrate two examples of a flow diagram between said memory 306a and said memory 306d.
  • Figures 6A, 6B and 6C illustrate three embodiments of a transaction processing flow diagram.
  • Figure 6A illustrates a prior art diagram 600a
  • Figure 6B illustrates a custom terminal diagram 600b
  • Figure 6C illustrates an improved financial transaction processing system 600c.
  • Figure 6A discusses the prior art by discussing said prior art diagram 600a.
  • Figure 6B illustrates said custom terminal diagram 600b.
  • Figure 6C illustrates said improved financial transaction processing system 600c.
  • Figure 7 comprises a flow chart 700.
  • Figures 8A, 8B, 8C, 8D and 8E illustrate a database schematic 800 for said financial transaction system 100, a system user table 802, a PIN entries table 804, an accounts table 806, and a bank table 808, respectively.
  • Figure 8B illustrates said system user table 802.
  • Figure 8C illustrates said PIN entries table 804.
  • Figure 8D illustrates said accounts table 806.
  • Figure 8E illustrates said bank table 808.
  • Figures 9A and 9B illustrate said transactions table 902 and said itemized items 904.
  • Figure 9A illustrates said transactions table 902.
  • Figure 9B illustrates said itemized items 904.
  • Figure 10 illustrates a system user form 1002.
  • Figure 1 1 illustrates a receipt 1 100.
  • Figure 12 illustrates a flow chart 1200 between a merchant 1202, a third party 1204 and an issuer 1206.
  • Figure 13 illustrates a flow chart 1300 between a merchant 1202, a third party 1204 and an issuer 1206.
  • FIG. 1 illustrates a first network configuration 101 of a financial transaction system 100.
  • said financial transaction system 100 can comprise a one or more computers at a one or more locations.
  • said one or more computers can comprise a first computer 102a, a second computer 102b and a third computer 102c.
  • said one or more locations can comprise a first location 103a, a second location 103b and a third location 103c.
  • said first location can comprise a field location.
  • said one or more computers can communicate on a network 106, which can connect to a one or more servers (such as a server 108).
  • a printer 104 can be hardwired to said first computer 102a (not illustrated here), or said printer 104 can connect to one of said one or more computers (such as said third computer 102c, illustrated) via network 106.
  • Said network 106 can be a local area network (LAN), a wide area network (WAN), a piconet, or a combination of LANs, WANs, or piconets.
  • LAN local area network
  • WAN wide area network
  • piconet a combination of LANs, WANs, or piconets.
  • LAN local area network
  • WAN wide area network
  • piconet a combination of LANs, WANs, or piconets.
  • LAN local area network
  • WAN wide area network
  • piconet a combination of LANs, WANs, or piconets.
  • LAN local area network
  • WAN wide area network
  • piconet a piconets
  • said server 108 represents at least one, but can be many servers, each connected to said network 106.
  • Said server 108 can connect to a data storage 110.
  • Said data storage 1 10 can connect directly to said server 108, as shown in Figure 1, or may exist remotely on said network 106.
  • said data storage 110 can comprise any suitable long-term or persistent storage device and, further, may be separate devices or the same device and may be collocated or distributed (interconnected via any suitable communications network).
  • FIGS 2A, 2B and 2C illustrate a perspective overview of a mobile phone 201a, a personal computer 201b and a tablet 201c.
  • the useful definition of a computer has become more broadly understood to include mobile phones, tablet computers, laptops, desktops, and similar.
  • Microsoft® have attempted to merge devices such as a tablet computer and a laptop computer with the release of "Windows® 8".
  • said one or more computers each can include, but is not limited to, a laptop (such as said personal computer 201b), desktop, workstation, server, mainframe, terminal, a tablet (such as said tablet 201c), a phone (such as said mobile phone 201a), and/or similar.
  • said one or more computers can have similar basic hardware, such as a screen 202 and a one or more input devices (such as a keyboard 204a, a trackball 204b, a one or more cameras 204c, a wireless - such as RFID - reader, a track pad 204d, and/or a home button 220).
  • said screen 202 can comprise a touch screen.
  • said track pad 204d can function similarly to a computer mouse as is known in the art.
  • said tablet 201c and/or said personal computer 201b can comprise a Microsoft® Windows® branded device, an Apple® branded device, or similar.
  • said tablet 201c can be an X86 type processor or an ARM type processor, as is known in the art.
  • Said financial transaction system 100 can comprise a data 206.
  • said data 206 can comprise data related to financial transactions.
  • said one or more computers can be used to input and view said data 206.
  • said data 206 can be input into said one or more computers by taking pictures with one of said one or more camera 204c, by typing in information with said keyboard 204a, or by using gestures on said screen 202 (where said screen 202 is a touch screen).
  • said first computer 102a can comprise an iPhone®, a BlackBerry®, a smartphone, or similar.
  • one or more computers can comprise a laptop computer, a desktop computer, or similar.
  • Figure 3 illustrates an address space 302 within said one or more computers.
  • Each among said one or more computers and said server 108 can comprise an embodiment of address space 302.
  • said address space 302 can comprise a processor 304, a memory 306, and a communication hardware 308.
  • said processor 304 can comprise a plurality of processors
  • said memory 306 can comprise a plurality of memory modules
  • said communication hardware 308 can comprise a plurality of communication hardware components.
  • said data 206 can be sent to said processor 304; wherein, said processor 304 can perform processes on said data 206 according to an application stored in said memory 306, as discussed further below.
  • Said processes can include storing said data 206 into said memory 306, verifying said data 206 conforms to a one or more preset standards, or ensuring a required set among said required data 206 has been gathered for said data management system and method.
  • said data 206 can include data which said one or more computers can populate automatically, such as a date and a time, as well as data entered manually. Once a portion of gathering data has been performed said data 206 can be sent to said communication hardware 308 for communication over said network 106.
  • Said communication hardware 308 can include a network transport processor for packetizing data, communication ports for wired communication, or an antenna for wireless communication.
  • said data 206 can be collected in one or more computers and delivered to said server 108 through said network 106.
  • Figures 4A and 4B illustrate two embodiments for collecting and storing data with said financial transaction system 100; a first embodiment with a flow diagram between said first computer 102a and said server 108, and a second embodiment comprising of just said first computer 102a.
  • said first computer 102a can comprise an address space 302a, a processor 304a, a memory 306a, and a communication hardware 308a.
  • said server 108 can comprise an address space 302d, a processor 304d, a memory 306d, and a communication hardware 308d.
  • said communication hardware 308a and said communication hardware 308d can send and receive data to and from one another and or can communicate with said data storage 110 across said network 106.
  • data storage 110 can be embedded inside of said one or more computers as a data storage 110a, which may speed up data communications by said financial transaction system 100.
  • said data can be stored temporarily on said data storage 1 10a and later moved to said data storage 110 for backup and sharing purposes.
  • said server 108 can comprise a third party data storage and hosting provider or privately managed as well.
  • said data storage 110 can be located on said first computer 102a, here labeled as said data storage 1 10a.
  • said first computer 102a can operate without a data connection out to said server 108 while performing said system and method for field capture of data.
  • Figures 5 A and 5B illustrate two examples of a flow diagram between said memory 306a and said memory 306d.
  • said financial transaction system 100 can process said data 206 on said first computer 102a and/or said server 108.
  • said memory 306a can comprise a device application 502 capable of generating a data records 504 from user inputs or, otherwise, processing said data records 504 delivered to said device application 502 from said data storage 110.
  • said data records 504 can be transferred between said device application 502 on said memory 306a of said first computer 102a and a server application 506 in said memory 306d of said server 108.
  • said server 108 can be useful for processing said data 206, as is known in the art.
  • said server 108 can be removed from the flow diagram entirely as said memory 306a is capable of processing said data records 504 and/or said data 206 without the assistance of said server 108.
  • Figures 6A, 6B and 6C illustrate three embodiments of a transaction processing flow diagram.
  • Figure 6A illustrates a prior art diagram 600a
  • Figure 6B illustrates a custom terminal diagram 600b
  • Figure 6C illustrates an improved financial transaction processing system 600c.
  • FIG. 6A discusses the prior art by discussing said prior art diagram 600a.
  • said prior art diagram 600a can receive a transaction at said for processing transactions (illustrated by said prior art diagram 600a), a new transaction 601 can enter said prior art diagram 600a at a merchant terminal 602 and/or an ATM 604, as is known in the art.
  • said new transaction 601 can be transmitted to an acquirer 606, then to one of a plurality of third party networks 608, then to an issuer 610, which may then process said new transaction 601 with a data processor 612 and return an authorization message back to said merchant terminal 602 or said ATM 604.
  • said issuer 610 and said data processor 612 can be at a first financial institution 614a.
  • said first financial institution 614a may require further processing of said new transaction 601 at a second financial institution 614b.
  • the current model for switch processing of credit and debit cards is a relatively simple one.
  • a bank issues a card to a consumer.
  • the consumer makes a payment using the card with a merchant.
  • the merchant uses a network (such as said plurality of third party networks 608) to process the card (that is, said new transaction 601) to receive its payment.
  • Said plurality of third party networks 608 charges the merchant a percentage for processing the card.
  • the credit card company (such as said first financial institution 614a and/or said second financial institution 614b) charges a percentage of the percentage paid to said plurality of third party networks 608 for processing said new transaction 601 (tied to said card).
  • Said prior art diagram 600a and other current processing systems, are designed such that, regardless of how transactions are handled, the merchants lose out on their collected funds (for the added convenience of a near immediate bank draft). If that turns out to be a larger sale, they always pay more. The banks also lose out if the card numbers are ever stolen because they hold the liability of that theft. However, if a bank is absorbing the liability, then the bank should be reaping the benefits.
  • Figure 6B illustrates said custom terminal diagram 600b.
  • said prior art diagram 600a can be improved by installing proprietary terminals at transaction locations, such as a merchant's location.
  • said custom terminal diagram 600b can comprise a custom terminal 620 capable of handling traditional transactions which have previously been handled by said custom terminal diagram 600b. Accordingly, said custom terminal 620 can be reverse compatible with existing transactions, such as said new transaction 601. However, said custom terminal 620 can add new functionality, as discussed as follows.
  • FIG. 6C illustrates said improved financial transaction processing system 600c.
  • said custom terminal 620 can be used to handle both a one or more traditional transactions 601a and a one or more internal transactions 601b.
  • said one or more traditional transactions 601a can comprise well-known debit and credit transactions upon which everyday commerce is transacted, such as Visa® debit and credit transactions, and so on.
  • said one or more internal transactions 601b can comprise transactions at vendors and merchants with a direct relationship with said first financial institution 614a and/or said second financial institution 614b.
  • said custom terminal 620 can handle gift card accounts for a merchant or gas station credit accounts used to make purchases at a branded convenience store.
  • said custom terminal 620 may receive said one or more internal transactions 60 lb and bypass said plurality of third party networks 608 by, instead, routing transactions across an internal network 630 to said first financial institution 614a. In so doing, said custom terminal 620 may enable a merchant to process said one or more traditional transactions 601a and said one or more internal transactions 601b, and thereby selecting among said plurality of third party networks 608 and said internal network 630 for purposes of minimizing transaction costs.
  • Said financial transaction system 100 can offer consumers a new set of tools for managing their money and turning the ACH payment system into a worldwide commodity.
  • electronic commerce can allude to any or all of the following types of payment options: (i) using magnetic-stripe or RFID-enabled cards for payments, (ii) using Smart Cards to make payments, (iii) auto pay features tied to any card, (iv) use of NFC or eWallet or Bluetooth® type payments, and (v) use of online ACH payments.
  • said service can comprise a preferred mode of transactions: ACH.
  • said financial transaction system 100 can allow banks to provide a new type of card using a different kind of electronic switch for the processing of such payments.
  • the novelty of this approach will allow the banks to be able to offer something the consumer may believe to be cutting edge as well as possibly saving merchants some of their hard earned money.
  • said financial transaction system 100 can absolve said financial transaction of carrying the liability involved with issuing a debit card displaying one of the major credit card company's logos.
  • said financial transaction system 100 can allow a bank to be freed up to issue cards and actually collect funds in a new way: (i) The cards could no longer based on standard bin ranges, instead, they could based on an alphanumeric system which bypasses the standard networks, (ii) financial transaction system 100 could only collect a far smaller flat fee, allowing the banks to offer extremely reduced and competitive rates to their merchants, (iii) all payments made with financial transaction system 100 cards could use an ACH switch, and (iv) could offer bank customers a wide variety of tools for managing their money.
  • said financial transaction system 100 can be implemented in today's market.
  • said financial transaction system 100 can be implemented for consumers with no perceived changes aside from having a differently branded card or (possibly) an app that they use to make payments. Otherwise, all functionality can remain the same. That is, said consumers can receive a set of impressive tools including the paperless receipt system with little change in their spending habits.
  • merchants can benefit by not paying out their profits in fees that.
  • banks can benefit by getting a piece of the pie and offer a service for which consumers will appreciate and love them.
  • Figure 7 comprises a flow chart 700.
  • Said flow chart 700 can comprise a step one 702, a step two 704 and a step three 706.
  • said step one 702 can comprise receiving a one or more transactions at a custom terminal from a one or more customers for a one or more merchants.
  • said step two 704 can comprise communicating between said custom terminal and an issuer through a third party network for standard transactions, and an internal networks for said internal transactions.
  • said step three 706 can comprise reaching an outcome at said issuer for each of said one or more transactions, and communicating said outcome back to said custom terminal.
  • said one or more transactions comprise a standard transactions and an internal transactions.
  • Figures 8A, 8B, 8C, 8D and 8E illustrate a database schematic 800 for said financial transaction system 100, a system user table 802, a ⁇ entries table 804, an accounts table 806, and a bank table 808.
  • Said database schematic 800 illustrates a data relationship arrangement for said financial transaction system 100, as is known in the art.
  • Said system user table 802 can comprise a list of users of said financial transaction system 100;
  • said PIN entries table 804 can comprise a list of PINs associated to users listed in said system user table 802 and referring to a one or more accounts in said accounts table 806.
  • Said accounts table 806 can comprise a list of bank accounts and account information, and can refer to a list of banks found in said bank table 808.
  • said system user table 802 can comprise a system user ID 810, a user info 812, a username 814, and a password 816.
  • said PIN entries table 804 can comprise a pin ID 820, a sys user ID 810, a pin ID nickname 821, a bank acc num 822, a pin seq 824, a pin offset 826, a bus 830, a pers 832, a proj num 834, a notif 836, a geo limit 838, a restrict 840, a restrict period 842, and a chrg ordr 844.
  • said accounts table 806 can comprise a bank account number 822, a bank ID 852, an account zip 854, an account limit 856, a bank pin offset 858, and an account type 860.
  • said bank table 808 can comprise a bank ID 852, a bank name 870 and a bank info 872.
  • a transactions table 902 can comprise a transactionid 910, a transaction date 912, a pin ID 820, a result 914, and a location 916.
  • an itemized items 904 can comprise an itemizationid 920, a transactionid 922, an item desc 924, a cost 926, a quantity 927, a tax 928, a subtotal 930, a customl 32a, a custom2 32b, an item category 934, and a user memo 936.
  • Each among the tables in said database schematic 800 can comprise a unique (key) identifier field which can comprise: said sys user ID 810 for said system user table 802; said pin ID 820 for said PIN entries table 804; said bank account number bank acc num 822 for said accounts table 806; said bank ID 852 for said bank table 808; said transactionid 910 for said transactions table 902; and said itemizationid 920 for said itemized items 904.
  • Database schematic 800 illustrates a relationship between the fields of its tables.
  • said sys user ID 810 in said system user table 802 can have a one to many relationship with said sys user ID 810 in said ⁇ entries table 804; said bank acc num 822 in said PIN entries table 804 can comprise a many to many relationship with sid bank acc num 822 in said accounts table 806; said bank ID 852 in said accounts table 806 can comprise a many to one relationship with said bank ID 852 in said bank table 808; said pin ID 820 in said transactions table 902 can comprise a many to one relationship with said pin ID 820 in said PIN entries table 804; and, finally, said transactionid 922 in said itemized items 904 can comprise a many to one relationship with said transactionid 910 of said transactions table 902.
  • Descriptions of the data relationships, as presented in this disclosure are merely exemplary and may be modified by one trained in the art to overcome everyday issues without departing from the scope of this application.
  • FIG. 8B illustrates said system user table 802.
  • Said system user table 802 is a listing of users of said financial transaction system 100, each of home can be added to said database schematic 800 as a single row in said system user table 802.
  • said system user table 802 can comprise more fields related to users and user biographical information, as is known in the art.
  • system user table 802 comprises a unique id (said sys user ID 810), a user description (said user info 812), a user name (said username 814), and a password (said password 816).
  • the database schematic 800 has three users, as illustrated.
  • FIG. 8C illustrates said PIN entries table 804.
  • said financial transaction system 100 can comprise a system for mapping users to unique PIN numbers with special characteristics associated with them, and said PIN entries table 804 can explain much of those special characteristics.
  • said PIN entries table 804 can comprise a reference to said sys user ID 810 of said system user table 802, as discussed above. Accordingly, each user of said financial transaction system 100 can have more than one PIN number (and therefore more than one of said pin ID 820) associated with them.
  • Each field in said pin ID 820 can comprise a nickname set by users (said pin ID nickname 821), a bank account set up by the user (said bank acc num 822), a sequence to charge as a default (said pin seq 824), an encoded reference to a PIN number associated with each field (said pin offset 826), a one or more characterization fields associated with transactions made with each among said pin ID 820 (which can comprise said bus 830, said pers 832, and said proj num 834), a one or more restriction fields (which can comprise said notif 836, said geo limit 838, said restrict 840, and said restrict period 842), and an order for charging set by a user (said chrg ordr 844).
  • said bus 830 can comprise a flag to characterize a transaction as a business transaction
  • said pers 832 can comprise a flag for personal transactions
  • said proj num 834 can comprise a flag for a particular project number.
  • “Joe Thompson” can characterize transactions as reimbursable or as a personal transaction based on which pin ID 820 he selects, even though the same bank account (said bank acc num 822) is charged for the transaction.
  • users of said financial transaction system 100 can select a characterization of a transaction, without regard to its funding source, at the point of checking out.
  • said pin offset 826 can comprise an encrypted code associated with a traditional PIN number used in financial transactions.
  • FIG. 8D illustrates said accounts table 806.
  • data about an account (identified by said bank acc num 822), a bank (which can comprise said bank ID 852) are stored with other account information such as zip codes (said account zip 854), transaction limits (said account limit 856), and account types (said account type 860).
  • Said accounts table 806 can comprise said bank pin offset 858 which can comprise the PIN offset associated with said bank acc num 822 as issued by said bank ID 852; that is, the original PIN as stored with by the card issuer may be stored as said bank pin offset 858.
  • FIG. 8E illustrates said bank table 808.
  • said bank table 808 can store data related to banks used in said financial transaction system 100.
  • said bank table 808 can comprise said bank ID 852, a name of each bank (said bank name 870), and a one or more fields for storing data related to each bank (here simplified as said bank info 872).
  • Several more fields may be necessary for the management of bank data such as contact info, unique transaction management instructions, contacts, or similar.
  • Said bank info 872 is used as a place holder for these additional fields which would be obvious to one in the art.
  • FIGs 9A and 9B illustrate said transactions table 902 and said itemized items 904.
  • each transaction associated with said ⁇ entries table 804 can be stored in said transactions table 902; and, where available, each item associated with each among said transactions table 902 can be stored in said itemized items 904.
  • FIG. 9A illustrates said transactions table 902.
  • Said transactions table 902 can comprise a unique ID for each transaction (said transactionid 910), a date and/or time for each transaction (said transaction date 912), a reference to a unique value in said ⁇ entries table 804 (said pin ID 820), a transaction result record (said result 914) and a location and/or merchant associated with the transaction (said location 916).
  • the data entered into said transactions table 902 is discussed further below.
  • FIG. 9B illustrates said itemized items 904.
  • Said itemized items 904 can comprise a unique ID for each itemized data row (said itemizationid 920), a reference to a unique ID in said transactions table 902 (said transactionid 922), a description of the line item (said item desc 924), a transaction cost for each item (said cost 926), a quality of each item purchased (said quantity 927), a tax for each line item (said tax 928), a subtotal of the cost times quantity plus tax spent on each line item (said subtotal 930), and a one or more line item characterization fields (which can comprise said customl 932a, said custom2 932b, said item category 934, and said user memo 936).
  • Said one or more line item characterization fields can comprise a one or more customized allocation fields (comprising of said customl 932a and said custom2 932b), an item by item characterization field (said item category 934) and a memo for users to annotate transactions (said user memo 936).
  • Figure 10 illustrates a system user form 1002.
  • said system user form 1002 can comprise a user information 1004 and a ⁇ entries for user 1006.
  • the parts of said system user form 1002 are illustrated further in said Figure 10.
  • Figure 11 illustrates a receipt 1 100.
  • said receipt 1 100 can comprise an itemization of the items associated with a transaction.
  • said itemization can be characterized by the data illustrated in Figure 11.
  • said financial transaction system 100 can comprise a system designed to aid consumers in avoiding the hassles of keeping up with a plurality of pieces of paper that they need to handle their books in their personal and business lives.
  • said financial transaction system 100 can help with IRS record keeping. As the IRS currently stands, it is the paper trail that they require for an audit of an individual's yearly taxes. It is also currently admissible under their rules to have a digital scan or digital photo of the receipt as proof of the person's transaction actually having taken place. In one embodiment, said financial transaction system 100 can centralize and simplify the digitization of these receipts by generating the files at the time the transaction is made and storing them on a secure, PCI compliant server thus allowing the individual to retrieve them later for line itemization or tracking of their expenses.
  • said financial transaction system 100 can take commerce a step further by allowing merchants to store all of their transactions on a merchant account on a server for bookkeeping purposes.
  • said merchant accounts will allow them to also add the service of ACH payment by way of a private network switch which will "trim the fat" of paying a percentage of transactions for processing credit cards; instead they can only pay a flat fee.
  • financial transaction system 100 systems will provide a number of features via web-based apps that will be both beneficial to merchants and consumers alike. This list will likely grow as time progresses, but for the time being is already rather robust and of value to different parties as follows.
  • said financial transaction system 100 can comprise advanced security features.
  • said financial transaction system 100 can comprise advanced security features.
  • through a variety of means such as email verifications, the use of LexisNexis, merchants checking ID's, test deposit verification, and standard identification checks already instituted by credit card processors such as CVV2 codes, this disclosure feels that this is very attainable goal. In the course of development, there may be newer, more novel approaches that crop up, but it will definitely be covered by the current standards that are instituted.
  • FIG. 12 illustrates a flow chart 1200 between a merchant 1202, a third party 1204 and an issuer 1206.
  • Said flow chart 1200 can comprise a step one 1208, a step two 1210, a step three 1212, a step four 1214, and a step five 1216.
  • said step one 1208 can comprise submitting and requesting an authorization of said transaction data from said merchant to said third party.
  • said transaction data can comprise an account number and a PIN.
  • said step two 1210 can comprise looking up said one among said one or more PINs and said account number in said data storage by said third party.
  • said step three 1212 can comprise authorizing said transaction data with said issuer associated with said transaction groups.
  • said step four 1214 can comprise sending an authorization approval back to said third party and to said merchant.
  • said step five 1216 can comprise characterizing said transaction data according said association between said one or more PINs associated and said one or more transaction groups in said data storage.
  • FIG. 13 illustrates a flow chart 1300 between a merchant 1202, a third party 1204 and an issuer 1206.
  • Said flow chart 1300 can comprise a step one 1308, a step two 1310, a step three 1312, and a step four 1314.
  • said step one 1308 can comprise submitting and requesting an authorization of said transaction data from said merchant to said third party.
  • said step two 1310 can comprise storing said itemized listing of items associated with said transaction data.
  • said step three 1312 can comprise authorizing said transaction data with said issuer associated with said one or more issuer accounts.
  • said step four 1314 can comprise sending an authorization approval back to said third party and to said merchant.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Computer Security & Cryptography (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

La présente invention concerne un système de traitement de transactions de comptes comprenant un compte ayant un numéro de compte stocké dans un stockage de données. Ledit numéro de compte est associé à un titulaire de compte ayant des informations de titulaire de compte et un ou plusieurs PIN. Ledit numéro de compte est géré par un tiers. Lesdites informations de titulaire de compte et ledit ou lesdits PIN sont stockés dans ledit stockage de données. Ledit ou lesdits PIN sont associés à un ou plusieurs groupes de transaction. Ledit ou lesdits groupes de transaction sont associés à un ou plusieurs comptes d'émetteurs associés audit titulaire de compte. Ledit ou lesdits comptes d'émetteurs sont chacun financés et gérés par un ou plusieurs émetteurs. Une ou plusieurs données de transaction sont associées à ladite ou auxdites transactions, et chacune comprend au moins un montant de transaction, ledit numéro de compte et un PIN parmi ledit ou lesdits PIN.
PCT/US2015/015079 2014-02-07 2015-02-09 Système et procédé de transaction financière WO2015120420A2 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201461937377P 2014-02-07 2014-02-07
US61/937,377 2014-02-07
US201461950831P 2014-03-10 2014-03-10
US61/950,831 2014-03-10

Publications (2)

Publication Number Publication Date
WO2015120420A2 true WO2015120420A2 (fr) 2015-08-13
WO2015120420A3 WO2015120420A3 (fr) 2015-11-12

Family

ID=53778619

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/015079 WO2015120420A2 (fr) 2014-02-07 2015-02-09 Système et procédé de transaction financière

Country Status (1)

Country Link
WO (1) WO2015120420A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106503996A (zh) * 2015-09-08 2017-03-15 Sk普兰尼特有限公司 基于web的支付业务提供设备、方法以及系统
CN107798541A (zh) * 2016-08-31 2018-03-13 苏宁云商集团股份有限公司 一种用于在线业务的监控方法及系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060123465A1 (en) * 2004-10-01 2006-06-08 Robert Ziegler Method and system of authentication on an open network
US9177314B2 (en) * 2006-08-14 2015-11-03 Chijioke Chukwuemeka UZO Method of making secure electronic payments using communications devices and biometric data
US9317850B2 (en) * 2010-04-05 2016-04-19 Cardinalcommerce Corporation Method and system for processing PIN debit transactions
CA2864171C (fr) * 2012-02-15 2020-06-23 Cardinalcommerce Corporation Plateforme d'authentification pour des emetteurs de debit a numero d'identification personnel (pin)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106503996A (zh) * 2015-09-08 2017-03-15 Sk普兰尼特有限公司 基于web的支付业务提供设备、方法以及系统
EP3142055A1 (fr) * 2015-09-08 2017-03-15 SK Planet Co., Ltd. Appareil, procédé, système de fourniture de services de paiement sur le web et support d'informations non transitoire lisible par ordinateur mémorisant un programme informatique enregistré en son sein
CN107798541A (zh) * 2016-08-31 2018-03-13 苏宁云商集团股份有限公司 一种用于在线业务的监控方法及系统
CN107798541B (zh) * 2016-08-31 2021-12-07 南京星云数字技术有限公司 一种用于在线业务的监控方法及系统

Also Published As

Publication number Publication date
WO2015120420A3 (fr) 2015-11-12

Similar Documents

Publication Publication Date Title
US11605066B2 (en) Physical, logical separation of balances of funds
US20210248584A1 (en) Offline bill splitting system
US10885515B1 (en) System and method for canceling a payment after initiating the payment using a proxy card
US10460395B2 (en) Graphical user interface for tracking transactions
US11347744B2 (en) Data management device, communication system and methods for tagging data in a data table and triggering automated actions
US9355394B2 (en) Systems and methods of aggregating split payments using a settlement ecosystem
AU2010246280B2 (en) System and method for providing consumer tip assistance as part of payment transaction
US11315091B2 (en) Method and means for social network payments
US9224141B1 (en) Encoding a magnetic stripe of a card with data of multiple cards
EP3479322A2 (fr) Séparation physique et logique de soldes de fonds
US20140310153A1 (en) Systems and methods for mobile device financing
US20110238473A1 (en) Alternate mobile payment service
US11244299B1 (en) Location-based transaction completion
US20230013189A1 (en) Real-time transaction and receipt processing systems
WO2016061349A1 (fr) Procédé et système de paiement du fond de la pyramide
WO2015120420A2 (fr) Système et procédé de transaction financière
AU2015201865A1 (en) System and method for providing consumer tip assistance as part of payment transaction
AU2008329649B2 (en) Control system arrangements and methods for disparate network systems
CA2981385C (fr) Dispositif de gestion de donnees, systeme de communication et procedes pour marquer des donnees dans une table de donnees et declencher des actions automatiques
JP2021026776A (ja) 資金移動管理システム及び該システムによる資金移動管理方法並びに該方法を実行するためのプログラム
WO2009070716A1 (fr) Agencements de système de commande et procédés pour des systèmes de réseaux disparates

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15746016

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15746016

Country of ref document: EP

Kind code of ref document: A2