Paypages

paypages provide a secure and stylish interface to capture all the sensitive data required to collect money from your customers key features security & compliance secure and pci dss compliant protecting you and your customers 3d secure all pages support 3d secure when required/desired direct debit scheme rules compliant we ensure scheme rules are followed so you don't need to (reference https //www bacs co uk/resources/pages/guideandrules aspx ) address validation card bin checking card expiry date validation card identification payment methods multi payment route our paypages allow you to collect card payments, direct debit payments, ach payments, and paypal all through the same form customization & control customizable flow control success and failure page redirection is configurable, allowing for tailored user experience management dynamic and controlled by salesforce salesforce content and processes drive our paypages, meaning you are always in control object specific variations paypage behaviour varies depending on whether it's associated with the authorisation or payment object this allows for object specific data capture and processing localization the interface supports multi currency and multi language technical features & integrations salesforce lightning and communities ready made for salesforce lightning components and communities, giving you hassle free and secure integrations regularly tested optimized, tested, and always improving we use browserstack to ensure your customers transact successfully (reference https //www browserstack com/ ) how it works generating a paypage paypages are only available once an unaric payments 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 controlling paypage content when you create the unaric payments record, the data you populate and choices you make will affect how the paypage url performs and what data it presents to your customer 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 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 unaric payments payment form is embedded in a containing web page of your own 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 paypage template the paypage template is highly dynamic and responds to the following parameters within salesforce amount frequency (including one off payments) payment types (including combinations of payment types, such as card & direct debit, paypal & direct debit, card, paypal & echeck, etc ) address data (can be pre populated) url to navigate to on completion of the payment (including cancel, fail, & success endpoint fields) the template also has the following dynamic elements built in notification if the salesforce web service cannot be contacted uk postcode checker & lookup display of card type based on card number validation of card number using the luhn algorithm display of issue number & start date fields only if the card requires it validation of security code as 3 or 4 digits depending on the card type ability to switch between card, direct debit, echeck, or paypal on the fly ability to enter iban or distinct local bank details for all bacs/sepa european direct debit countries automatic hiding/showing and labeling of local bank detail fields based on selected country compliance with bacs and sepa scheme rules; correct compliance labeling is determined by scheme rules in the selected country choice of payment type to show by default paypage template styling the paypage can have some stylistic changes applied in order for it to fit within your customer journey, this includes changing page font changing button colours (text and background in both normal and hover mode, and border) changing link colour changing the logo (ideal size is 400px wide and 80px high, though the height is the key factor any bigger and you risk truncation) we can also remove the logo completely if required changing the page title hide / show "pay as company" link hide / show postcode lookup hide / show billing address switching between iban and local details for direct debits changing the 'processing' gif from the default gears changing the favicon (the icon that appears in the browser's tab for the website ) if you require any customised changes, contact mailto\ support\@asperato com as we will have to apply these customisations for you