Open web payments
Download as PPTX, PDF5 likes9,345 views
The document proposes an open standard called Open Web Payments (OWP) to create consistency across online payment platforms. OWP would define common APIs, data models, and extensions to allow interoperability. It describes representing transactions as entries in the Atom format, with extensions to include payment details. It provides examples of how a grocery application might use OWP for an online purchase.
Open web payments
- 1. Open Stack For Open Web PaymentsPraveen AlavilliRay Tanaka
- 3. State of the Online Payments
- 6. A Case for Open Web Payments
- 7. Open Stack for Open Web Payments
- 8. Next steps / Call for ActionPayments – a look back !EFT1970sPayPal 1998Barter100,000BC – 3,000BCCommodity3,000BC – 650BCCash 650BC - NowCredit1950 - NowPayment Gateways1995eCommerce1981 (1984)
- 9. There are many players…
- 11. Payment NetworksCredit/Debit Card Networks
- 12. ACHsome gateway
- 13. Essential components of Online PaymentsAuthentication – Who are you?Authorization – How much do you want to charge?Payment Instrument – What are you using to pay?
- 14. MotivationReduce FrictionInteroperability across multiple payment platformsPCI Compliance
- 15. Open Web PaymentsConsistency APIs across platformsSingle model for authorization, payments and transactionsSupport for real and virtual currenciesSingle, extensible document model
- 16. What we’re not covering (for now)Payment data portability (Merchant + Consumer)Client, user and receiver account managementDirect integration with financial institutions
- 17. Transactions AS THE CORE
- 20. The closest sibling on the web !
- 21. Feeds – web resources
- 22. Feeds – A closer Look<entry> <id>tag:blogger.com,1999:blog-754260340057137512.post-2123024611142172293</id> <published>2010-03-11T13:46:00.001-05:00</published> <updated>2010-03-11T13:46:50.788-05:00</updated> <category scheme='http://www.blogger.com/atom/ns#' term='wallet'/> <title type='text'>Fueling the Wallet.Next</title> <content type='html'>……</content> <link rel='alternate' type='text/html' href='http://whyidentity.blogspot.com/2010/03/fueling-walletnext.html' title='Fueling the Wallet.Next'/> <link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=754260340057137512&postID=2123024611142172293' title='0 Comments'/> <author> <name>Praveen</name> <uri>http://www.blogger.com/profile/10778095038892167017</uri> <email>noreply@blogger.com</email> </author> </entry>
- 23. Transactions – A closer lookDate
- 24. Sender – Payer, Buyer, Customer
- 25. Receiver - Friend, Merchant, Seller, Some Service Provider)
- 26. Type of Payment – instant, subscription, pre-pay, post-pay, refund, agreement to pay in future
- 27. Reason for payment – purchase, personal, gift, etc.
- 28. Category – Restaurant, Merchandise, Travel, etc.
- 31. Status
- 32. Application/Client– Web Site, Mobile Application, etc.Mapping Transaction ATOM Entry
- 33. Open Web Payments ExtensionsFilling in the missing pieces in the puzzle
- 34. ATOMAn XML-based Web Content and metadata syndication format
- 35. POCOSimple, Portable and Standard Contact schemaShipping & Billing Address -- poco:address
- 36. OAUth 2.0Request (Client) Authentication End User Authorization (Transaction Approval)Little sketchy !
- 37. ATOMPubApplication level protocol for publishing and editing web resources
- 38. So what’s our open stack ?TransactionHistoryApplicationConsumerApplicationMerchantApplicationPoCoOpen Web PaymentOpenSearchOpenWebPaymentsStackAtomAtomPubOAuthhost-meta/WebFingerPayments Provider
- 39. How does this work ?
- 40. Transactions represented by an Entry<entry> <id> -unique-transaction-id- </id> <title type=“text”> -short desc of transaction- </title> <published> -transaction creation date- </published> <author> <name>-name of the app-</name> <uri>-app url-</uri> <id>-unique-app-identifier-</id><OWP:consumer_id>-id-</OWP:consumer_id> <OWP:consumer_transaction_id>-txn-id-</OWP:consumer_transaction_id> </author> <category scheme=“-iri-” term=“-category-” label=“-label-”/> <link rel=“alternate” type=“text/html” href=“-url-to-receipt-”> <content type=“xhtml”>-detailed-desc-</content> <OWP:transaction>…</OWP:transaction></entry>
- 43. http://owp-api.net/schema/1.0/actions/PrePayAgreementhttp://owp-api.net/schema/1.0/actions/PostPayAgreementPrior agreement between Sender and ReceiverPrePay Agreement results in money movementPostPay Agreement results in no money movementRequires end user authorization
- 44. http://owp-api.net/schema/1.0/actions/PrePayhttp://owp-api.net/schema/1.0/actions/PostPayPrePay is for transaction recording purposes – no money movementPostPay is for merchant credit functionality – no money movement
- 45. http://owp-api.net/schema/1.0/actions/DelegatedPaymentAgreementDelegate access to the application to make Payments on behalf of the userRequires end user authorization.Allows to set max amount allowed, max number of payments, frequency, start/end dates, and receivers.
- 46. http://owp-api.net/schema/1.0/actions/HoldFundsNo money movement but funds are held in for a specific receiverRequires end user authorizationAllows to set amount, and expiry.
- 47. http://owp-api.net/schema/1.0/actions/PayFor money movement from sender to receiver.In most cases requires end user authorization.No explicit user authorization required when used with a TransactionId for previously held funds or Delegated Payment access or when sender is same as Client
- 48. Authentication and AuthorizationOAuth 2.0 ?
- 50. Need Access Token ?
- 51. How to do dynamic user approvals ?
- 52. Implicit and User FederationsDiscoveryhttps://service.provider.com/.well-known/host-meta<?xml version='1.0' encoding='UTF-8'?><XRD xmlns='http://docs.oasis-open.org/ns/xri/xrd-1.0' xmlns:hm='http://host-meta.net/ns/1.0'> <hm:Host>service.provider.com</hm:Host> <Link rel='http://owp-api.net/1.0/provider' href='http://service.provider/openpayments'></XRD>
- 53. API
- 54. Putting this all together – a grocery app<entry> <id>https://paymentsservice.com/owp/transaction/id/12345678</id> <published>2010-07-15T01:46:00.001-05:00</published> <updated>2010-07-14T08:00:50.788-05:00</updated> <category scheme='http://openpayment.org/atom/ns#' term='groceries' label="Groceries"/> <category scheme='http://www.blogger.com/atom/ns#' term='store' lavel="Safeway"/> <title type='text'>Groceries from Safeway</title> <content type='html'> <ul><li>2% Milk</li><li>2 Gallons Water</li><li>2lb Tomatos</li></ul> </content> <link rel='alternate' type='text/html' href='http://www.safeway.com/order-status' title='Safeway online Store'/> <author> <name>Your Grocery App</name> <uri>http://your-grocery-app.com</uri> <email>support@yourgroceryapp.com</email><OWP:consumer_id>api-caller:1234</OWP:consumer_id> </author>
- 55. Putting this all together – a grocery app <OWP:transaction> <OWP:action>http://owp-api.net/schema/1.0/object-types/Pay</OWP:action> <OWP:entity> <OWP:entity-type>http://owp-api.net/schema/1.0/entity-types/Sender</OWP:entity-type> <name>Praveen Alavilli</name><uri>https://me.paypal.com/id/1234567</uri><email>praveen@x.com</email> <OWP:funding-type>http://owp-api.net/schema/1.0/funding-types/Bank</OWP:funding-type> <OWP:funding-type>http://owp-api.net/schema/1.0/funding-types/CreditCard</OWP:funding-type> <OWP:funding-type>http://owp-api.net/schema/1.0/funding-types/DebitCard</OWP:funding-type> </OWP:entity> <OWP:entity> <OWP:entity-type>http://owp-api.net/schema/1.0/entity-types/Receiver</OWP:entity-type> <name>Safeway Store</name><uri>https://biz.paypal.com/id/7654321</uri><email>support@safeway.com</email> <OWP:amount currency="USD">25.50</OWP:amount> <OWP:payment-type>http://owp-api.net/schema/1.0/payment-types/Goods</OWP:payment-type> </OWP:entity> <OWP:entity> <OWP:entity-type>http://owp-api.net/schema/1.0/entity-types/Receiver</OWP:entity-type> <name>Your Grocery App</name><uri>https://biz.paypal.com/id/432156</uri><email>support@yourgroceryapp.com</email> <OWP:amount currency="USD">2.00</OWP:amount> <OWP:payment-type>http://owp-api.net/schema/1.0/payment-types/Services</OWP:payment-type> </OWP:entity> </OWP:transaction></entry>
- 56. Digital Goods app – using Pre-Pay<entry> <id>https://paymentsservice.com/owp/tranaction/id/2123024611142172293</id> <published>2010-07-15T01:46:00.001-05:00</published> <updated>2010-07-14T08:00:50.788-05:00</updated> <category scheme='http://owp-api.net/atom/ns#' term=’coins' label=”Coinsville Coins"/> <title type='text'>Buying coins on Coinsville</title> <content type='html’>PrePay for Coinsville</content> <link rel='alternate' type='text/html' href='http://coinsville.com/account' title=’Coinsville Account Page'/> <author> <name>Digital Goods App</name><uri>http://digitalgoodsapp.com</uri> <email>support@digitalgoodsapp.com</email> <OWP:consumer_id>api-caller:654321</OWP:consumer_id> </author> <OWP:transaction><OWP:action>http://owp-api.net/schema/1.0/object-types/PrePayAgreement</OWP:action> <OWP:entity> <OWP:entity-type>http://owp-api.net/schema/1.0/entity-types/Sender</OWP:entity-type> <name>Praveen Alavilli</name><uri>https://me.paypal.com/id/1234567</uri><email>praveen@x.com</email> <OWP:funding-type>http://owp-api.net/schema/1.0/funding-types/Gold</OWP:funding-type> <OWP:amount currency=”bar">2</OWP:amount> </OWP:entity> </OWP:transaction></entry>
- 57. Digital Goods app – recording payment<entry> <id>https://paymentsservice.com/owp/tranaction/id/45402461154323434234</id> <published>2010-07-15T01:46:00.001-05:00</published> <updated>2010-07-14T08:00:50.788-05:00</updated> <category scheme='http://owp-api.net/atom/ns#' term=’coins' label=”Coinsville Coins"/> <title type='text'>Purchase digital sword</title> <content type='html’>Blazing sword</content> <link rel='alternate' type='text/html' href='http://coinsville.com/order' title=’Coinsville Order Portal'/> <author> <name>Digital Goods App</name><uri>http://digitalgoodsapp.com</uri> <email>support@digitalgoodsapp.com</email> <OWP:consumer_id>api-caller:654321</OWP:consumer_id> </author> <OWP:transaction> <OWP:action>http://owp-api.net/schema/1.0/object-types/Pay</OWP:action> <OWP:entity> <OWP:entity-type>http://owp-api.net/schema/1.0/entity-types/Sender</OWP:entity-type> <name>Praveen Alavilli</name><uri>https://me.paypal.com/id/1234567</uri><email>praveen@x.com</email> <OWP:refTransactionId>https://paymentsservice.com/owp/tranaction/id/2123024611142172293</OWP:refTransactionId> </OWP:entity> <OWP:entity> <OWP:entity-type>http://owp-api.net/schema/1.0/entity-types/Receiver</OWP:entity-type> <name>Digital Sword Seller</name><uri>https://biz.paymentprovider.com/id/9832434</uri><email>support@sword.com</email> <OWP:amount currency=”bars”>0.25</OWP:amount> <OWP:payment-type>http://owp-api.net/schema/1.0/payment-types/Services</OWP:payment-type> </OWP:entity> </OWP:transaction></entry>
- 58. Next StepsJoin the community and help in driving the spec
- 61. Validate the document model
- 62. Explore more use cases
- 65. Payment PortabilityQ & A ?Contact us: @ppalavilli & @rtanakahttp://groups.google.com/group/owp-api
Editor's Notes
- #5: A very important result of this is that a developer has to learn, code and deploy different integrations with each and everyone separately. It’s just painful.