We are trying to create automatic invoices for customers that are on a subscription service and automatically charge them. I know there are ways in Acumatica to create recurring invoices and release them on a schedule but is there a way to automatically authorize and capture customer credit cards against those invoices in Acumatica?
Page 1 / 1
Make sure the Default Payment Method for the customer you want to process is the CC which needs to be Captured.
Invoices being created should have that payment method and they will show up on Generate Payments (ScreenId=AR511000) and Banking Module which is a process screen and you can schedule to process and payment being created for those Invoices.
Once the Payment created from that screen, this payment would be available on Capture Payments (ScreenId=AR511500) which lists all payments created against invoices with CC as Payment Method. This screen also can be automated using automation schedule.
This way you can generate Payment and Capture payment for your invoices automatically.
Hi
Make sure the Default Payment Method for the customer you want to process is the CC which needs to be Captured.
Invoices being created should have that payment method and they will show up on Generate Payments (ScreenId=AR511000) and Banking Module which is a process screen and you can schedule to process and payment being created for those Invoices.
Once the Payment created from that screen, this payment would be available on Capture Payments (ScreenId=AR511500) which lists all payments created against invoices with CC as Payment Method. This screen also can be automated using automation schedule.
This way you can generate Payment and Capture payment for your invoices automatically.
I know this is old, but have a question about this in 2024R1 with Acumatica Payments enabled (using the Fortis gateway).
I have set up automation schedules to Generate Payments and Capture Payments to run periodically, working great.
However, just had a situation where a customer with our credit card payment method set as their default, but not their specific saved card saved being the default (i.e., just the system payment method was default but the saved card was NOT set as the default) had a charge attempted for a payment.
A sales order shipment was processed and the automation initiated a charge for the payment, even though the sales order had no card assigned to it. The payment got declined but I’m thinking it never should have been charged in the first place.
Is this the default behavior, that it will attempt to charge because the default is set to the system payment method?
We don’t want customers getting declines in cases where a customer has multiple cards on file and doesn’t want any of them as the default (meaning our CSRs have to ask which card they want to use for each transaction.)
Thanks for the response. Upon further investigation, this turned out to be a non-issue: the attempted charge was initiated by the customer via the portal, not through my automation schedule.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.