Braintree 91518: Payment method token is invalid
What This Means
Braintree declined this transaction due to an issue with the token values used for the customer's saved payment method. Braintree error code 91518 means that a payment method token is not found in your Braintree Vault.
Common Causes For This Error
An issue with the "payment_method_token" usually means one of the following:
- The Gateway PaymentId is incorrect or has been changed in the Gateway
- The payment token sent to Braintree does not match the payment token for the Customer's billing profile in your Braintree Vault
Suggested Next Steps
-
Search for the customer in the Braintree Vault to confirm that this Customer's billing profile can or cannot be found.
- If a new payment profile can be found, you can edit the Scheduled Order and create a new payment method for this Scheduled Order by copying the Customer's billing information into their Scheduled Order (see "Adding A New Payment Method for Your Customer?" below).
-
If a new payment method is needed, contact the customer to have them add a new payment method and add it to their Scheduled Order.
-
You may also choose to add a new payment method for your customer, see "Adding a New Payment Method for Your Customer" below.
-
Once a new payment method is added to the Scheduled Order, the Scheduled Order should be processed with the new payment method.
Adding A New Payment Method for Your Customer?
If you are adding a new payment method for your customer directly to your payment gateway (manually), ensure that you edit the failed Scheduled Order, add a new payment method, and copy the required billing information from your payment gateway directly to their Scheduled Order including:
- Gateway CustomerId
- Gateway PaymentId
- Billing Address
- Payment Method Description (optional, but strongly suggested because it is used to display the payment method to your customer)
After Resolving The Issue
Once this issue is resolved, you should use the action to Restart Processing the Failed Scheduled Order.
Updated almost 2 years ago