Versions Compared

Old Version 82

changes.mady.by.user de Sousa Santos, Rodrigo

Saved on

compared with

New Version Current

changes.mady.by.user Eduardo Javier

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Document Status

Status
colourBlue
titleCLOSED

Closing date

2024-09-02

Document Owner(s)

de Sousa Santos, Rodrigo

Reviewers

...

Erros description

Paycomet Error Code

Operation not allowed for the credit card type

102

Card issuer could not validate card owner

115

CVC2 block incorrect

111

Operation not allowed for the credit card type

130

Country (customer IP address) not allowed

1192

Number of failed attempts (last 30 minutes) from the same ip address exceeded

1202

When the same card has several payments in "flight" at the time that one is finalized, the rest are denied with this code. This restriction is for security

1367

Authorization from different country than card issuer, not allowed

1196

  • The backend will return to the frontend from CommitOrder the response with:

    • code: The new error code with Domains that will be translated to show the error description in the modal;

    • rbiErrorCode: The new error code without Domains;

      • e.g.: 2.001, 2.102.003, 4.004

    • rbiErrorDomain: Domain related to the flow

      • e.g.: PAYMENT, CHECKOUT, CART

    • statusCode: Status code

      • e.g.: 500, 303, 404

    • statusCategory: Status category

      • e.g.: 5XX, 3XX, 4XX

...

Expand
titleWorkflow detailed

Exported Diagram Image

image-20240828-101501.png

Diagram ZenUML

Zenuml sequence macro lite
uuid97952bab-7497-425b-9069-38593d8a8fb7
customContentId4990402773
updatedAt2024-08-26T18:16:31Z
Error Messages
Severity: 2 - NORMAL - Normal User Errors.
image-20240920-201956.pngImage Removed
image-20240911-222215.pngImage Removed
image-20240920-203032.pngImage Removed
image-20240920-203935.pngImage Removed
image-20240920-204034.pngImage Removed
image-20240911-222554.pngImage Removed
image-20240911-222800.pngImage Removed
image-20240911-234208.pngImage Removed
image-20240911-234210.pngImage Removed
image-20240911-234214.pngImage Removed
Paycomet
Key
Description 
Modal Title
Modal Message
Modal CTA
Screen
102
error.PAYMENT.2.001
Operation not allowed for the credit card type
“Card type invalidPayment Declined”
“Your card is does not enabled to allow support this payment type at the moment. Please, contact your bank or try another payment method.”
"Pay another way”image-20240920-201130.pngImage RemovedChange Payment Method”
image-20241001-045844.pngImage Added
130
error.PAYMENT.2.002
Represents errors generated when a transaction is suspected of being fraudulent.
“Something went wrong"
“We had a problem processing this payment. Please 100
Represents an error related to credit/debit card transactions.
“Payment Declined"
“Your card does not support this payment type at the moment. Please, contact your bank or try another payment method.”"
"Pay another way”image-20240920-201716.pngImage RemovedChange Payment Method”
image-20241001-050256.pngImage Added
111
error.PAYMENT.2.100.003
Represents errors generated by internal fraud detection mechanisms within the system.
“Something went wrong"
“We had a problem processing this payment with this payment method. Please contact your bank support or try another payment method"
"Pay another way”
error.PAYMENT.2.004
Represents errors that occur during the validation of transaction data, such as missing mandatory fields, incorrectly formatted data, and other validation failures.
“Validation error”
“001
The payment transaction was rejected because the user informed an invalid card CVV.
“Payment Declined"
“The payment transaction was declined. Please check the Card informationcard name, card number, CVV, expire date and try again.”
"Check the information”image-20240920-202102.pngImage RemovedReview Card Details”
Screenshot 2024-10-02 at 08.26.26.pngImage Added
115
error.PAYMENT.2.100
Represents an error related to credit/debit card transactions.
“Card type invalid"
“Your card is not enabled to allow this payment at the moment. Please, contact your bank or try another payment method."
"Go back”
image-20240920-202324.pngImage Removed101.001
The payment transaction was rejected because card issuer could not validate card owner's identity.
“Payment Declined"
“The transaction was rejected because the card issuer could not verify the cardholder's identity. Try again and authorize the transaction with the card issuer in order to proceed”
"Go Back and Try Again”
Screenshot 2024-10-02 at 09.56.53.pngImage Added
1367
error.PAYMENT.2.100101.001
The payment transaction was rejected because the user informed an invalid card CVV.
“Validation error"
“The payment transaction was declined. Please check the Card information, number, CVV, expire date and try again.”
"Check the information”
image-20240920-202641.pngImage Removed002
Represents an error when In-Flight offline payments are rejected.
An example of occurrence is when the same card has several payments in "flight" at the time and one is finalized, the rest might be denied.
“Payment Failed”
“Sorry, we are unable to process this payment. Please verify the payment in your bank platform or use another payment method.”
"Go Back and Try Again”
Screenshot 2024-10-09 at 01.02.59.pngImage Added
1192
error.PAYMENT.2.102.101002
Represents errors that arise during the payment processing phase, such as failures in communicating with the payment gateway, billing errors, and other issues that may occur while processing a payment.
“Something went wrong"
“We were unable to process this payment due to internal errors. Please try again later.”
"Go back”
image-20240920-202742.pngImage Removedan error when the user's IP address is not from an allowed country.
Ex.: Iberia payments only allowed from Spain and Portugal.
“Payment Declined"
“It seems you're connecting from a different country, and we're unable to process your order. ”

