Никак не могу разобраться в чем дело. Пробовал разные методы. Звонил в банк, копался в инете. Сделал как сказано в статье — не помогло.
Порядок вывода комментариев:
Acht
3
0
07.07.2017 в 16:32
Я удалил ваш скриншот. Никогда не показывайте людям код карты и код безопасности.
Ошибка:
your payment method was declined. please enter another payment method
Так случается, когда вы делали покупки в App Store (или имели подписку) и ушли в минус. Для начала, надо убедиться, что у вас положительный баланс на счету. После этого сотрите Security Code и введите его заново. Либо, попробуйте сохранить неверный Security Code, а потом вернитесь к правильному.
Либо просто данные заполнены неверно.
Apple рекомендует в таких случаях следующее.
Убедитесь, что ваше имя и адрес совпадают с информацией в вашем финансовом учреждении.
Убедитесь, что платежный аккаунт, который вы используете, находится в хорошем состоянии.
Если вы используете кредит в магазине, убедитесь, что добавили достаточный кредит в свой аккаунт, чтобы покрыть ваши покупки.
Если вы можете использовать любой из этих способов оплаты . Вы не можете выбрать «Нет», когда у вас есть неоплаченный остаток или платеж.
Гость
0
07.06.2019 в 19:51
я гей
Гость
0
01.10.2019 в 14:45
Хочется из айпада галакси фолд сделать. Эпл ты что заебал?
Похожие вопросы
Why are Cards Declined?
A credit card transaction can be declined for several reasons. Sometimes you can tell why it was declined by reading the response code, but only the customer’s credit card issuer or financial institution can confirm the specific reason.
Here are a few of the major possibilities:
-
Incorrect credit card number or expiration date
-
Insufficient funds
-
Some credit card companies will reject international charges.
-
The customer’s bank or credit card company was having technical issues when the order was processed
-
If the customer made a large number of online purchases within a short period of time, some banks will reject some of the charges as a fraud prevention measures.
When Should I Retry a Declined Card?
Declines can be tricky. It’s tough to know if the card was declined for temporary issues and you can retry the transaction or if you’ll need to reach out to the customer for an alternative form of payment. Basically, there are two types of declines: hard declines and soft declines.
Hard declines should not be retried, as the reason the card is being declined is not temporary and subsequent tries will likely not be successful. On the other hand, soft declines are typically temporary issues such as a high level of recent activity on a card, a lack of matching AVS information or a card being over its limit. Let’s dive deeper into the details of each type of decline and some common decline codes associated with them.
Hard Declines
When cards are declined with the messages below, it’s unlikely that they will ever be successful on a subsequent attempt. In many cases, there is action required by the card issuing bank or cardholder before the issue will be resolved. A few common examples are listed below.
2047: Call Issuer. Pick Up Card
This message is intended for merchants in card-present environments, and can be confusing for online merchants. This error indicates that the card has been reported as lost or stolen by the cardholder. The card company is requesting that the merchant keep the card and call the number on the back to report it. In instances where you see this processor response, we recommend obtaining a different credit card from the customer.
2005: Invalid Credit Card Number
This message indicates that the credit card number is not associated with an active account.
2004: Expired Card
This message indicates that the credit card has expired and is no longer active.
2010: Card Issuer Declined CVV
This message indicates that the transaction was not approved because the CVV did not match what is on file with the card-issuing bank.
2015: Transaction Not Allowed
This response indicates that the card issuing bank is declining the transaction for unspecified reasons. The response doesn’t necessarily indicate that there is a problem with the card; however, it does indicate that the bank won’t approve this transaction.
Soft Declines
Cards failing with the following responses may be successful with a subsequent attempt. We usually recommend that merchants reattempt the transaction up to three additional times over the subsequent week or two if they are unable to reach the cardholder, as some of the reasons a card may be declined with this message can resolve themselves over that time period. If subsequent attempts all fail, we suggest reaching out to the customer to obtain an alternate form of payment. It is very unlikely that a card will be successful on the fourth or fifth attempt. A few common examples are listed below.
2000: Do Not Honor
A generic bank response which indicates simply that they are not willing to accept the transaction. The transaction may be declined due to a high level of recent activity on a card, a lack of matching AVS information, a card being over its limit, or a range of other reasons which only the bank knows.
2001: Insufficient Funds
The card doesn’t have the available funds today, but may be successful a different day.
2038: Processor Declined
This is a generic bank response which indicates simply that they are not willing to accept the transaction. The transaction may be declined due to a high level of recent activity on a card, a lack of matching AVS information, a card being over its limit, or a range of other reasons which only the bank knows.
2046: Processor Declined
This is a fairly generic response that many issuing banks will send back when declining a transaction. The transaction may be declined due to a high level of recent activity on a card, a lack of matching AVS information, a card being over its limit, or a range of other reasons which only the bank knows.
This card may be successful on a different day or you may need to call the bank for voice authorization.
Two of the most frequently returned response codes, 2046 and 2038 indicate that the customer’s bank is unwilling to accept the transaction — they are returned when payment authorization has been declined at the issuing bank. The causes for either are diverse and difficult to pin down without contacting the bank, but typical ones include a high level of recent activity on the card, an incorrect card number or expiration date entered on the checkout page, insufficient funds in the associated bank account, the card being over its limit and a rejection based on fraud filters at the bank. Being a soft decline (the result of a temporary issue), the best way to troubleshoot this error is to simply retry the card at a later time.
Another way to tackle this error is to enable card address fields on your chargebee web interface. This reduces 2046/2038 declines in that it makes information that is required at the issuing bank mandatory at checkout.
Navigate to Settings >> Billing >> Billing Rules >> Card Address Verification and mark address lines and CVV as mandatory.
If the error persists, consider contacting the customer with a request to try a different payment method and/or send a query to her bank.
Загрузка…
Why are Cards Declined?
A credit card transaction can be declined for several reasons. Sometimes you can tell why it was declined by reading the response code, but only the customer’s credit card issuer or financial institution can confirm the specific reason.
Here are a few of the major possibilities:
When Should I Retry a Declined Card?
Declines can be tricky. It’s tough to know if the card was declined for temporary issues and you can retry the transaction or if you’ll need to reach out to the customer for an alternative form of payment. Basically, there are two types of declines: hard declines and soft declines.
Hard declines should not be retried, as the reason the card is being declined is not temporary and subsequent tries will likely not be successful. On the other hand, soft declines are typically temporary issues such as a high level of recent activity on a card, a lack of matching AVS information or a card being over its limit. Let’s dive deeper into the details of each type of decline and some common decline codes associated with them.
Hard Declines
When cards are declined with the messages below, it’s unlikely that they will ever be successful on a subsequent attempt. In many cases, there is action required by the card issuing bank or cardholder before the issue will be resolved. A few common examples are listed below.
2047: Call Issuer. Pick Up Card
This message is intended for merchants in card-present environments, and can be confusing for online merchants. This error indicates that the card has been reported as lost or stolen by the cardholder. The card company is requesting that the merchant keep the card and call the number on the back to report it. In instances where you see this processor response, we recommend obtaining a different credit card from the customer.
2005: Invalid Credit Card Number
This message indicates that the credit card number is not associated with an active account.
2004: Expired Card
This message indicates that the credit card has expired and is no longer active.
2010: Card Issuer Declined CVV
This message indicates that the transaction was not approved because the CVV did not match what is on file with the card-issuing bank.
2015: Transaction Not Allowed
This response indicates that the card issuing bank is declining the transaction for unspecified reasons. The response doesn’t necessarily indicate that there is a problem with the card; however, it does indicate that the bank won’t approve this transaction.
Soft Declines
Cards failing with the following responses may be successful with a subsequent attempt. We usually recommend that merchants reattempt the transaction up to three additional times over the subsequent week or two if they are unable to reach the cardholder, as some of the reasons a card may be declined with this message can resolve themselves over that time period. If subsequent attempts all fail, we suggest reaching out to the customer to obtain an alternate form of payment. It is very unlikely that a card will be successful on the fourth or fifth attempt. A few common examples are listed below.
2000: Do Not Honor
A generic bank response which indicates simply that they are not willing to accept the transaction. The transaction may be declined due to a high level of recent activity on a card, a lack of matching AVS information, a card being over its limit, or a range of other reasons which only the bank knows.
2001: Insufficient Funds
The card doesn’t have the available funds today, but may be successful a different day.
2038: Processor Declined
This is a generic bank response which indicates simply that they are not willing to accept the transaction. The transaction may be declined due to a high level of recent activity on a card, a lack of matching AVS information, a card being over its limit, or a range of other reasons which only the bank knows.
2046: Processor Declined
This is a fairly generic response that many issuing banks will send back when declining a transaction. The transaction may be declined due to a high level of recent activity on a card, a lack of matching AVS information, a card being over its limit, or a range of other reasons which only the bank knows.
This card may be successful on a different day or you may need to call the bank for voice authorization.
I am trying to test out the Braintree Payments sandbox environment and it is working fine for some payments but not all.
In some payments I am seeing the transaction in Braintree but it has an error processor declined(2409)
According to Braintree’s documentation this means:
The customer’s bank is unwilling to accept the transaction. The customer will need to contact their bank for more details regarding this generic decline.
However, I was using the sandbox and it happens with PayPal and the card numbers provided by Braintree for testing.
It seems to only be happening for larger amounts. Am trying to test this now to see what the cut off amount is or if it is just coincidence. At the moment it is working for payments over 1000 but not over 2000.
Does anyone know if this is some sort of limit in the sandbox or has this happened to anyone before. I am worried this will affect the production environment but cannot test a transaction over 2000.