This version will be released on the 8th of October 2024!
SYSTEM INTERNALS
Fixes & Updates:
- Update Statuses for:
- 3DS Transactions
- Since the MPI provider now receives specific issuer decline codes from the SCA, merchants and users will receive detailed decline messages rather than the generic “3DS Authentication Failed.”
- The new decline codes are detailed in our documentation and below:
- Advice Codes
- We have modified the advice codes to better align them with those provided by the issuer.
Status Code | Description |
41135 | Unsupported Payment Method |
43006 | Unknown/Unsupported Device |
43007 | Card exceeds authentication frequency limit |
43022 | Expired Card |
43019 | Invalid Card Number |
43012 | Invalid Transaction |
43014 | Wrong Card Number |
43043 | Card Reported as Stolen |
43059 | Suspected Fraud |
43057 | Transaction not Permitted to Cardholder |
43011 | Transaction exceeds maximum number of challenges |
43097 | Decoupled Authentication Cannot be Performed |
43098 | Decoupled Authentication Expiry Time Exceeded |
43099 | Decoupled Authentication Not Attempted Due To Insufficient Auth Time |
43092 | Error Connecting to ACS |
43093 | ACS Timed Out |
43010 | VMID Issue With Participation in The Requested 3DS Program |
43095 | The 3DS Protocol Used for This Transaction is Either Outdated or Too Advanced for The ACS to Handle |
43090 | 3RI Transaction is not Qualified for Attempts Processing Under 3DS Protocol |
46999 | Unmapped Decline |
Fibonatix AC | Description |
AC01 | Cannot approve at this time, try again later |
AC02 | New account information available - check and retry |
AC03 | Retry with 3DS |
AC04 | Try again after 24 hours |
AC06 | Contact your customer success manager or merchant support |
AC07 | Do not try again (the issuer will never approve) |
AC08 | Try again in 1 hour |
AC09 | Try again in 2 days |
AC10 | Try again in 4 days |
AC11 | Try again in 6 days |
AC12 | Try again in 8 days |
AC13 | Try again in 10 days |
AC14 | Do not try again with the same card |
AC15 | Try using a different card/payment method |
AC16 | Try using a different card/payment method or contact your bank for further clarification |
AC19 | Use a different device |
- Cascading – added an extra parameter for the cascading option: '3DS Cascading Statuses.'
- This allows us to select which 3DS request statuses will be forwarded during cascading (default options are Y, A, N, U).
- The letters Y, A, N, and U in the context of 3DS (Three-Domain Secure) statuses generally represent different authentication outcomes during the 3D Secure transaction process:
- Y – Authentication Successful (the cardholder's identity has been verified).
- A – Authentication Attempted (the cardholder attempted authentication, but the result isn't definitive; typically, liability shift may still apply).
- N – Authentication Failed (the cardholder was not authenticated).
- U – Authentication Unavailable (the authentication service was unavailable for some reason, such as a system error or the issuer being unable to respond).
These codes are used to determine how to handle transactions based on the result of the 3DS authentication process.
- Changed the default error code in the processor.
- When we are unable to map an error code received from processors, we will now set the status to 46999 'Unmapped Decline' (previously 46001).
USER INTERFACE
Fixes & Updates:
- Dashboard Widget Addition
- Allow users to create widgets for each payment method (MC/Visa/AP/GP).
- Display decline graphs highlighting the top 5 decline reasons, with all other reasons grouped under "Others."
New Features:
- Added 'Create Ticket' Button in Paragon
- Simplifies the process for merchants to open a ticket with Merchant Support through the back office. Click here for instructions on how to open a ticket in Paragon
- Standard Reports
- Added templates with pre-defined filters to improve usability.
- Blocking Transactions by IP Address / BIN Country
- Block transactions based on Logic Hub definitions.