💡 ClickFix | Partial Payments

LOGIN

Case Study : INVOICING & E-COMMERCE

Part 4 : Partial Payments

Summary : Building upon Part 1 : Pay What You Want and Part 2 : Generating payable invoices of our Case Study, in this part we are going to give your clients the ability to do partial payments, on their own terms, similar to Xero and other invoicing softwares.

Why Use This : This part of our case study series highlights the unique ability for customers to choose how much they pay and when, offering unprecedented flexibility in managing their finances. By allowing multiple payment methods and enabling customers to make payments on their terms, this is a significant leap beyond standard installment plans.

Use Cases for Partial Payments:

Custom Payment Contributions: Empower customers to contribute any amount towards their invoices, providing flexibility for large or unexpected expenses.
Flexible Funding for Projects: Allow backers to support projects with varying contributions, perfect for crowdfunding initiatives or charitable donations.
Split Payments Among Multiple Parties: Facilitate group purchases or shared services by allowing each participant to pay a portion of the total cost.
Adaptable Payment Schedules: Enable customers facing temporary financial constraints to continue making payments at a pace that suits their current situation.
Emergency Services or Repairs: Offer peace of mind by allowing partial payments for urgent services, ensuring customers can access necessary services without financial burden.
Mixed Payment Methods: Accommodate customers wishing to use different payment methods for a single transaction, enhancing convenience and customer satisfaction.
Dynamic Donation Amounts: Support charitable efforts by allowing donors to choose their donation amount, encouraging more participation and support.

ClickFix's Partial Payments revolutionize the way businesses and customers interact financially, breaking away from rigid payment structures to embrace a more inclusive and adaptable approach. This feature not only enhances customer satisfaction but also opens up new avenues for managing finances, both for businesses and their clients.

New Object “Payments”
1. Fields
  1. Amount : price
  2. Status : Dropdown
    1. Awaiting Payment
    2. Charge Transaction
    3. Paid
2. Relationships
  1. 1 Invoice Many Payments
  2. 1 Contact 1 Payment (name relationship “Payment Invoice”)
New Invoice Field
1. “Amount Paid” Rollout field, to get the Total paid from all Payments
Clone page #Invoicing #Payment #ThankYou to make #Invoicing #Payment #ThankYouPart4
1. This time, we will charge a card against a Payment object via the 1-1 relationship
2. The only difference is we check the Payments Status on this page, which could be
  1. Charge Invoice = Processing Payment Block
  2. Paid = Success Block
  3. Awaiting Payment = Failure Block
    1. But in this last block, we need to add the 1-1 Relationship with the Payment, and move the invoice back to Charge Invoice
Clone Dynamic Page “Invoice” and name it “Invoice Partial Payments”
1. New template/url
2. Design wise for the invoice itself everything stays the same except for
  1. the total being pulled from Amount Total field
  2. Two new lines above the total for Amount Paid & Amount Remaining
  3. Edit the pay now block to add
    1. Payment object field : Payment Invoice//Amount
      1. Prefilled with full remaining amount for the invoice, which is Total - Amount Paid
    2. Payment object field : Payment Invoice//Status dropdown
      1. Hidden, preselected to “Charge Transaction”
    3. Invoice Relationship Paying Invoice//Unique ID Prefilled
  4. Redirects to #Invoicing #Payment #ThankYouPart4
We can use our Dynamic Page “Invoice PDF” again here
New Contact Automation #ComplexInvoiceManagement
1. Clone #InvoiceManagement
2. Trigger “Payment Invoice” relationship is updated and Payment Invoice//Status is Charge Transaction
3. Charge the transaction using a simple “partial payment” product (the actual invoice for the clients we will generate ourselves as a pdf)
4. Also, after payment hook, send a hook that will connect the generated payment object to the relevant invoice
5. Our usual goals on Last Transaction Status
6. Last step after check if the Invoice is fully paid. If so, move it to Paid and generate the PDF invoice.

Download Assets

Note that you must be logged into the Ontraport account to import this

Divider Text

What's Inside

One Automation
1. #ComplexInvoiceManagement
Two Pages
1. #PayWhatYouWant #ThankYou (to be edited to target your Payment custom object)
2. Template Invoice Partial Payments (import the block into an Invoice Dynamic Template)
3. Template Invoice PDF (import the block into an Invoice Dynamic Template)
One Dropdown Field "Pay What You Want Status" (which you can remove once you are using the Invoice Object Fields

ClickFix Features

Conditional Display Overview (🆓 Free Plan)
Calc Shortcode Overview (🆓 Free Plan)
Log Transaction Overview Documentation (➰Essential Plan)
1. Alternative : Ontraport API
Page to PDF Overview Documentation (➰Essential Plan)
1. Alternative : Zapier + DocRaptor
URL Shortener Overview Documentation (➰Essential Plan)
1. Alternative : Zapier

What You Must Do

Since we cannot share Custom Object Automations with you, you'll have to follow the steps above to recreate this system, including
1. Create #Invoicing #Payment #ThankYouPart4, which you can clone/edit from imported page "#PayWhatYouWant #ThankYou"
2. Import blocks from Template Invoice Partial Payments into Dynamic Templates and Edit the Pay now block to add the Payment field amount and status
3. Import blocks from Template Invoice PDF into Dynamic Templates
In the imported contact automation, edit all triggers and updates to the Payment//Status to match your fields, and the webhook within the automation to enter YOUR ClickFix Token (or use Ontraport API)
(Note that post data is corrupted by Ontraport during import, see note within the automation)
Add products to the different payment forms

CLICKFIX

PRODUCT

Template Library

Shortcodes

DISCOVER

Case Studies

Live Documentation

Support

Change Log