...
As an alternative, you can create your own recurring transaction database. In this case, there are a few required fields you will need to submit in order to be in accordance with card brand mandates - see recurring payment guidelines here.
Because the customer's information (e.g. address) remains linked to each token, issuer declines due to AVS mismatch or similar are a lot less likely. If your client would like to be able to keep multiple payment methods on file, they can save multiple tokens per customer.
Note:
| Info |
|---|
Saving AVS information on a Customer is not required to create a token. However, it is strongly recommended that it be saved to the record to increase successful recurring and card-on-file transactions with the token. |
| Child pages (Children Display) |
|---|