If you are using OpenEdge, it is possible to allow your users to save payment methods for future use. You can learn more about how cards-on-file works.
Store a Payment Method During Checkout
When you save a payment method, there are two ways to store it. The first way is if the user would like to store a payment method during checkout.
The user will see the payment form, including an amount owed. Behind the scenes, OpenEdge will store the payment information for future use.
You can confirm if a payment method was successfully saved by looking in the CP Pay history log.
Store a Payment Method Outside of a Transaction
The second way to store a payment method is outside of a transaction. For example, if a user would like to update their card on file before the next billing cycle.
In this example, they would be presented with a very similar form, except that the amount owed is $0. Behind the scenes, the card is being verified by performing a $0 authorization. However, since no funds for flagged for settlement, no payment will go through.
These types of transactions can be confirmed using the OpenEdge Transaction Finder. They will show as “Auth” and not as “Sale”.
These types of transactions will show in the CP Pay activity log as well. They will be listed as “Saved Payment Method Creation”.
Store an ACH (Bank Account) on File
You can store ACH as a payment method just like credit cards and debit cards with one exception. Before checking out, the user may choose if they want to save their payment method, if so, behind the scenes OpenEdge will store this information. The user will be presented with the ACH form.
The one exception is that you cannot store ACH outside of a transaction. $0 authorizations is not supported at this time.