B1 iPayment Server Component - Overview

The iPayment Server Component consists of a number of workers that run in sequence.
Each worker has a minimum wait time between runs and will run on the next sequence if this minimum wait time has been exceeded for that specific worker.

Here is an overview of workers in the sequence they're processed and their minimum wait times:
The titles link to a more technical article about each worker's flow.

Note:  Since the workers run in sequence, even though the minimum wait times have been exceeded, it is possible that one worker will be waiting for another worker to finish working.
This can in some cases mean that workers run less often, if you experience this being a problem you should try to identify the source of the hangup.

Example: The minimum wait time of 5 minutes for the Add Credit Card worker has been exceeded, but because the Authorization Expired worker is processing a large batch of 10000 authorizations, it ends up having to wait until the Authorization Expired worker has finished all 10000 requests.
The processing time for the workers will vary depending on their load at the time, so in larger databases with a lot of transactions, some of them may end up running for extended periods.

Extended Logging:
If you wish to figure out what is going on more specifically if it is from iPayment 2020.06 and higher possible to enable extended Debug Logging for the server component. Here is how you activate it:

• On your desktop create a new txt-file called "FeatureFlags.txt"
• 
• Open the file and write the word IPAY_DEBUGMODE
• 
• Save the file and copy it to the iPayment Server Component install folder (Normally 'C:\Program Files (x86)\Boyum IT\iPayment Server component')
• Restart the iPayment Server Component Service