Loopit Documentation
Changelog
  • Getting Started
    • What is Loopit?
    • Key Concepts
    • Setting up Loopit
      • Logging into Loopit
      • Multiple vs Single Workspaces
      • Configure Your Workspace
        • Workspace Details
    • Quick Start Guide
    • Welcome to Loopit 2.0
      • Understanding Loopit's Pricing Structure
  • Assets
    • Overview
    • Categories
      • Managing Categories and Subcategories in Loopit
      • Understanding Categories and Subcategories
      • Managing Pricing Overrides in Loopit
    • Adding Your Fleet
      • Uploading Photos
    • Tracking
      • Meter Readings
      • Tracking devices
    • Fleet Management
      • Issues
      • Service reminders
      • Inspections
    • Price Overrides
      • Customizing Charge Pricing Across Packages, Categories, and Fleet
      • Package-level Prices
      • Category-level Override
      • Asset-level Override
      • Asset-level Ultimate Override
  • Bookings
    • Overview
    • Lifecycle of a Booking
      • Creating a Booking
      • Confirming a Booking
      • Activating a Booking
        • Before Activation
      • Editing a booking
        • Adjust the price
        • Schedule Booking Changes
      • Pausing a Booking
      • Ending a booking
      • Cancel a booking
    • Deposits
      • Collecting deposits
      • Refunding/Claiming deposits
    • Referral source tracking
    • Tracking booking owner/manager
    • Contracts
      • How to Append Terms & Conditions (T&Cs)
      • How to send signed copy of contract/agreement to customer?
      • Inserting Dynamic Variables in Contract Templates
  • Billing
    • Invoices
      • Overview
      • One-Time Charges & Invoicing
      • Tax Types & Rules
      • Downloading Invoices
      • Overdue Invoices
      • Statement of account
      • Emailing invoices
      • Ad Hoc Billing & Invoices
    • Payments
      • Overview
      • Stripe integration
        • AU Becs Direct debit
      • Payment retry - Dunning
      • Auto pay
    • Credit Notes
      • Overview
      • Applying credit notes
      • Auto-apply credit notes
    • Setting up your packages
      • Program Types
      • Packages
        • What are packages?
        • Creating a package
        • Charge types and models
        • Configuring delivery on packages
        • Charges per location
    • Add Ons
      • Mileage Billing
      • Claim Excess & Excess Reduction
    • Billing Items
  • Settings
    • Users
      • Roles & Permissions
      • Inviting & Assigning Users
      • Enabling & Disabling Users
    • Locations
      • Managing Locations
      • Invoice Customisation
      • Assigning Fleet Locations
      • Booking pickup date rules
    • Workflows
      • Overdue Invoice Reminder
    • Email templates
      • Merge Tags
      • Entity Types
      • Creating a Template
    • Contract templates
      • Creating a template
      • Assigning a Contract Template
    • Integrations
      • Xero
      • FrankieOne
      • Geotab
      • Telemax
      • Rentalmatics
      • Sumsub
      • Tessera MVR Search
      • Experian AU
      • Bonzah Insurance
    • Webhooks
    • Website
      • Facebook Meta Pixel
    • Booking Rules
  • Security
    • Security information
  • People/Companies
    • Creating a Person or Company
      • Creating a person
      • Creating a company
    • Emergency contacts and references
    • Document expiry notifications
Powered by GitBook
On this page
  • Payment status
  • Invoice payment status
  • Overdue balances
  1. Billing
  2. Payments
  3. Stripe integration

AU Becs Direct debit

Last updated 21 days ago

Loopit supports AU BECs direct debit via Stripe. AU BECs is a delayed notificaiton (asynchronous) form of payment, this means that it can take up to four business days to receive notification on the success or failure of a payment after you initiate a debit from the customer’s account.

For new customers, Australia BECS Direct Debit transactions have a default limit of 1,500 AUD per transaction and 4,500 AUD per week. If you need higher limits, contact Stripe directly.

Payment status

When a direct debit is initiated the payment status will be "Processing" until it either changes to "Success" or "Failed". To see why a direct debit failed you can navigate to the payments list and hover over the "Failed" Status.

Invoice payment status

When the first attempt for a direct debit is initiated the invoice remains as "Unpaid". On the invoices list it will have a label "Payment processing", this means the direct debit is in progress and has not yet been successful or failed.

If the payment fails the invoice status will changed to "Failed" or "Paid" in the case of a success. Further attempts will not change the invoice payment status until it has a successful payment.

Overdue balances

An invoice is considered overdue even if the payment has been initiated and is in progress. We will remove an overdue flag once the payment has successfully completed.

Differences for Loopit 2.0: Your total overdue balance may appear higher as direct debit payments are processing. We do not treat processing payments as successful whilst they are processing.

support