Code and Message errors are returned when an HTTP 400 error occurs.
Errors returned in Code and Message
Code and MessageThe Code and Message parameters appear in the response body when an HTTP error occurs, usually a 4xx. They detail the cause of the failure in the request or processing, allowing you to quickly identify the problem.
Code: numeric code that identifies the error type;Message: text message describing the error.
Example
See below an example of a response body for a VerifyCard request when there's an error in MerchantId
[
{
"Code": 114,
"Message": "The provided MerchantId is not in correct format"
}
]Important:
CodeandMessagefollow the same values asProviderReturnCodeandProviderReturnMessage, but are returned in different situations.ProviderReturnCodeandProviderReturnMessageindicate the business result (with the provider/acquirer) in HTTP 2xx responses.The specific codes and messages apply to the Cielo acquirer; for other acquirers, check the corresponding documentation.
How to handle Code and Message errors?
Code and Message errors?- Fix the submitted data: check required fields, formats, and sizes;
- Check credentials:
MerchantIdandMerchantKey; - Confirm the enabled services on the Cielo website, under the E-commerce tab;
- Confirm authorized IPs on the Cielo website;
- Check API Status for persistent 5xx errors.
Code and Message table
Code and Message tableCode and Message show the same values as ProviderReturnCode and ProviderReturnMessage, but are returned in different situations:
- The
ProviderReturnCodeandProviderReturnMessagevalues are returned in successful HTTP operations (200 or 201); - The
CodeandMessagevalues are returned in HTTP error operations (e.g., 400).
The table below lists the codes and messages specific to the Cielo acquirer. If the merchant uses another acquirer integrated with the Gateway, check that acquirer's documentation for the equivalent codes and messages.
See the full table:
| Reason Code | Reason Message |
|---|---|
| 00 | Successful |
| 01 | AffiliationNotFound |
| 02 | IssuficientFunds |
| 03 | CouldNotGetCreditCard |
| 04 | ConnectionWithAcquirerFailed |
| 05 | InvalidTransactionType |
| 06 | InvalidPaymentPlan |
| 07 | Denied |
| 08 | Scheduled |
| 09 | Waiting |
| 10 | Authenticated |
| 11 | NotAuthenticated |
| 12 | ProblemsWithCreditCard |
| 13 | CardCanceled |
| 14 | BlockedCreditCard |
| 15 | CardExpired |
| 16 | AbortedByFraud |
| 17 | CouldNotAntifraud |
| 18 | TryAgain |
| 19 | InvalidAmount |
| 20 | ProblemsWithIssuer |
| 21 | InvalidCardNumber |
| 22 | TimeOut |
| 23 | CartaoProtegidoIsNotEnabled |
| 24 | PaymentMethodIsNotEnabled |
| 25 | CouldNotFindPaymentToken |
| 26 | MerchantIdJustClickNotFound |
| 27 | BrandNotSupported |
| 28 | CardOptionsNotSupported |
| 29 | WalletKeyIsInvalid |
| 30 | MerchantWalletConfigurationNotFound |
| 31 | BoletoRequiredDataNotSupported |
| 32 | ConnectionWithAntifraudFailed |
| 33 | AbortedByCardVerification |
| 34 | ProblemsWithAcquirer |
| 35 | ValidationError |
| 36 | AcquirerTransactionNotFound |
| 37 | SplitTransactionalError |
| 38 | MerchantSplitConfigurationNotFound |
| 39 | SplitSoftDescriptorIsRequired |
| 40 | SplitFraudAnalysisIsRequired |
| 41 | SplitAntifraudMerchantConfigurationNotFound |
| 42 | ProviderNotFound |
| 43 | PaymentSettingsNotFound |
| 44 | SubAcquirerMerchantConfigurationNotFound |
| 45 | AbortedBySubAcquirer |
| 98 | InvalidRequest |
| 99 | InternalError |
| 100 | CieloPayCardHolderIsNotActive |
| 101 | CieloPayStrongValidationIsInvalid |
| 102 | CieloPayExpireDateDoesNotMatch |
| 103 | CieloPayCardHolderApiError |
| 104 | SplitPaymentFacilitatorDataNotFound |