ao link
Affino

Payment Gateways Overview

 

Overview

Affino supports 11 Payment Gateways, these are:

  • Affino (Purchase Order)
  • GoCardless
  • Pay360 - Hosted
  • PayPal - Standard
  • PayPal - Website Payments Pro
  • PayPal - Website Payments Pro (iframe)
  • Realex Payments
  • Sage Pay
  • Stripe
  • Worldpay

Notes on SSL and PCI Compliance

Recently it has become best practice to have entire websites under SSL - it improves SEO as well as Security - so All sites, let alone Ecommerce sites should have SSL by default.

 

There have also been some quite recent changes to PCI Compliance, which means less payments being processed onsite on Affino Sites, and more transactions being passed on to external payment gateways.

 

The requirements for Ecommerce PCI have ramped up quite significantly recently, and are not compatible with an integrated platform approach like Affino - whose core benefit is in its single-sourcing, single customer view and seamless customer journeys and analysis.

 

For PCI compliance Ecommerce has to be a wholly separated and stand-alone functionality - which in these terms means that depending upon requirements, most payment transactions will be handled away from Affino, and there will be less seamless integration in that regard.

 

The hand-off process will need to be clearly delineated and identified to fulfil all the new PCI requirements.

Payment Gateway Setup

You will need to obtain most of the keys/secrets from the service provider (i.e Stripe).

 

Typical fields are:

  • Name - Enter Reference Name
  • Gateway Type - i.e. Stripe
  • Run Mode: Live or Test (note: you always start off in Test Mode, and go to Live at launch; you will often need different credentials / keys for this)
  • Publishable Key - obtained on the payment service providers' dashboard
  • Secret Key - obtained on the payment service providers' dashboard
  • Webhook URL - Copy-paste the Webhook URL into the payment provider to generate the Webhook Signing Secret
  • Webhook Signing Secret - obtained on the payment service providers' dashboard
  • API Username - The API Name you have registered (often in the form of an email address)
  • API password - Usually 10 digit key (e.g. 1234561327)
  • Signature - Enter the Signature provided
  • Live: Tick to make Payment Gatewat active

Added to the above, each payment gateway has specific options related to gifts, subscriptions and taxes.

 

NOTE - Payment Gateways are assigned to Payment Methods, which in turn are applied on Store Profiles.

 

Troubleshooting

The most common issues to do with Payment Gateways are as follows:

  • Wrong Credentials - Username | Password | Signature
  • Payment Gateway or Payment Method is not set to Live
  • Incorrect Run Mode Selected - does not match Licence Key
  • Wrong Access Token / Webhook URL / Webhook Secret / API Key
  • No active SSL on Website / Server

Did you find this content useful?

Thank you for your input

Thank you for your feedback

Driving business at some of the world's most forward thinking companies

Our Chosen Charity

Humanity Direct