Some Of The Common Building Blocks of Payment APIs

I'm taking a look at the world of payment APIs right now. As with all my other monitoring of the API space, I am only looking for the best approaches, by the most interesting companies in the space--I don't have time to track on everything, 

I am looking to take a snapshot of the payment API space, understand who the key players are, and how they are delivering valuable payment API resources that developers are actually using. Last week I puled together 38 payment APIs that I'm watching, and this week I am spending some time going through their sites, looking for what I'd consider to be some of the common building blocks of payment APIs. 

Currently I have 50 building blocks I found across these 38 payment providers:

Merchant Account - Creation, management and integration with merchant accounts that are required to process credit cards.

Bank Account - Integration with existing bank accounts, for inclusion in payment workflows.

Processor / Gateways - Access to multiple payment processors and gateways in multiple countries.

Currencies - Ability to conduct transactions in multiple currencies.

Credit Card Transactions - The option to process major credit cards.

ACH Transactions - The option to process transactions over the ACH network.

Checks / Wire Transactions - The option to do bank to bank, wire and check transactions.

Cash Transactions - The option to process major credit cards.

Virtual Transactions - The option to accept transactions for credits via virtual accounts.

Aggregate Transactions - Tools for performing multiple transactions at once.

Credit Card Reader - A physical credit card reading device.

Credit Card Scan / Picture - A mobile phone scan or picture of a credit card.

One Click / One Touch / Instant Buy - The ability to enable single action transactions.

Recurring Payments - The ability to perform recurring or subscription based transactions.

Prepayments - The ability to setup payment(s) prior to designated payment date.

Metered Payments - Payments based upon some metered usage of a resource.

Estimates - Estimations of payments, with payment handling at designated time.

Invoices - Physical or online invoicing of customers as request for payment.

Mobile Billing - The ability to perform transaction against mobile users monthly phone bill.

Social Payments - An option for making and accepting payments via social platforms like Facebook and Twitter.

Email Payments - Tools for sending and receiving transactions via email.

SMS Payments - Tools for sending and receiving transactions via SMS.

Carts - Ready to go online shopping cart solutions to support payment services.

Checkout - Ready to go checkout pages, to support payment services.

Forms - Embeddable HTML and JavaScript based forms to conduct transactions.

Buttons - Embeddable HTML and JavaScript buttons to initiate transactions.

Marketplace - The ability to facilitate marketplace style transactions between sellers and vendors.

Fraud Protection - Tools and services that assist developers in preventing payment fraud.

PCI Compliance - Tools and services that help developers achieve PCI compliance.

Encryption - Providing necessary encryption tools and services to protect communications.

Sandbox - A safe environment for developers to develop applications against, ensuring quality of service in production environments.

Webhooks - Registering of developer provider URLs for making HTTP calls when specific events occur.

Push Notifications - A push notification framework for developers to use when delivering push features in their applications.

Bar-codes - The ability to generate bar-codes that represent potential physical or virtual transactions.

Products - Separate systems for managing products that transactions will be part of.

Orders - Separate systems for managing orders in which transactions will be part of.

Customers - Separate systems for managing customers who perform transactions.

Coupons - Separate systems for coupons which can be applied against transactions

Loyalty - Separate systems for managing customer loyalty programs.

Expenses - Separate systems or managing expenses that involve transactions.

Time Tracking - Separate systems for tracking time associated with transactions.

Cards - The ability to issue physical or virtual gift, membership and other types of cards.

JS Libraries - Supporting JavaScript libraries that provide embeddable integration with payment services.

Mobile SDKs - Supporting mobile SDKs for iOS, Android, Windows and others, to facilitate mobile payments.

On-Premise - The ability to deploy payment services on-premise, keeping transactions secured locally.

Cloud - The ability to deploy payment services in the clouds, with centralized security.

3rd Party Shopping Carts - Integration options for popular 3rd party shopping carts.

Platform as a Service (PaaS) Integration - Integration with popular PaaS platforms like SalesForce and Google Apps.

Frameworks - Integration with popular programming frameworks like Backbone and Angular.

Automation - Integration with leading API automation platforms like Zapier and IFTTT.

As with all of my research, this is ongoing. My hopes is to better educate myself (and you too), about the payment API sector, which I consider a pretty critical aspect of the overall API economy.

If there are any building blocks that you think should be included in my research, let me know at @kinlane, and I'll see about including.