Skip to content
This repository has been archived by the owner on Sep 11, 2022. It is now read-only.

Latest commit

 

History

History
45 lines (34 loc) · 1.71 KB

Interface-Keys.md

File metadata and controls

45 lines (34 loc) · 1.71 KB

Conventional keys for payment interfaces

Conventional values for payment interfaces (i.e. APIs). Typically PSP names plus a postfix if they provide multiple independent APIs.

THIS IS NOT A LIST OF PARTNERS, PREFERRED PROVIDERS OR SOME OTHER RECOMMENDATION OR BUSINESS STATEMENT. It just serves to reserve names for companies that are or could be integrated privately or publicly in the future.

To be used in:

  • commercetools payment object "paymentMethodInfo.paymentInterface" property

Formal convention:

  • Please prefix white-labeled / branded but identical APIs with the name of the white label offering and separate with a dash. E.g. PAY_ON-ARVATO. This makes it easier to map the transaction request to an interface implementation.
  • [A-Z,_,0-9]*, minus-hyphen reserved for branded variants of the same interface.
  • Try to avoid shortcuts.
  • Keep the list sorted alphabetically

Special Values

Key Name
INTERNAL catch-all for payments done by the merchant manually. Alternatively a custom value can be used that is not in the list below.
EXAMPLE reserved for examples in documentation
TEMPLATE reserved for the specification templates

Interfaces (i.e. Providers & Gateways per API that is to be implemented)

(in alphabetical order)

Key Name Website
ADYEN
AUTHORIZE_NET
BRAINTREE Braintree (a PayPal company) http://www.braintree.com
PAYMILL
PAYONE PAYONE http://www.payone.de
PAYPAL PayPal (TODO incl. PayPal Pro? ) http://www.paypal.com
SOFORT TODO is Klarna a separate API?
STRIPE Stripe https://stripe.com
WIRECARD http://www.wirecard.com/