Point of Transaction 301 (elective. PoT 201 and Cloud Payments 210 prerequisites): The Network is the Terminal

As complexity, and commensurate value, in processing payments moves to the network platform, or “cloud,” endpoints will increasingly access that value through flexible thin-client interfaces. For remote payments this may take the form of API-enabled alias-registration and checkout services. For physical retailers this may take the form of IP-enabled PoS terminals and self-serve kiosks. (for advanced discussion, see Graduate Studies elective PoT 520: Applied Convergence Theory and the Alias Engine as Mobile Point of Sale Processor. This course to be offered in the Spring).

Point of Transaction 301 Lesson 1: PoT Landscape


Rules, guidelines, processing deployment, network provisions, and much of the product capability delivered by the current payments business have been developed, maintained, managed, and propagated by the companies that deliver payments to consumers. (Read More)

Point of Transaction 301 Lesson 2: PoT Evolution


Somehow, however, innovations in consumer payment have been making it to the point of transaction.  How exactly? Or should the question be “where?” (Read More)

Point of Transaction 301 Lesson 3: PoT Implications


All that remains is for the payments applications managed by the major online checkout engines to be ported to the physical point of sale. With IP-enabled points of sale and software services driving them, that’s a fairly easy technical leap. (Read More)


Point of Transaction 301: Exam


Time to click a few radio buttons on a web page and tell us what you think of the potential convergence of eCommerce tools and stakeholder motivations at the physical Point of Transaction. (Take Quiz)



Point of Transaction 301: Exam Results


The exams have been scored. Here is a round-up of how PYMNTS U. participants answered on the Point of Transaction 301 exam. (View Results)