Ezidebit Cloud Payment Implementations CRM Applications / Account Receivable Industry Australian Insights API Download, and Resource Centre: http://developers.ezidebit.com.au/ For account receivable (AR) payment management, best practice implementations usually involve a web site, customer relationship management system (CRM), Ezidebit cloud payments, and a financial accounting system. All four play an important part in shaping your business process and customers payment experience. The Ezidebit Cloud Payments API includes a comprehensive suite of widgets, client side methods, and SOAP web service to address all your AR business use cases. In Australia, our data demonstrates that AR payments significantly are split between once off invoice payments and recurring payments from either bank account or credit card. The aim to lead your customers to a fully electronic and recurring payment cycle drives up your business revenue, but significantly drives down administration costs. A basic implementation may include 4 use cases: 1. Once off Payments (invoice Payments) 2. Sign-up for recurring payments 3. Recurring Billing ( e.g. fortnightly) 4. Reconciliation This brief covers each use case in turn. Note: Other edge use cases should be considered, such as edit customer details, and cancel account.
Once Off Payments Once off payments, via a credit card can be accepted either directly from the customer via your website or through a call center. From within the Ezidebit Cloud Payments API developers can use either: Option 1 - Instant Payment Widget This hosted page can be configured as an integrated page or a standalone. Click on the examples below. Stand-Alone https://webpay.demo.ezidebit.com.au/paymentsbillerconfirm.aspx?biller=11407 Integrated https://webpay.demo.ezidebit.com.au/payment.aspx?pt_digitalkey=5ff21795-9722-4f73- BE1C-0D96F34692C1&PT_PaymentReference=TRANSID- 000111&PT_CustomerName=Customer_Name&PT_PaymentAmount=100&PT_ReturnURL=http: //worldlearningcentre.com.au/ The page can be easily customized to your business branding, and there are many options that can be configured to customize the forms functionality. Option 2 - Client Side Methods. Using our ChargeCard() function from our Clientside Method library your developer can create a fully customized web page into your workflow that accept credit card details, whilst ensuring PCI compliance. Option 3 Process Realtime Token Payments If your customer has already registered for recurring payments (see next section). you can use the credit card stored for recurring payments to process a Instant Payment, that is, get the result immediately. See ProcessRealtimeTokenPayment() method.
Sign-up for Registered Customers and Recurring Payments Through offering a web signup process, your client organization can capture valuable customer details for an ongoing digital nurturing program and to initiate recurring payment. The signup process collects basic contact details, bank account or credit card details, and the customer authority for Ezidebit to debit from there account on behalf of the client organization. The signup process is typically initiated from the website. This step creates an Ezidebit customer account and securely stores the credit card or bank account details in the PCI vault. Once again Ezidebits, cloud payment API offers 2 ways to achieve this. Specifically this includes our Scheduled Payment Widget, and Client Side Methods. Option 1 - Scheduled Payment Widget There are two variant use cases for this widget. Option 1(a) direct debit authority only where the payer securely provides their bank details and agrees to debits from their account as your business require. Click the link below to see an example: https://demo.ezidebit.com.au/webddr/requestform.aspx?a=0x313634323343455354455354&debit s=4&nosms=1&ureflabel=invoice%20number&uref=345678&fname=a&lname=customer&email= a@eftel.net&mobile=0405135367&addr=1%20long%20rd&suburb=tambo&state=qld&pcode=408 0&dur=1&businessOrPerson=1&callback=http://www.ezidebit.com.au/ (if clicking on the link does work cut and past to browser) The page can be easily customized to your business branding, and there are many options that can be configured to customize the forms functionality. Option 1(b) direct debit authority and future payment schedule - where the customers securely provides their bank details and agrees to a schedule of recurring payments (with an optional once off payment). Click the link below to see an example: https://demo.ezidebit.com.au/webddr/requestform.aspx?a=0x313634323343455354455354&debit s=2&sms=1&ureflabel=invoice%20number&uref=345678&fname=a&lname=customer&email=a@ eftel.net&mobile=0405135367&addr=1%20long%20rd&suburb=tambo&state=qld&pcode=4080&f req=4&rdate=1&ramount=59.95&dur=1&businessorperson=1&callback=http://www.ezidebit.com. au/ (If clicking on the link does work cut and past to browser)
The Scheduled Payment Widget can either be pre-populated with customer details if they have been already collected by your site, or alternatively the customer can enter contact details directly into the form. The choice of which approach to use depends on your specific website design and how it interacts with your CRM software. Option 2 Client Side Methods Using our powerful SaveCustomer() and SaveCustomerAccount() functions from our Clientside Method library your developer can create your own fully customized web pages that accept credit card and bank details in a PCI complaint manner, and the customer authority for Ezidebit to debit their account as instructed. Recurring Billing The function of triggering payments from customer bank accounts or credit cards occurs in the CRM software. If the signup process requested a direct debit authority from the customer such that payments could be taken as required Option (a) the software would call the Ezidebit AddPayment() method instructing Ezidebit to take a payment against the bank account or credit card that has been stored securely against the customers Ezidebit account during the sign-up process. If the sign-up process used was Option (b) where a specific recurring ($) amount was presented, then Ezidebit will automatically process the payment each period without further instruction. For ad hoc purchases from a registered customer you can use the credit card stored for recurring payments to process an Instant Payment, that is, get the result immediately. See ProcessRealtimeTokenPayment() method. Reconciliation The function of updating the customers account with successful payments also occurs in the CRM software. Periodically the software will call the Ezidebit GetPayments() method which will return the status of all payments.
Client Side Method Payer Browser Website/Application Server CRM Software Ezidebit Cloud Payments Opens your website Request page List "membership options" Select membership type Display payer details form Provide user details Display details review page Confirm details are valid Submit registration & banking details + Agree to T&C SaveCustomer () Callback (BankRecieptID & Customer ref) Create Ezidebit Customer + Process a real-time transaction (optional) New member receipt New customer unique ID Create Customer Email notification