We are changing the name of SL QuickPay to SL QuickCollect to avoid confusion with other systems out there. Plus, we think that since we are focused on the collection side of things of AR. Because of this QuickCollect has much more meaning.
SL QuickCollect is a Catalina Technology solution that allows you to email or SMS message out a simple link to your customer as a request for payment. The customer can then click on the link and are sent to a payment page without any portal login required. This lowers the barrier of entry for you to collect from your customers and get paid faster.
SLQuickCollect is Catalina’s solution that allows you to email or SMS message out a simple link to your customer as a request for payment.
Custom properties are a way to personalize the emails that go out to the customer. As well as the payment page and receipts they see. You can have an unlimited number of parameters with whatever text you want to send to the customer. And you can place it anywhere you want on the email and page templates.
Here is a quick demo on how you can do this via a RESTful API. And how to modify the templates to display the parameters.
Below is an example of a payload that you would send to the SLQuickCollect API.
CustID: The Customer ID of the customer you are sending the payment request to.
Amount: The amount you want to collect
PaymentEmailList: A delimited list of emails that the request is going to go to.
Properties: This is a list of properties as Name/Value pairs. You can create as many of these properties as you want. And then you can display them in the email, payment page, receipt email, and receipt page templates any way you want.
When you want to display a custom property on a template page, you use this ASP.NET format:
So, if the property name is “COMMENTS”, you would use this:
We have been busy adding new features to SLQuickCollect. SLQuickCollect is Catalina’s solution that allows you to email or SMS message out a simple link to your customer as a request for payment. The customer can then click on the link and are sent to a payment page without any portal login required. This lowers the barrier of entry for you to collect from your customers and get paid faster.
Below are a few of the new features we have added to SLQuickCollect over the last month.
Ability to create payment requests via web page: This is a way to quickly send out SLQuickCollect links from a simple to use web page.
Send attachments: You can send any type of attachment with the quick link email. This could include the invoice PDF, a work order document, pictures, or any other type of document you would want to send to the customer as information about the payment request.
Add custom properties to the requests: Custom properties are a way for you to send custom information to the SLQuickCollect link so that the customer knows what they are paying for. These custom properties are unlimited and can be whatever you want. They could include: notes, order number, work order number, or anything you can think of. These properties can then be displayed to the customer on the SLQuickCollect link email, payment page, receipt page, and receipt email templates.
More multi-site/config options: This allows you to create different email templates, config options, payment methods, branding, etc. By doing this, you can have a completely different setup for different companies, marketing campaigns, storefronts, and more.
L2/L3 fields: SLQuickCollect (and Account Central) can capture level 2 and level 3 fields such as PO Number, extended address information, line item information, etc. This allows for savings on credit card transaction fees.
Payment entry requests: Not only can you create payment requests that would apply against invoices (payment applications), but now you can create payment requests for “payment entries” in SL. These are payments that aren’t directly applied to an invoice. But just captured against the customer account.
This is a demo that shows you how to create a mobile app to interact with Dynamics SL to provide a “Contact Free” payment solution to help protect your employees and customers during COVID 19. The intended user of this example app would be a customer service rep, sales person, or field service rep who needs to collect payment from a customer (handy for collecting a deposit or down payment before delivery, installation, or service work to be done).
This demo uses Catalina’s API to search customers in SL and then lets the user to request a payment from a customer by generating a link and emailing it to the chosen customer. That customer then can click on the link and pay the amount which automatically creates a payment in SL’s AR.
Check out the video of the demo on our Youtube channel here:
Below is a screenshot of the Android app from the above demo. First you can search for a customer by a keyword. That search will then bring back a list of results. You can then click on the customer you want to request funds for. The app will automatically fill in the email address of the customer (from the Customer record in Dynamics SL). You can change the email address if you want. You then enter a requested payment amount and hit submit. Once you do this, Catalina’s SLQuickCollect will send off an email to the customer with a link which will then allow them to make a PCI compliant secure payment. Once authorization occurs, SLQuickCollect will then create a payment in Dynamics SL automatically.
As mentioned below, if you want to have starter code on creating an Android App (with Visual Studio and Xamarin), you can check out an example on our Github here (NOTE: I would only consider this a starter. This is in no means something finished but enough to get you started)
Getting paid by your customers can sometimes be difficult. Catalina’s payment portal allows users to login and manage their account and pay their invoices. But customers still need to login.
To reduce the barrier of entry for customers to pay, Catalina has come up with SLQuickCollect. SLQuickCollect allows you to send out a link via email or SMS which the customer clicks on. They are then sent to a payment page without any login required. They simply pay (Credit Card or ACH). Once that payment is authorized and captured, SLQuickCollect creates the payment in Dynamics SL.
The above shows how you can request for an amount not tied to any invoice. This is especially handy if you need to capture a deposit against a sales order, service call, etc. This payment would go into the SL “Payment Entry” screen.
The demo shows how you can request a payment from the sales order screen for a deposit amount. This would then send a link to the user via email. The user would click on the link and pay.
The request payment allows you to decide an amount to charge for a deposit for the order. It also has a handy percentage calculator to take out the guess work.
NOTE: SLQuickCollect also has the ability to send out a simple link to pay for an invoice and have that payment applied to one or more invoices through the “Payment Application Screen”
Catalina’s SLQuickCollect is a way to send a request for payment to your customer as an email with a link to click to pay. Your customer simply clicks on it and pays (no need for a portal login or anything). The payment works through a PCI compliant payment processor and is automatically integrated back into Dynamic SL’s AR.
There are many ways to create SLQuickCollect links. One of which is calling a stored procedure by passing a few parameters.
The stored procedure is called: xct_spSLPaddInvoicePaymentRequest
The parameters to this proc is:
@batNbr: The batch number of the invoice you want to send
@refNbr: The invoice number you want to send
@CustID: The customer who the link is going to be going to
@paymentEmailList: A delimited list of email addresses the link will be sent to
@siteID: (optional) For which configuration site to use (defaults to ‘SLPAY’)
@setupID: (optional) The PayFabric setupID you are to send. If not passed, the default will be used from SLQuickCollect’s configuration
@deviceID: (optional) The PayFabric deviceID you are to send. If not passed, the default will be used from SLQuickCollect’s configuration
You can call this stored procedure from most anything. You could call it from a trigger when an invoice is created. You can call it from a SL screen. Or even another application all together (like maybe excel that has a list of invoices to send)
Here is an example of how I added a button on the Invoice and Memo screen to send a SLQuickCollect link for a particular invoice.
Below, you can see where I created a button “Send SLQuickLink” that will take the current invoice on the screen and send a payment request link to the customer.
Below is the code behind the click event of the button. This will look at the current batNbr, refNbr (invoice number), custID, and get the email tied to the customer to send the link to that customer’s email.
Private Sub bPayLink_Click()
Dim SQLStr As String
Dim Csr_temp As Integer
Dim sCustID As String
Dim recfound As Integer
Dim maintflg As Integer
sCustID = GetObjectValue("ccustid")
SQLStr = "Customer_All " + SParm(sCustID)
serr = SqlFetch1(Csr_temp, SQLStr, bCustomer, LenB(bCustomer))
Dim lsSQL As String
Dim liCursor As Integer
lsSQL = "xct_spSLPaddInvoicePaymentRequest" & SParm(ThisScreen.cbatnbr.Text) & SParm(ThisScreen.crefnbr.Text) & SParm(ThisScreen.ccustid.Text) & SParm(bCustomer.EMailAddr) & SParm("SLPAY")
Call sql(liCursor, lsSQL)
MsgBox ("SLQuickLink Sent to CustID " + ThisScreen.ccustid.Text + " for invoice " + ThisScreen.crefnbr.Text)