PayTo

Take real-time bank payments from customers in Australia. Your customer authorises a payment agreement with their bank once, and from then on PayTo works the way any saved payment method does in Pepper. You enable it per customer in PMC, set a fee for it the same way you set a card fee, and filter payment history by it.

For distributor admins. You get a bank payment method for Australian customers with a per-customer toggle, its own configurable fee, and its own filter in payment history. Nothing about how you configure fees changes.

For your customers. They authorise one agreement with their bank and then pay from the bank account rather than a card, which avoids card processing fees on every order.

PayTo is enabled per customer relationship, not per distributor. Turning it on for one customer does not affect any other customer on your account.

When it is off, the customer's Customer Preferences panel in PMC shows the default payment method toggles with no Enable PayTo payments among them, and the customer sees no PayTo option at checkout.

The PayTo agreement. Your customer's standing authorisation with their bank to let you take payments. It is created once and then lives in one of three states: pending, active, or inactive. Payments only go through against an active agreement.

Agreement states. An agreement is pending after it is created and before the customer authorises it with their bank. It becomes active when the bank confirms the authorisation. It becomes inactive if the customer or their bank closes or cancels it. An agreement that goes inactive also removes the saved PayTo payment method from the customer's account.

Three behaviours shape how you plan this.

The ACH toggle is not shown for this customer once PayTo is on.

PayTo fees work the way every other payment method fee works. Fees are configured per customer and per payment method in PMC, so you can pass a PayTo fee through, absorb it, or set it differently from what that customer pays on cards.

Your customer sees the fee at checkout, shown as [amount] PayTo fee, or no PayTo fee when none applies.

Payment history in PMC has a PayTo filter option alongside the existing method filters, so you can pull PayTo payments on their own.

At checkout, a customer with an active PayTo agreement sees PayTo as a payment method, with its own icon, and the fee line described above.

A customer who has not saved a payment method yet is prompted to add one before they can submit.

Two messages are specific to PayTo:

A customer gets one bank payment method. PayTo is it, for customers you enable it on.

Activating an agreement changes the customer's default payment method. It becomes PayTo.

An inactive agreement removes the saved method. The customer will not see a stale PayTo option, and will need a new agreement to use PayTo again.

Fees are unchanged in model. Per customer, per payment method, configured in PMC.

Can a customer use PayTo and another bank payment method at the same time? No. A customer gets one bank payment method.

My customer's PayTo option disappeared. Their agreement went inactive, usually because it was closed or cancelled at their bank. Pepper removes the saved method when that happens. They will need to authorise a new agreement.

My customer says PayTo is not authorised yet. The agreement was created but their bank has not confirmed it. They need to finish authorising it in their banking app. Until then, payments against it are blocked.

I turned on PayTo but the customer still does not see it. Check that their agreement is active. A pending agreement is one the bank has not confirmed yet, and payments against it are blocked until the customer completes authorisation.

Can I turn PayTo on for a customer outside Australia?