Create many scheduled payments from a CSV file

To schedule many customers at once, open Import from CSV and choose the Scheduled payments tab. You need access to both account settings and scheduled payments. Each row is one schedule with one item, for a customer and a saved payment method you already have, so load your customers and products first. The import charges nobody: an active schedule takes its first payment on its start date.

1. Download the template. Only customer, frequency and start_date are required, plus a product or a description with a unit_price. A customer or product that does not exist, is switched off, or fits more than one record makes that row not imported, with the reason beside it.
2. Choose frequencies. Use once, daily, weekly, monthly or yearly, and the optional every column for every 2 weeks, every 3 months and so on (1 to 99). Quarterly, semiannual, biweekly and fortnightly are understood as well. Bimonthly and twice a month are refused, because they mean different things to different people. For a monthly or yearly row, the optional day_of_month column takes 1 to 31 or last; left blank, the schedule keeps the day it starts on. The start date cannot be in the past. An end date or a number of payments only applies to a repeating schedule.
3. Name the saved method. The payment_method column picks one, such as visa 4242; blank uses the customer's default. A customer with no usable saved method makes the row not imported. Use only the last four digits: a file with a whole card or account number is refused.
4. Active or paused. Schedules are active unless you tick Create the schedules paused; a status column overrides that for a row. Paused schedules never run until someone resumes them.
5. Check, then confirm. The preview lists every row with its first payment date and amount. When it would set up active schedules, you see how many and how much they take each time they all run, and must tick the box that the customers have agreed to be charged. Nothing is created until you do.

A row that matches a schedule the customer already has (same method, amount, frequency and first payment date) is skipped, so the same file is safe to upload twice. A monthly schedule that starts on the 29th to the 31st returns to that day after a short month and runs on the last day of the month when there is no such day.