Method for performing transactional communication using a universal transaction account identifier assigned to a customer
First Claim
1. A transactional communication method using transactional messages delivered over a communication network (CN), wherein the CN comprises a routing database;
- the routing database comprising at least a first field storing a network identifier (NI) and a second field storing a network address (NA);
the routing database providing resolution services by receiving from a remote terminal a query containing the NI and retrieving the NA from the second field corresponding to the received NI wherein the retrieved NA is further used to locate a connection endpoint;
the CN implementing a messaging protocol or request-response session messaging protocol (MP) wherein MP messages are created using MP messaging syntax rules;
wherein transactional messages are delivered to a service provider or processing center authorized by the service provider (SP) managing customer accounts and processing the transactional messages while providing services to a customer;
the method comprising;
creating, using at least one of one or more hardware processors, universal transactional account (UTA) identifiers, each of the UTA identifiers comprising a unique string of symbols or characters;
assigning, using at least one of the one or more hardware processors, each of the UTA identifiers to the customer and associating the UTA identifier with a customer account corresponding to the customer;
assigning, using at least one of the one or more hardware processors, the NA further referred to as an account NA to the SP;
receiving, using at least one of the one or more hardware processors, the UTA identifier from a first remote terminal, at a time subsequent to creation of the UTA identifier, and storing the UTA identifier into the first field and the account NA into the second field of the routing database;
creating, at a second terminal coupled to the CN and using at least one of the one or more hardware processors, an MP message containing at least the UTA identifier and a value;
sending, by the second terminal and using at least one of the one or more hardware processors, the UTA identifier for resolution to the routing database using the CN and retrieving the account NA from the second field of the routing database corresponding to the received UTA identifier;
transmitting, via the CN and using at least one of the one or more hardware processors, the created MP message from the second terminal to the SP at the retrieved account NA; and
receiving, at the SP and using at least one of the one or more hardware processors, the transmitted MP message and parsing the MP message to determine the UTA identifier and the value.
0 Assignments
0 Petitions
Accused Products
Abstract
Methods, systems, computer data signals, recordable media and methods of doing business for wireless or wired network communication between network resources each having a unique telephone number associated therewith, including, among other feature, forming a primary number file (PNF) comprising a uniform telephone address (UTA) which has a telephone number associated with a network resource.
User-friendly and seamless payment procedure is provided wherein payer or payee only need to know accordingly the payee or payer UTA number to allow transaction and seamless payment routing between payer and payee bank accounts. Unified approach is allowed wherein financial institution also are networking Targets having UTA numbers assigned for them and the financial institution can receive Fund Transfer Agreement or Deal Agreement from networking Targets, authenticate payer using particular Target UTA and apply the payment from this particular UTA bank account.
Internet Settlement Architecture provides unique implementation of a clearing routes ranging by using cost command for EEP; and the ranging in turn allows the routing management by using cost and time user preferences, thus allowing operational cost management implementation for financial institutions and their respective customers using cost tracing command. On-line, multi-tier and multi-route clearing infrastructure and payment services provide seamless and transparent payment cost and payment routing management, enabling End-to-End payment Straight Through Processing (STP). Network specific identifiers (such as UTA, ZUTA and others) and the network specific software user interfaces (phone user interface and only numeric keyboards) may be used to navigate and manage the Internet Settlement Infrastructure enabling seamless payment addressing and clearing. Users are enabled to address payments without a need to know payee'"'"'s banking details and payment routing information providing End-to-End account details resolution and Straight Through Processing for payment clearing services. Payment processing is diverted into online communication. Extensive use of the PKI trusted sources enables trusted financial account mappings allowing secure payment and clearing environment. The use of Attribute Certificates containing only payer network address mapped to its DCF network address allows filling in the DNS system database with the trusted mapping information avoiding the need to disclose the real banking details of the payee to a public. The use of existing DNS technology for resolution of trusted mapping information allows seamless gathering of banking routing information enabling on-line straight through processing.
-
Citations
30 Claims
-
1. A transactional communication method using transactional messages delivered over a communication network (CN), wherein the CN comprises a routing database;
- the routing database comprising at least a first field storing a network identifier (NI) and a second field storing a network address (NA);
the routing database providing resolution services by receiving from a remote terminal a query containing the NI and retrieving the NA from the second field corresponding to the received NI wherein the retrieved NA is further used to locate a connection endpoint;
the CN implementing a messaging protocol or request-response session messaging protocol (MP) wherein MP messages are created using MP messaging syntax rules;
wherein transactional messages are delivered to a service provider or processing center authorized by the service provider (SP) managing customer accounts and processing the transactional messages while providing services to a customer;
the method comprising;creating, using at least one of one or more hardware processors, universal transactional account (UTA) identifiers, each of the UTA identifiers comprising a unique string of symbols or characters; assigning, using at least one of the one or more hardware processors, each of the UTA identifiers to the customer and associating the UTA identifier with a customer account corresponding to the customer; assigning, using at least one of the one or more hardware processors, the NA further referred to as an account NA to the SP; receiving, using at least one of the one or more hardware processors, the UTA identifier from a first remote terminal, at a time subsequent to creation of the UTA identifier, and storing the UTA identifier into the first field and the account NA into the second field of the routing database; creating, at a second terminal coupled to the CN and using at least one of the one or more hardware processors, an MP message containing at least the UTA identifier and a value; sending, by the second terminal and using at least one of the one or more hardware processors, the UTA identifier for resolution to the routing database using the CN and retrieving the account NA from the second field of the routing database corresponding to the received UTA identifier; transmitting, via the CN and using at least one of the one or more hardware processors, the created MP message from the second terminal to the SP at the retrieved account NA; and receiving, at the SP and using at least one of the one or more hardware processors, the transmitted MP message and parsing the MP message to determine the UTA identifier and the value. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30)
- the routing database comprising at least a first field storing a network identifier (NI) and a second field storing a network address (NA);
Specification