Currently purchasing cards apparently rely on close ties with issuers as
well as supplier support.

.PAY (*), an "input specification" to a proposed OASIS payment
standard track, changes this by making each party do what they are
best at which means:
- Issuers/Banks pay
- Suppliers deliver goods or services
- Employers control/authorize/archive what their employees do

How does this work?
1. The merchant sends a "rich" transaction request to the buying organization
2. The purchasing-server authenticates the purchaser
3. The purchasing-server checks the Level III-like items and authorizes if ok
4. The purchasing-server sends the transaction request to a PSP/bank fo
    fulfillment using ACH, credit-cards, debit-cards, etc.
5. The PSP/bank returns the complete transaction
6. The purchasing-server sends this back to the merchant
(there are some minor deviations but the principle is as above)


      The net result is that the entire concept of a purchasing card
      disappears, and a real-time B2B-transaction takes its place. 


And how about those non-web-based transactions?  Well,
unfortunately we will have to wait another 5 years or so
until the phone-makers heve recovered from the current
recession and see some light in the tunnel.

*) Reading only: http://buyer.x-obi.com/dotpaybuyer/faq.html
    Running .PAY: https://buyer.x-obi.com/dotpaybuyer/buyer

cheers,
Anders



Reply via email to