Integration Configuration

once integrated with gocardless, it is possible to employ many of its features directly from asperato success+ gocardless success+ is used to recover failed payments automatically, using ai to identify the best time to retry failed payments how it works after a payment fails to be collected, asperato informs gocardless that the payment needs retrying asperato will then retry collecting as configured by the gocardless account graph td a\["payment created in asperato"] >b\["asperato informs gocardless about new payment"] b >c\["payment status submitted for collection"] c >d{payment collection successful?} d yes >e\["payment status collected from customer"] d no >f\["payment status retry in progress"] f >g\["payment resubmitted (gocardless settings)"] g >h{payment collection successful?} h yes >e h no >i{retry attempts exhausted?} i yes >j\["payment status failed"] i no >f classdef startend fill #002d4c,stroke\ none,color #fff,font weight 600,font family\ helvetica,rx 5px,ry 5px; classdef process fill #42a4dd,stroke\ none,color #fff,font weight 500,font family\ helvetica,rx 5px,ry 5px; classdef decision fill #f4f7fa,stroke\ none,color #002d4c,font weight 600,font family\ helvetica,rx 5px,ry 5px; class a,l startend; class b,d,e,f,g,i,k process; class c,h decision; the automatic retries are enabled at org level and then the setting filters down to individual payment records, enabling you to control which payments get retried if you have enabled success+ at gocardless and asperato, it is not recommended to take payment from an alternative route when the payment status is retry in progress fields & status metadata value field (payment object) retry attempt status (payment object) retry in progress how to enable you need to enable success+ separately for each currency from the gocardless dashboard contact gocardless support to get an understanding of the setup and testing of this feature to enable success+ in asperato, write to support\@asperato com mailto\ support\@asperato com we will confirm you once this setting is enabled exclude payments from retries after success+ is enabled for your organization, new payment records will have the success+enabled checkbox automatically set to true by default to exclude a specific payment record from the success+ retry process, simply edit the record and uncheck the success+enable checkbox add the following fields to the payment page layout to manage and monitor retries success+enabled ( asp04 success plus enabled c ) approx next retry date ( asp04 approx next retry date c ) the attempt retry field's value is determined by a custom setting and may differ from the success+enabled checkbox payments are only retried if both the success+enabled field and the attempt retry field are checked this allows for even finer grained control over which payments are retried view next retry date for gocardless success+ customers it is possible to see the date on which gocardless will re attempt to collect a payment to enable it, add next retry date on asperato payment page layout from the salesforce setup payment notifications suppression gocardless automatically sends you notifications for several events, including payment, mandate, and subscription creation you can deactivate payment notifications through asperato, which is helpful if you have your own notification system in place supressing these gocardless notifications will not affect the mandatory emails which are part of the bacs scheme rules (e g the emails sent following direct debit setup) notifications for mandate created and subscription created events will continue to be sent by gocardless even if you suppress payment notifications how it works the payment object in salesforce includes two fields related to notification suppression field name type purpose suppress notification by psp standard field controls notification behavior for individual payment records suppress psp notifications formula field displays the calculated suppression status based on relevant settings these fields are primarily for informational purposes and auditing the actual control of notification suppression is managed by protected customer settings and custom settings the suppress notification by psp field on a payment record is populated automatically depending on how the payment is processed scenario 1 scheduled batch processing via asperato payment schedule when payment records are created through the asperato payment schedule result the field is set to true if the custom settings for suppression (detailed in configuration steps 1 and 2) are enabled when the payment is created by the schedule scenario 2 manual processing from salesforce when you click the process payment using authorisation button from salesforce, and a pop up window with a checkbox for suppression appears result the field's value will match the selection you make in the suppression checkbox on the processing page scenario 3 custom processes (salesforce flows or apex code) when payment records are created using custom salesforce flows or apex code result the field defaults to false unless you explicitly set it to true in your custom flow logic or apex code configuration steps gocardless approval before suppressing payment notifications, you must obtain approval from gocardless to this end, contact gocardless support at help\@gocardless com mailto\ help\@gocardless com mention that you wish to handle “payment created” notification for all the schemes that you intend to use (eg , sepa, bacs, becs, pad, ach, etc ) note that to gocardless, you will have to individually mention the schemes for which you intend to handle the notifications asperato configuration contact asperato support at at support\@asperato com mailto\ support\@asperato com and ask them to set the protected customer setting bypass payment notifications by psp to true this setting requires subscriber level access to be modified we are required by gocardless to see evidence of your handling of notifications for this purpose, our customer success team would ask you to complete a self signed form and provide the confirmation email from gocardless once we have these two documents our team will enable this feature for your salesforce org salesforce settings in salesforce, go to setup > custom settings open asperato one settings click manage and edit set the suppress notification for payments custom setting to true click save to finish if you use custom salesforce flows or apex code to create payment records, you must ensure the suppress notification by psp field on each payment record is explicitly set to true if not set, it defaults to false in custom processes suppress payment notifications in records go to the authorisation tab and select the record against which to take payment click the process payment using authorisation button mark the suppress notification by psp checkbox click on process payment to finish go to the payments tab click the new button enter the required payment details in the payment reference information section, mark the suppress notification by psp checkbox after getting the necessary approvals, check the approvals section if the value of the custom setting field suppress notification for payments is set to true, then all the payments created by the payment schedule will have the value of suppress notifications by psp set as true troubleshooting if gocardless payment notifications are still being sent after you have configured suppression verify that you have received approval from gocardless for payment notification suppression confirm that both the protected customer setting bypass payment notifications by psp (configured via asperato support) and the custom setting suppress notification for payments (configured in salesforce) are set to true if you use custom processes (flows or apex) to create payments, ensure your custom code correctly sets the suppress notification by psp field to true on each payment record re enable gocardless payment notifications to resume receiving payment notifications from gocardless request asperato support ( support\@asperato com mailto\ support\@asperato com ) to set the protected customer setting bypass payment notifications by psp back to false set the custom setting suppress notification for payments in salesforce back to false passthrough parameters it is possible to send custom values with gocardless on the authorisation and payment records using passthrough parameters for more information, see gocardless at psp passthrough parameters docid\ kqqxsrwdqysbny0tya2ug development work is involved in implementing this feature we strongly suggest appointing a salesforce consultant to manage implementation gocardless faster ach it usually takes 4 5 working days to receive a direct debit ach payment in your bank account gocardless are accelerating this process by charging your customers on the same day that you create payments, and sending payouts ‘same day’, reducing processing time by 2 days chat to your gocardless customer success manager to have this feature enabled on your account they will advise you once this is done payment creation requirements the due date (in gocardless this is charge date ) must be the same date that the payment is submitted ( i e today) and must adhere to the following nacha conditions it must be a domestic payment (no international ones) equal to or less than $1m to make sure the intended faster ach payments are charged the same day, they must be submitted before the submission deadline of 11am est anything after that time will fall into standard ach processing times payment records reflect the payout reference number that is generated by gocardless when a payment has been completed suppress direct debit notifications sent by psp it is possible to request the suppression of direct debit notifications contact support at support\@asperato com to request this suppression if you would like to send your own direct debit messaging test direct debit when setting up a mandate or processing a direct debit payment, there are inherent delays in receiving confirmation the time required for mandate confirmation varies by region for instance, in the uk, it typically takes approximately three days for precise timing details specific to your region, consult your direct debit provider these processing delays can significantly impede testing workflows to facilitate efficient testing, gocardless provides scenario simulators given the nature of the asperato integration, we suggest using name triggered scenarios multi signature bank accounts for gocardless direct debits some bank accounts require two or more signatures to authorise a direct debit setup when using gocardless through asperato, a checkbox is provided for customers to indicate if their bank account has this requirement selecting this checkbox triggers the download of a direct debit mandate form, as these details cannot be collected directly through the api 1\ customer the customer downloads the mandate form by clicking the link on the payment page (as shown in the screenshot above) the customer can either use a pdf editor to fill in the form electronically or print the form and fill it in manually the completed form must be sent to the company requesting the authorisation (your company) 2\ create mandate log in to your gocardless dashboard and create a new mandate do not attempt to collect bank details through the standard gocardless flow this mandate will initially be incomplete pending receipt of the physical form email a copy of the completed pdf mandate form to help\@gocardless com gocardless requires this physical copy to complete the mandate setup 3\ email asperato email support\@asperato com with the following information the gocardless mandate id the salesforce record id (e g , the contact id or opportunity id) to which the mandate should be associated asperato will then import the data into salesforce so that the two systems align