Introduction

payments is a comprehensive payment solution salesforce application use payments to collect and send payments, safely save customers information, and automate your payment processes payments legacy name is asperato you may still encounter the term asperato in this documentation and within the salesforce interface, including object names (e g , asperato authorisation , asperato payment ), api names (e g , asp04 authorisation c , asp04 payment c ), and various actions why use payments? unify the payment related requirements of your company while integrating payments with your salesforce org and data support a wide range of currencies, payment methods—such as credit/debit cards, direct debit, ach/echeck, and paypal—and integrate multiple payment services providers, including stripe, worldpay, gocardless, braintree, and authorize net set live notifications and alerts that pinpoint payment failures promptly for a swift issue resolution access to and store extensive customer data, including payment history, while complying with industry standards for data handling, such as pci dss automate recurring payments and set up retry mechanisms for failed payments generate payment links and codes and embed pay pages in your site without writing code use cases offering a wide range of options for payments, payments can easily meet general and specific requirements and fit a variety of business models franchises franchises operating under a single salesforce org but requiring payments to be deposited into multiple bank accounts—each corresponding to different franchisees or legal entities—can setup distinct groups of psp connections payments can then be routed appropriately and deposited into the correct bank accounts subscription based services companies offering subscription services can utilize asperato to automate recurring billing by securely storing customer payment methods through authorizations, businesses can schedule automatic payments, reducing manual intervention and ensuring timely revenue collection real estate real estate companies can manage and automate various financial transactions, such as property sales, rent, deposits, and maintenance fees, directly within salesforce tenants can access self service portals to make payments using various methods, including bank transfers, credit/debit cards, and direct debits professional services and manufacturing businesses in these sectors often manage numerous client invoices asperato streamlines the payment process by integrating pay now buttons, links, or qr codes directly into invoices asperato also offers many options for refunding create refund records manually, through salesforce flows, or via batch classes, specifying details such as the associated payment, payment method, and refund amount payments architecture overview payments’s architecture is built around a modular data model that cleanly separates different aspects of the payment lifecycle at its core, four key objects form the backbone of the system objects authorisations docid\ f33l 1zecsfrnsvxhueo5 object name asperato authorisation api name asp04 authorisation c this object records the approval details for a payment before funds are captured, an authorisation is generated to confirm that payment methods are valid and that sufficient funds exist an authorisation record is linked to both one off and recurring transactions, serving as a reusable reference for subsequent payments payments docid\ nf5zal0y9xdg fyhctw8c object name asperato payment api name asp04 payment c the payment object represents the actual financial transaction it captures details such as the transaction amount, payment method, status, and related metadata every payment is typically associated with an authorisation that validates the transaction in addition, the payment object forms the basis for any follow on actions, such as refunds refunds docid\ lg6oxx86 ru4kvicq tq object name asperato refund api name asp04 refund c when a transaction needs to be reversed, the refund object is used it maintains all the details about the reversal process, including the refunded amount and the status of the refund operation refund records reference the original payment to ensure complete traceability and auditability payment schedules docid\ mr7d24nqdmzsfhovef2wd object name asperato payment schedule api name asp04 paymentschedule c the system is designed with clear relationships between these objects an authorisation record acts as the anchor it is referenced by both payment and schedule objects for one off transactions, the payment record is directly tied to its corresponding authorisation in recurring payment scenarios, the schedule object uses an existing authorisation to generate a series of payment records automatically if a refund becomes necessary, the refund object connects back to the original payment record, creating a full, auditable trail across the payment lifecycle objects flowchart graph td; asperato\["\<b>asperato\</b>\<br/>authorisations\<br/>payments"] < >|webhooks| aws\["\<b>aws\</b>\<br/>translation layer\<br/>webhook processing"]; paymentpage\["\<b>payment page\</b>\<br/>payment details\<br/>bank details (authorisation)"] > aws; aws < >|api| asperatosf\["\<b>asperato/sf\</b>"]; paymentpage < > asperatosf; subgraph asperatosf\["\<b>asperato/sf\</b>"] authorisations\["\<b>authorisations\</b>\<br/>customer bank details/tokens\<br/>mandate references\<br/>accounts/contacts"]; paymentschedule\["\<b>payment schedule\</b>\<br/>authorisation\<br/>amount\<br/>frequency"]; payments\["\<b>payments\</b>\<br/>accounts, contacts\<br/>payment outcome\<br/>authorisation"]; refund\["\<b>refund\</b>\<br/>payment\<br/>amount"]; end asperatosf > authorisations; asperatosf > paymentschedule; asperatosf > payments; asperatosf > refund; %% apply styling classdef startend fill #002d4c,stroke\ none,color #fff,font weight 400,font family\ helvetica,rx 5px,ry 5px; classdef process fill #42a4dd,stroke\ none,color #fff,font weight 400,font family\ helvetica,rx 5px,ry 5px; classdef decision fill #f4f7fa,stroke\ none,color #002d4c,font weight 400,font family\ helvetica,rx 5px,ry 5px; class asperato,aws,asperatosf startend; class paymentpage,payments process; class authorisations,paymentschedule,refund decision; unaric behind payments payments is part of unaric's suite of salesforce applications unaric applications comprehend the responsibilities of various business departments, offering solutions for revenue operations unaric equips you to optimize every step of your revenue journey, from prospecting tools like linkedin integration and data enrichment to asset and inventory tracking service operations enhance your customers' experiences with communication tools, telephony integrations, insightful analytics, and comprehensive cs support solutions system administration maintain and optimize your salesforce instance with unaric's administration tools and features unaric's team of business builders and entrepreneurs brings experience and expertise, helping businesses maximize their salesforce investment visit unaric website to know the rest of the suite and get in touch to have a conversation