Credit Cards

For both Importing of Credit Cards or Tokens, the following apply:

• If the frequency is blank or One-off, then the card will always be attempted to be charged, regardless of the start date.
• For non One-off frequency, ie. Recurring,  where the Start Date is on or before todays day, OR the Payment Form, field "Enable Recurring" is  NOT "Yes - Tokenise on Signup, Charge on Selected Date", then the card will always be attempted to be charged.
• For non One-off frequency, ie. Recurring,  where the (Start Date is after todays date, or the Regular Payment Day is specified and does not equal todays date) AND,  the Payment Form, field "Enable Recurring" IS "Yes - Tokenise on Signup, Charge on Selected Date", then the card will be tokenised and the Recurring Payment will have the Next Payment Date set to the start date.
• For non One-off frequency, ie. Recurring,  a Recurring Payment Record is always created and the Payment Txn will be set to Matching Complete.  This means both successfully charged cards and failed cards during imports will always have a Recurring Payment Record create. This is so the standard Payments2Us retry logic will work, plus the processes for managing failed recurring payments would also apply.

Direct Debits

• One-off frequency is not supported.
• There will be no attempt to charged the Direct Debit during import.  This also applies for payment gateways that support automated direct debits such as EziDebit.
  The Recurring Payment will have the Next Payment Date set to today or the Start Date (if field is specified in the import
• For Payment Gateways that support Automated Direct Debit processing, such as EziDebit, if the Account and BSB are specified, then they will be tokenised.