How to Determine When to Schedule the Payment Processor

How to Determine When to Schedule the Payment Processor

Module: Payment Processing
Processing > Payment Processing > Create Payment Batches
Topic: When to Schedule Payment Batches
Version(s):  All
Editions: All     

When you have multiple payment processors it can seem confusing determining how to setup a schedule to create the payment batches.
The following will help guide you through the schedule creation.

Scheduling

See Batch Creation for Credit Cards for specific instructions on how to create a batch in order to schedule it
  1. Determine which payment processor is the default payment processor for the campaign.
  2. When scheduling additional payment processors you will want to make sure to check the radio to override constraints. 
  3. Determine which payment processors use tokenization.
    1. You will want all of your non token processors to run first. 
    2. The order of criteria (splitting them into separate batches or running all together) will not cause errors so long as non token processors are run first.
  4. Use link jobs, as well as the offset times, to run the batches at different times.
  5. Once you have your non token processors scheduled you can repeat the process with your token processors. 
    1. Pick up where you left off with the time and link it to the last job created.
Schedule different times for each job in order to:
  1. not pull orders into the wrong payment batch
  2. allow the server to work more efficiently 

Questions to Consider

Why does tokenization matter?

Payment profiles created with tokenization can only be processed with the account the token was created in. Unlike a credit card, you cannot use a token on multiple payment processors.

This is why non token processors need to run first in order to not pull token orders into the same batch.

What does the Override Constraint do again?

The override constraint allows a campaign to use multiple payment processors. For the client you will always run batches for the default payment processor first (without the Override Constraint checked) then run batches for the other payment processor(s) with the Override Constraint checked.

What about volume caps on payment processor?

Review Payment Processing Account Volume Caps for more information regarding how to setup volume caps.

Set the batch schedules as instructed above. Once a volume cap is reached  "any remaining transactions within the batch will be removed and set back to Pay Ready status. Once this occurs, "Auth and Settle" transactions will be immediately eligible for processing within a batch associated to a different Processing account, whereas "Settle Only" transactions will have their associated Pre-auth set back to “Available” so that it can be settled again at a future date when the limits are no longer exceed for the account that the pre-auth occurred through."