Show credit card error reason @ checkout
I'm currently running 2.1.3 and utilizing Braintree processing at checkout. Currently, if a customer places an error with a bad credit card, wrong CVV number, or wrong address, they just get the error of
An error occurred on the server. Please try to place the order again.
What do I need to change in PaymentInformationManagement.php to override this and show the actual reason for decline? Such as card declined, cvv error, address error, etc.
checkout magento-2.1.2
asked Feb 11 '17 at 3:37
Eric FoxEric Fox
86213
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm currently running 2.1.3 and utilizing Braintree processing at checkout. Currently, if a customer places an error with a bad credit card, wrong CVV number, or wrong address, they just get the error of
An error occurred on the server. Please try to place the order again.
What do I need to change in PaymentInformationManagement.php to override this and show the actual reason for decline? Such as card declined, cvv error, address error, etc.
checkout magento-2.1.2
asked Feb 11 '17 at 3:37
Eric FoxEric Fox
86213
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
The file you are looking for is PaymentDetailsHandler.php. Braintree returns different codes depending on the status of the payment: developers.braintreepayments.com/reference/general/… you would need to check against those codes to determine why the payment failed
– Andrew Noble
Feb 11 '17 at 4:48
add a comment |
I'm currently running 2.1.3 and utilizing Braintree processing at checkout. Currently, if a customer places an error with a bad credit card, wrong CVV number, or wrong address, they just get the error of
An error occurred on the server. Please try to place the order again.
What do I need to change in PaymentInformationManagement.php to override this and show the actual reason for decline? Such as card declined, cvv error, address error, etc.
checkout magento-2.1.2
asked Feb 11 '17 at 3:37
Eric FoxEric Fox
86213
I'm currently running 2.1.3 and utilizing Braintree processing at checkout. Currently, if a customer places an error with a bad credit card, wrong CVV number, or wrong address, they just get the error of
An error occurred on the server. Please try to place the order again.
What do I need to change in PaymentInformationManagement.php to override this and show the actual reason for decline? Such as card declined, cvv error, address error, etc.
checkout magento-2.1.2
checkout magento-2.1.2
asked Feb 11 '17 at 3:37
Eric FoxEric Fox
86213
asked Feb 11 '17 at 3:37
Eric FoxEric Fox
86213
asked Feb 11 '17 at 3:37
Eric FoxEric Fox
86213
asked Feb 11 '17 at 3:37
Eric FoxEric Fox
86213
asked Feb 11 '17 at 3:37
Eric FoxEric Fox
86213
86213
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
The file you are looking for is PaymentDetailsHandler.php. Braintree returns different codes depending on the status of the payment: developers.braintreepayments.com/reference/general/… you would need to check against those codes to determine why the payment failed
– Andrew Noble
Feb 11 '17 at 4:48
add a comment |
The file you are looking for is PaymentDetailsHandler.php. Braintree returns different codes depending on the status of the payment: developers.braintreepayments.com/reference/general/… you would need to check against those codes to determine why the payment failed
– Andrew Noble
Feb 11 '17 at 4:48
The file you are looking for is PaymentDetailsHandler.php. Braintree returns different codes depending on the status of the payment: developers.braintreepayments.com/reference/general/… you would need to check against those codes to determine why the payment failed
– Andrew Noble
Feb 11 '17 at 4:48
The file you are looking for is PaymentDetailsHandler.php. Braintree returns different codes depending on the status of the payment: developers.braintreepayments.com/reference/general/… you would need to check against those codes to determine why the payment failed
– Andrew Noble
Feb 11 '17 at 4:48
add a comment |
1 Answer
1
active
oldest
votes
Magento place order flow provides only high-level errors, it allows to make an application more secure. So it's not a good idea to show specific errors for a customer.
According to Magento Braintree implementation, it based on Hosted Fields, so all card data validation, like card number, expiration dates, CVV processes on the payment form.
answered Feb 11 '17 at 11:35
joni jonesjoni jones
1,836414
So there's no way of showing the customer that the transaction isn't working because of card number, CVV, etc? Instead, they just see a generic message saying there was an error on the server, making them think it's the website, and not their card.
– Eric Fox
Feb 11 '17 at 20:05
You can override default behavior but I don't recommend to do it. Also, I think it's a not particular case when a real card successfully validated on payment form but failed after authorization/sale transaction.
– joni jones
Feb 12 '17 at 8:43
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f159332%2fshow-credit-card-error-reason-checkout%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Magento place order flow provides only high-level errors, it allows to make an application more secure. So it's not a good idea to show specific errors for a customer.
According to Magento Braintree implementation, it based on Hosted Fields, so all card data validation, like card number, expiration dates, CVV processes on the payment form.
answered Feb 11 '17 at 11:35
joni jonesjoni jones
1,836414
So there's no way of showing the customer that the transaction isn't working because of card number, CVV, etc? Instead, they just see a generic message saying there was an error on the server, making them think it's the website, and not their card.
– Eric Fox
Feb 11 '17 at 20:05
You can override default behavior but I don't recommend to do it. Also, I think it's a not particular case when a real card successfully validated on payment form but failed after authorization/sale transaction.
– joni jones
Feb 12 '17 at 8:43
add a comment |
Magento place order flow provides only high-level errors, it allows to make an application more secure. So it's not a good idea to show specific errors for a customer.
According to Magento Braintree implementation, it based on Hosted Fields, so all card data validation, like card number, expiration dates, CVV processes on the payment form.
answered Feb 11 '17 at 11:35
joni jonesjoni jones
1,836414
So there's no way of showing the customer that the transaction isn't working because of card number, CVV, etc? Instead, they just see a generic message saying there was an error on the server, making them think it's the website, and not their card.
– Eric Fox
Feb 11 '17 at 20:05
You can override default behavior but I don't recommend to do it. Also, I think it's a not particular case when a real card successfully validated on payment form but failed after authorization/sale transaction.
– joni jones
Feb 12 '17 at 8:43
add a comment |
Magento place order flow provides only high-level errors, it allows to make an application more secure. So it's not a good idea to show specific errors for a customer.
According to Magento Braintree implementation, it based on Hosted Fields, so all card data validation, like card number, expiration dates, CVV processes on the payment form.
answered Feb 11 '17 at 11:35
joni jonesjoni jones
1,836414
Magento place order flow provides only high-level errors, it allows to make an application more secure. So it's not a good idea to show specific errors for a customer.
According to Magento Braintree implementation, it based on Hosted Fields, so all card data validation, like card number, expiration dates, CVV processes on the payment form.
answered Feb 11 '17 at 11:35
joni jonesjoni jones
1,836414
answered Feb 11 '17 at 11:35
joni jonesjoni jones
1,836414
answered Feb 11 '17 at 11:35
joni jonesjoni jones
1,836414
answered Feb 11 '17 at 11:35
joni jonesjoni jones
1,836414
1,836414
So there's no way of showing the customer that the transaction isn't working because of card number, CVV, etc? Instead, they just see a generic message saying there was an error on the server, making them think it's the website, and not their card.
– Eric Fox
Feb 11 '17 at 20:05
You can override default behavior but I don't recommend to do it. Also, I think it's a not particular case when a real card successfully validated on payment form but failed after authorization/sale transaction.
– joni jones
Feb 12 '17 at 8:43
add a comment |
So there's no way of showing the customer that the transaction isn't working because of card number, CVV, etc? Instead, they just see a generic message saying there was an error on the server, making them think it's the website, and not their card.
– Eric Fox
Feb 11 '17 at 20:05
You can override default behavior but I don't recommend to do it. Also, I think it's a not particular case when a real card successfully validated on payment form but failed after authorization/sale transaction.
– joni jones
Feb 12 '17 at 8:43
So there's no way of showing the customer that the transaction isn't working because of card number, CVV, etc? Instead, they just see a generic message saying there was an error on the server, making them think it's the website, and not their card.
– Eric Fox
Feb 11 '17 at 20:05
So there's no way of showing the customer that the transaction isn't working because of card number, CVV, etc? Instead, they just see a generic message saying there was an error on the server, making them think it's the website, and not their card.
– Eric Fox
Feb 11 '17 at 20:05
You can override default behavior but I don't recommend to do it. Also, I think it's a not particular case when a real card successfully validated on payment form but failed after authorization/sale transaction.
– joni jones
Feb 12 '17 at 8:43
You can override default behavior but I don't recommend to do it. Also, I think it's a not particular case when a real card successfully validated on payment form but failed after authorization/sale transaction.
– joni jones
Feb 12 '17 at 8:43
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f159332%2fshow-credit-card-error-reason-checkout%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The file you are looking for is PaymentDetailsHandler.php. Braintree returns different codes depending on the status of the payment: developers.braintreepayments.com/reference/general/… you would need to check against those codes to determine why the payment failed
– Andrew Noble
Feb 11 '17 at 4:48