Skip to main content

We are noticing that IFS is trying to authorize credit card transactions for customer orders in our development environment around 1am everyday - even for past orders that have already been charged. We have disabled the credit card type to prevent the transactions from going into “authorized” status.


Does know how to stop IFS from scheduling these transactions for orders that have already been completed/paid for or why it keeps trying to authorize these orders?

 

Thanks for your help.

Hi, 

Sorry this took so long, I had to ask - via an email. 

There is a scheduled database task with name “Auto authorize customer orders with remaining authorized amount”. Ask them to delete or de-activate that.

You may also want to verify that the DEV environment is sending messages to the credit card processor sand box - not live.  If DEV was a copy of PROD, that set up should be changed - if it has not already. 

Best regards, 

Thomas

@Thomas Peterson Great, this worked. Thank you!

Hi, 

Sorry this took so long, I had to ask - via an email. 

There is a scheduled database task with name “Auto authorize customer orders with remaining authorized amount”. Ask them to delete or de-activate that.

You may also want to verify that the DEV environment is sending messages to the credit card processor sand box - not live.  If DEV was a copy of PROD, that set up should be changed - if it has not already. 

Best regards, 

Thomas

@Thomas Peterson For the most part this worked but I am getting one or two that are still getting authorized around 1am. Other than the CC Auto Authorize scheduled database task, is there any other tasks/background tasks that could trigger these one or two orders?

Would auto authorize running also allow for freight charges to get captured if using the freight interface?  Right now, when using the credit card interface with the freight interface does not allow for the additional freight charge to be captured because the credit card processing requires pre-authorization and this step is done at the release of the order.

@mpmhoco Thanks for the reply! This issue was resolved because we found that the credit card settings for our production environment copied over into one of our test environments, so we turned it off and we are no longer having this issue.

Terms & ConditionsCookie settings