"Go Back”
Screenshot 2024-10-15 at 10.22.01.pngImage Added
1202
error.PAYMENT.2.101102.001
The payment transaction was rejected because card issuer could not validate card owner's identity.
“Identity error"
“Sorry, we were unable to verify the cardholder's identity. Please use another payment method.”
"Go back”
error.PAYMENT.2.101.002
Represents an error when In-Flight offline payments are rejected.
An example of occurrence is when the same card has several payments in "flight" at the time and one is finalized, the rest might be denied.
“Something went wrong”
“Sorry, we are unable to process this payment. Please use another payment method.”
"Go back”
error.PAYMENT.2.102
Represents errors generated when a transaction is rejected as restricted by PSP or issuer.
“Something went wrong”
“Sorry, we are unable to process this payment. Please use another payment method."
"Go back”
error.PAYMENT.2.102.001
Operation is not allowed for this card type.
“Card type invalid”
“Your card is not enabled to allow this payment at the moment. Please, contact your bank or try another payment method.”
"Pay another way”
error.PAYMENT.2.102.002
Represents an error when the user's IP address is not from an allowed country.
Ex.: Iberia payments only allowed from Spain and Portugal.
“Location Invalid"
“You cannot place orders from this country at this store. Please choose another store and try again.”
"Go back”
error.PAYMENT.2.102.003
Represents an error when the number of failed attempts from the same user has been exceeded.
“Order limit exceeded"
“You have exceeded the number of attempts to place an order. Please try again later.”
"Go back”
Severity: 4 - ABNORMAL
error.PAYMENT.4.000
General, unspecified payment error.
“Failed Payment”
“Something went wrong with this payment. Please try again later”
"Go back”
error.PAYMENT.4.001
Represents errors related to security and authentication within the payment system.
Impact: All the payment transactions are failing.
Solution: Investigate security related settings, like secrets.
“Failed Payment”
“Something went wrong with this payment. Please try again later”
"Go back”
error.PAYMENT.4.002
Represents errors arising from system configuration issues.
Impact: All the payment transactions are failing.
Solution: Review the configuration for the specific service and PSP.
“Failed Payment”
“Something went wrong with this payment. Please try again later”
"Go back”
image-20240911-234208.pngImage Removed
error.PAYMENT.4.003
Represents errors related to internal connection problems, such as failures in communication between microservices, internal network issues, or connectivity problems with the Payment Service Provider (PSP).
Solution: Investigate communication-related infrastructure issues
“Failed Payment”
“Something went wrong with this payment. Please try again later”
"Go back”
image-20240911-234208.pngImage Removed
error.PAYMENT.4.004
Represents errors associated with database operations within the system.
“Failed Payment”
“Something went wrong with this payment. Please try again later”
"Go back”
error.PAYMENT.4.005
Represents errors caused by failures in third-party connections with external services necessary for the transaction, such as banks, payment gateways, identity verification services, etc.
“Failed Payment”
“Something went wrong with this payment. Please try again later”
"Go back”
image-20240911-234208.pngImage Removed
error.PAYMENT.4.006
Represents errors that occur due to external factors not directly related to the internal infrastructure of the payment system.
“Failed Payment”
“Something went wrong with this payment. Please try again later”
"Go back”
image-20240911-234208.pngImage Removed
error.PAYMENT.4.007
Represents errors that occur at the service layer, such as internal service failures, configuration issues, or other problems that prevent the service from functioning as expected.
“Failed Payment”
“Something went wrong with this payment. Please try again later”
"Go back”
image-20240911-234208.pngImage Removed
error.PAYMENT.4.008
Represents errors that occur during the internal processing of payment transactions.
Ex.: Payment not found for the given rbiOrderId
“Failed Payment”
“Something went wrong with this payment. Please try again later”
"Go back”
image-20240911-234208.pngImage Removed003
Represents an error when the number of failed attempts from the same user has been exceeded.
“Order Attempts Exceeded"
“You have exceeded the number of attempts to place an order. Please try again in X minutes.”

(30min for Paycomet)
"Go Back and Try Again Later”
Screenshot 2024-10-15 at 10.22.40.pngImage Added
1196
PAYMENT.2.102.005
Authorization from different country than card issuer, not allowed

“Payment Declined”
“Unfortunately, payments from different country than card issuer are not allowed on this platform. Please use a card issued in the same country or change your payment method.”
“Change Payment Method”
Screenshot 2024-10-09 at 01.07.27.pngImage Added
Old Methods
Until that migration starts, we will deprecate the methods mapErrorsWithCodes and parseGraphQLErrorCodes to prevent the creation of new error flows using the "old" approach, encouraging the adoption of the new model.
...
 Expand
titleErrorDialogComponent details
 Code Block
const ErrorDialogComponent: UseErrorDialogHook<P>[0] = useCallback(
    ({
      buttonLabel = formatMessage({ id: 'okay' }),
      heading = formatMessage({ id: 'somethingWrong' }),
      image,
      ...rest
    }) => {
      ...
      const pendingRbiError = delve(pendingData as T, 'error', null);

      ...

      const modalAppearanceEvent = isRBIError(pendingRbiError)
        ? undefined
        : modalAppearanceEventMessageOverride.current || modalAppearanceEventMessage;

      const errorEventMessage = isRBIError(pendingRbiError)
        ? undefined
        : errorEventMessageOverride.current;

      return (
        <Dialog
          heading={title || heading}
          body={dialogBody}
          image={image}
          onDismiss={dismissDialog}
          actions={actions}
          modalAppearanceEventMessage={modalAppearanceEvent}
          errorEventMessage={errorEventMessage}
          aria-label="error"
          {...rest}
        />
      );
    },
    ...
  );
How to use the new error 
...
modal?
After all these changes, when it’s needed to use the new error modelmodal:
import the useErrorModal:
...