Introduction

Building exceptional payments forms is no mean feat, little things can have large impacts on the user experience. Agreeing on a great payment flow is a challenge for everyone running an online business, even harder when they want to consider payment from from multiple starting points like Salesforce and digital invoices.


Many businesses now demand multiple starting points to accepting payments, these might include: Over the phone, online via public websites, online via private communities, at events etc. Importantly they want the user experience to remain consistent.


We’ve developed payment pages that take into account all the best practice we can find and added a little new thinking to cater for a flexible and dynamic integration required by Salesforce customers.



Key Considerations


1. Generating a Paypage

Paypages are only available once an Asperato ONE record (Payment or Authorisation) has been created in Salesforce. These records generate the URL related to the paypage (Checkout screen), it is this URL that you have to distribute to your customer to complete the payment.



2. Controlling Paypage content

When you create the Asperato ONE record, the data you populate and choices you make will affect how the Paypage URL performs and what data it presents to your customer.  Further details here:

https://asperato.github.io/docs/templates/#template-features


3. Branding a Paypage

We have designed our paypages to function as a checkout screen, these should look and feel just like a simple form. They are functional across many devices and as such the layout is fixed. Stylistic changes can be applied. Further details here:

https://asperato.github.io/docs/templates/#minor-stylistic-changes


4. Providing customer access to Paypages

A customer needs to receive the payment URL in order to complete it. There a many ways to distribute it; directly via a clickable link on an email, in a chat group, text or similar. Or as a clickable button as part of an digital document (Invoice or contract). Or as part of a more complex online journey where the Asperato ONE payment form is embedded in a containing web page of your own.


5. Paypage Launch Options

Choosing how you present our paypage to your customer depends on many factors, what works for your website may not work as well for you online invoices. We support the following:


Overlay: https://asperato.github.io/docs/templates/#using-the-template-as-an-overlay


as an iFrame:
https://asperato.github.io/docs/templates/#using-the-template-in-an-iframe


in a separate window or tab:
Note if used it will show the URL that starts: https://live.protectedpayments.net not your own web address.



Paypage Features and Benefits

Multi Payment Route

Our paypages allow you to collect Card payments, Direct Debit payments, ACH payments and Paypal all through the same form.


3D Secure
All pages support 3d Secure when required / desired.
Regularly tested
Optimized, tested, and always improving, we use Browserstack to ensure your customers transact successfully. https://www.browserstack.com/
Secure and PCI-DSS compliant
Protecting you and your customers.
Direct Debit Scheme rules compliant
We ensure scheme rules are followed so you don’t need to. https://www.bacs.co.uk/resources/pages/guideandrules.aspx
Dynamic and controlled by Salesforce
Salesforce content and processes drive our paypages, meaning you are always in control.
Salesforce Lightning and Communities ready
Made for Salesforce Lightning components and communities giving you hassle free and secure integrations.