Payment Processing Accounts are accounts with unique credentials setup with your chosen Payment Gateway. This is where you will process transactions between you and your customers.
To add the new accounts, please navigate to Company Data -> Payment Data -> Payment Processing Accounts. Once there click the green plus sign icon in the upper right corner of the screen to launch a new Payment Processing Accounts window. Within that window enter an Account Name that makes sense to you (I like to use the same naming convention as previous accounts).
Environment ID of Production
Account Type of Credit Card
- Check the credit cards that will be processed through this account.
- Chose the Payment Processor to associate this account to
- Skip all the way down to Login Username and Login Password and populated them accordingly.
- Assign the Campaigns and Product Groups that will use this as their default credit card payment processing account, and any Rules based on response text from the gateway and Save your changes.
- Repeat the above steps for any additional accounts being added.
To modify the default payment processing account on imports, navigate to Processing -> Import / Export -> Imports and click the Show Schedules button. Click the arrow to the left of the schedule name to expand the selections for the first applicable import schedule. You will notice that the default payment processing accounts are grayed out and appear unable to be edited. That is not so. Just click the Use Default Payment Accounts box, wait for the page to refresh, click the Use Default Payment Accounts box again, and select the new accounts that you want to use from the drop down menu. Click Save in the Edit Schedules box to save your changes. Repeat these steps for each import that will require the update.
If you are changing the account used for preauths within your system (from the order entry screen) there is one final step in the setup switchover process. Please navigate to navigate to Company Data -> Advertising -> Maintain Scripts and click the green edit pencil to the left of the first applicable script name to launch the Script Properties window. Click on the Pay/Shipping tab and chose the correct Payment Processing Account from the drop down menu and Save your changes. Repeat this for each script that will require an update.
Once you complete the steps above you are all set. There is a setting in the system where items will only get into Settle Only batches for the accounts with which they were preauthed. So if you plan to stop using the accounts already setup in your system you will want to continue to create Settle Only batches on these accounts for a while. When processing Settle Only batches, please ensure that the box next to Override Constraints is checked.
ensure that everything is making it into a batch and nothing is missed, we
recommend running an Item Status Report under Reports -> Customer Service
Reports every day after processing is complete.
Answer – OLX can have a programmer set the bit on the back end to have credits process only through the account that was used when the payment was captured.
OLX set the bit on the back end to have credits process only through the account that was used when the payment was captured.
Answer - To issue credits through the original account, you will want to run an auth and settle batch for credits as well. When processing your Auth&Settle batches, you want to follow your default payment processing account association, so you will want to ensure that Override Constraints is unchecked for those.
Answer – If you set a default payment processing account for CS, that may be used for entering any new orders using the DNIS you have setup for CS. That does not relate to refunds, though. If a CSR issues an RMA, the credit item will be created in Item Pending or Item Pay Ready status once the RMA is closed. When a CSR issues an instant credit, the credit item will be immediately created. If the CSR attempts to process a refund through the Order Detail screen, then as long as they are not setup with the permission to 'override payment processing constraints', the only account that will be available in their drop down menu will be the account that is set as the default credit card payment processing account for the campaign or product groups associated with the items on the order.
- OLX can have a programmer set the bit on the back end to have credits process
only through the account that was used when the payment was captured.
Answer – The creation of a payment batch is determined by Status, Processing Type, Date, and Product Group. The creation of autoship orders is Client, Date, and Campaign driven. That said, the only way to handle what you are describing is by creating a separate Product Group for the offers to be processed through a different payment processing account.
For now, there are a couple of options for avoiding having to create new product groups for each Payment Processing Account.
1) You can filter by campaign(s) when creating autoship orders under Processing -> Autoship Processing, run PrePayment Processing, then manually create your payment batch, go back to Processing -> Autoship Processing and repeat the previous steps until each autoship batch is processed through their own accounts.
2) You can create autoship orders under Processing -> Autoship Processing, then filter by Campaign on the PrePayment Processing page (using the Advanced Filtering option), then create the payment batch, then return to PrePayment Processing filtered by campaign, create payment batch and so on.
Both will add to your total processing time. But both are also able to be scheduled. Personally, I would go with option 2 as it cuts out one step. Either way, I would suggest that your regular/initial orders be processed separately *after* you finish with autoship orders (because by then you can run PrePayment Processing on all items without having to worry about the status of those items).