Payment API Basics

Common use cases & payment provider tech

This preso has been prepared as supplementary material to a

2014 SXSW Open Discussion on

Payment APIs in the US

Common Payment Use Cases

Payments are used by websites & mobile apps

in a variety of ways:

• Shopping Cart / Checkout

• Recurring / Subscription Payments

• P2P payments

• Donations

• Split or parallel payments

• Chained payments

• Mass payments

• Crowdfunding: donor to platform, platform to

campaigner

Payment providers tech

Payment providers provide developers various

technologies to integrate payments into sites

and apps

• Buttons, Widgets, Plugins, Web Hooks

• APIs

o REST

o SOAP

• SDKs / Libraries

o variety of languages

o mobile: Android, iPhone, Windows etc.

Key Payment API Providers in US

Amazon: http://services.amazon.com/amazon-payments

Authorize.Net: http://developer.authorize.net/api

Balanced: https://docs.balancedpayments.com/current/api

BancBox: http://www.bancbox.com/api/index

Braintree: https://www.braintreepayments.com/developers

Chirpify: https://chirpify.com/developers

Dwolla: https://developers.dwolla.com

PayPal: https://developer.paypal.com

Stripe: https://stripe.com

Amazon Integration Methods

Cart Provider Plug-in

Set up Amazon Payments using your own cart or an eCommerce provider’s

tools and plug-ins.

HTML Button The Checkout button is HTML code that sets up a button image and also describes the item, including

its SKU, price, title, shipping and tax rates, and promotions. You generate the Checkout button

automatically using the Create Checkout Button function, or you create the button yourself based

on button creation requirements.

API Integration Amazon Payments provides a set of widgets and APIs that you embed on your site and integrate with

your back-end systems. Customers purchase on your website with the payment and shipping

information stored in their Amazon accounts. Once the buyer completes the purchase, Amazon

APIs provide you the customer’s name, email, and shipping address, so that you can fulfill the

order and authorize, capture, and refund payments. The only information you pass to Amazon is a

request to authorize payment of the order amount

Amazon Flexible Payments Service

Multiple or recurring payments between a buyer and a seller

for e-commerce, digital content, donations, or services.

• Payment authorization—Buyers must authorize payments for you to be able

to charge them. Buyers log in to Amazon Payments and agree to make the

payment using a specified payment method.

• Payments—Transfer money from the buyer's account to the seller's.

• Recurring-use payment tokens—A buyer authorizes a recurring payment

token once, and thereafter it is charged a specific amount at regular intervals

until the token expires.

• Multi-use payment tokens—A buyer authorizes a multi-use payment token

once but it can be used repeatedly according to its constraints.

• Seamless mobile payment support—Amazon FPS automatically supports

payments within mobile web browsers.

• Notifications—Get notified automatically when transactions succeed or fail.

• Refunds—Refund the money from a successfully completed transaction.

• Cancellation of payment tokens—Cancel any of your payment tokens at any

time.

Authorize.net integration methods

Authorize.net

Balanced payment use cases

Braintree payment use cases

• Shopping cart, billing, or ecommerce platform

o Braintree only to accept payments to a single merchant account.

• Recurring or subscription billing

• Discounts and Add-ons to create promotional periods or rewards

Chirpify Use Cases

Buy, sell, donate, fundraise and pay

instream on Twitter, Instagram & Facebook

Dwolla payment integration

methods

Stripe* Payment Use Cases

• Charge Credit & Debit Cards

• Subscriptions

• Metered billing

• Coupons

• P2P

• Donations

* Stripe and Stripe Connect

Stripe website payment

PayPal Payment Use Cases

• Selling Physical or Digital Goods

• Subscriptions

• Metered billing

• Coupons, Rebates

• P2P

• Donations

• Affiliate Fees

• Invoicing

• Admission Fees

• Group Dues

• Virtual Currencies

• Shared payments

Use Case Example

Authorize.net Balanced Braintree

• PHP

• Ruby

• Java

• C#

• Android

• iOS

Amazon SDKs

• PHP

• .NET

• Java

• Android

• iOS

Stripe

• .js (browser)

• Python

• Ruby

• PHP

• Java

• iOS

• Android

• PHP

• Ruby

• Java

• Python

• Node

• Perl

• iOS

• .js (browser)

Dwolla

• PHP

• Ruby

• Java

• Python

• Node

• Perl

• iOS

• Scala

• Clojure

• PHP

• Ruby

• Java

• .Net

• Python

• Node

• Perl

• Android

• iOS

• Windows Phone

• .js (browser)

PayPal

• PHP

• Ruby

• Java

• Python

• Node

• .NET

• iOS

• Android

Appendix

• Payment Business Positioning by IDATE

• 2013 Mobile Payments & Banking by FirstPartner

• UK & Global Payments Landscape by Juniper Research