What is buy now pay later (BNPL)?

Buy now pay later lets customers complete a purchase and pay in instalments — typically four fortnightly payments — rather than upfront. Your business receives the full payment immediately; the BNPL provider takes on the credit risk and collects from the customer.

Afterpay is the dominant provider in Australia for consumer retail. Zip (formerly ZipPay / ZipMoney) covers higher-value purchases with longer repayment terms. Humm (formerly Certegy) and Latitude Pay are also used in specific sectors.

For Australian retail, healthcare, and service businesses, BNPL has become a standard checkout expectation — particularly for purchases in the $50–$2,000 range.

When does your app need it?

• Your average transaction value is in a range where BNPL meaningfully reduces purchase hesitation ($50–$2,000)
• Your customers are predominantly Australian consumers aged 18–45 (the core BNPL demographic)
• Competitors in your space already offer BNPL and you're losing sales because you don't
• You're in retail, beauty, wellness, healthcare, fitness, or home services
• You want to increase average order value — customers often spend more when they can split payments
• You're building for mobile commerce or a consumer-facing booking/payment flow

How much does it cost?

Adding BNPL integration typically adds 4–8 hours of development — roughly $1,000–$2,000 AUD.

This is one of the lighter integrations — the BNPL provider handles all the credit checking, risk, and payment collection. Your app just needs to present the option at checkout, call the provider's API to initiate the arrangement, and handle the confirmation.

Cost increases slightly if:

• You need to support multiple providers (Afterpay + Zip)
• Your checkout has complex order structures (multiple items, partial refunds)
• Your platform is a marketplace where the BNPL flow needs to work across multiple sellers

Note: BNPL providers charge merchants a fee per transaction — typically 4–6% for Afterpay, 2–6% for Zip depending on the product. This is an ongoing operational cost, not a build cost, but it's significant.

How it's typically built

Each BNPL provider has an API (and in most cases, an SDK or hosted checkout component). Your app passes the order details — items, amounts, customer details — to the provider, which generates a redirect to their own checkout UI where the customer agrees to the terms. On completion, the provider sends a confirmation to your app and releases the full payment amount to your account (minus their fee).

Afterpay is the most straightforward to integrate for standard retail use cases. Zip has more flexibility for higher-value or service-based transactions.

For React Native or web apps, most BNPL providers offer drop-in JavaScript or native SDK components that handle the UI flow.

Questions to ask your developer

• Which providers are you integrating? Afterpay and Zip have different customer bases and transaction limits — you may want both.
• How are refunds handled? Partial and full refunds via BNPL need to be processed through the provider's API, not your regular payment flow.
• Is the BNPL option shown clearly with instalment breakdown? Australian regulations require the instalment amounts to be clearly communicated at point of sale.
• What happens if the BNPL approval is declined? Your checkout should fall back gracefully to standard payment options.
• Are there product eligibility restrictions? Some BNPL providers restrict certain product categories (alcohol, gambling, etc.).

---

See also: One-off payments · Subscription billing · App cost calculator