Fortezza Card Error Codes
Contents |
there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug. Skip to credit card declined error codes main content Mozilla About Developers Store Support Products search mozilla: Roadmap Projects
Credit Card Processing Error Codes
Coding Module Owners Hacking Get the Source Build It Testing Releases Nightly Builds Report A Problem Tools Bugzilla Tinderbox credit card response codes Bonsai LXR FAQs Table of Contents | Previous | Next | Index Chapter 8 NSS and SSL Error Codes NSS error codes are retrieved using the NSPR function PR_GetError. In
Visa Decline Codes
addition to the error codes defined by NSPR, PR_GetError retrieves the error codes described in this chapter.SSL Error Codes SEC Error Codes SSL Error Codes Table 8.1 Error codes defined in sslerr.h Constant Value Description SSL_ERROR_EXPORT_ONLY_SERVER -12288 "Unable to communicate securely. Peer does not support high-grade encryption." The local system was configured to support the cipher suites permitted for domestic use. The list of credit card declined codes remote system was configured to support only the cipher suites permitted for export use. SSL_ERROR_US_ONLY_SERVER -12287 "Unable to communicate securely. Peer requires high-grade encryption which is not supported." The remote system was configured to support the cipher suites permitted for domestic use. The local system was configured to support only the cipher suites permitted for export use. SSL_ERROR_NO_CYPHER_OVERLAP -12286 "Cannot communicate securely with peer: no common encryption algorithm(s)." The local and remote systems share no cipher suites in common. This can be due to a misconfiguration at either end. It can be due to a server being misconfigured to use a non-RSA certificate with the RSA key exchange algorithm. SSL_ERROR_NO_CERTIFICATE -12285 "Unable to find the certificate or key necessary for authentication." This error has many potential causes; for example: Certificate or key not found in database. Certificate not marked trusted in database and Certificate's issuer not marked trusted in database. Wrong password for key database. Missing database. SSL_ERROR_BAD_CERTIFICATE -12284 "Unable to communicate securely with peer: peers's certificate was rejected." A certificate was received from the remote system and was passed to the certificate auth
SUMMARY Below you'll find explanations of decline codes you may have encountered as well as potential solutions. Declines are made by the card-issuing bank,
Credit Card Declined Codes 05
not your software. If your client does not believe their card
Credit Card Declined Code 200
should have declined, please advise them to call the 1-800 on the back of the card for credit card error messages more information. If you receive a decline that is not listed on this page please contact Merchant Support. Declined - 30002: DECLINED This means that the card holder's credit http://www-archive.mozilla.org/projects/security/pki/nss/ref/ssl/sslerr.html card company has blocked the transaction. Have the client call the 800 number on the back of the card and find out why. Declined - 30009: EXCEPTION This means your merchant account has been deactivated pending receipt of your W-9 document. Download a W-9 here. Take a photo and mail it to 1099Group@elavon.com or fax it to 1-877-304-0975. If you https://support.mindbodyonline.com/hc/en-us/articles/203255323-U-S-credit-card-decline-codes have questions about receipt or time frame to reactivation, contact Elavon at 1-844-878-7493. 01 Call This means that the card holder's credit card company has blocked the transaction. Have the client call the 800 number on the back of the card and find out why. 02 Call This means that the card holders credit card company has blocked the transaction. Have the client call the 800 number on the back of the card and find out why. 04 Hold-call or Pick Up Card Merchant to keep the card. There is a problem with the card. Call the 800 number on the back of the card to determine the issue. 05 Decline Do not honor. The customer's credit card company is telling you not to honor the card. There is a problem with their account or they don't recognize the billing address on file. Add the cardholder's correct billing address to the Billing Info and try the card one more time. If it continues to decline, call the 800 number on the
text renditions for the ultimate authority. The Open Group R. Salz (OpenGroup) Request For Comments: 100.0 January, 1997 DCE AND FORTEZZA INTRODUCTION This document discusses how to http://www.opengroup.org/rfc/rfc100.0.html integrate the Fortezza card with DCE. We propose a two-phase approach: first, use of the card as an instance of the DCE 1.2.2 public-key login technology; and second, use of the card as the cryptographic engine of a full PKI. In order for this document to be self-contained, we start with a introduction to the various aspects of DCE login. We then introduce the card. credit card We then discuss how the Fortezza card might be integrated into the DCE login suite. The next section briefly touches on more complete integration of the card, as part of full DCE support for multi-crypto. Finally, we list some of the issues that will need to be resolved; this last section is probably the most important area of this document. Background Information Introduction to DCE credit card declined login Logging in to DCE, also known as obtaining network credentials, is achieved by obtaining a ticket-granting-ticket, TGT, to the DCE privilege service. This is done via two API's: sec_login_setup_identity, and sec_login_validate_identity. Historically, the first requests an encrypted TGT from the security service, and the second uses the provided user password to generate a key and decrypt the TGT, allowing it to be used in the process of making all future authenticated RPC's. (The pre-authentication protocols added in DCE 1.1 shift the work a bit, so that only the username is validated in the first part, and a strongly-encrypted request proving knowledge of the password is made in the second part.) In DCE 1.2.2, the APIs have been preserved, but the implementation has undergone significant changes to allow public-key based cryptography to be used for login. See [RFC 68] for more details. In the protocol definitions below, the common notation {xxx}Sc means that xxx is signed by c, or encrypted if Pc is used. Client-->KDC: {TrustedRoots, Checksum, Time, Nonce, KDCName}Sc That is, the client sends an optional list of the root CA's that it trusts, a checksum and a nonce (plaintext confounder), its value