Update - We are working to restore service with the previous version.
Apr 25, 2024 - 22:25 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 25, 2024 - 21:15 CEST
Scheduled - The latest version of the platform is here, affecting the components listed below.
As this is a major release, we estimate a downtime of 15 minutes during this intervention, with all requests responding with the HTTP Response code 503; we apologize for any inconvenience this may cause in the meantime.
What’s new & Improvements
This version includes performance improvements and bug fixes.
Merchant Panel
Chargeback Transactions Custom Fields
For Chargeback transactions, the fields Custom1, Custom2, and Custom3, provided with the original transaction will be displayed in the Merchant Panel
Failed Authorizations
When an Authorization has failed, for example, due to errors in 3D Secure User Authentication, it is now visible with the Transaction Status "Failed" in the Merchant Panel.
Web API
New Status "Failed" for Failed Authorizations
When a transaction fails during the authorization process, the transaction will be marked as status "Failed". Failed Authorizations are visible in the Merchant Panel.
New Validation and API Response Code
A validation with response code 0629 has been introduced to the API Call Complete Add Stored Payment Option. It prevents storing a Payment Option for a PaymentOptionCode different than the one provided in the related Init Add Stored Payment Option request.
Dot-less Domain Support for Dev Environments
URL Input Validation has been altered to allow dot-less domains for flexibility in development environments. This means, for example, URLs such as https://localhost/test are allowed for development purposes.
For the best compatibility with the widest range of external systems and payment providers, it's still strongly recommended for Merchants to use HTTPS Absolute URLs, including a top-level domain.
General Changes
Rate Limiting
Rate Limiting of all API Requests has been implemented to avoid instability due to unexpected peaks in demand, for example "Black Friday" Sales events. In case you are expecting high demand, please reach out to your Customer Relationship Manager.
SDK Change
Dot-less Domain Support for Dev Environments
URL Input Validation has been altered to allow dot-less domains for flexibility in development environments. This means, for example, URLs such as https://localhost/test are allowed for development purposes.
For the best compatibility with the widest range of external systems and payment providers, it's still strongly recommended for Merchants to use HTTPS Absolute URLs, including a top-level domain.
SDKs Latest Versions
Periodically updates are released to the web and mobile SDKs, which can include new functionality, bug fixes, and security updates.
We urge all stakeholders to update integrated SDK versions to the newest version as soon as these are available as the following link.
The latest SDK version is always available from our documentation website.
The latest version numbers are: Web – v9.0 iOS – v9.0 Android – v9.0
SmartPay customers do not need to take any action.
Rollback possible: Yes
All maintenance work can be considered complete once this has been announced on the status page i.e. please assume the environment is undergoing maintenance until you receive confirmation of successful conclusion.
Unless otherwise stated, we do not expect any incompatibility to be introduced by this change, despite this, to ensure your customer base continues to enjoy the same experience prior to the introduction of this change in other environments, we recommend executing regression tests immediately following the successful conclusion of this deployment and raising a service request explicitly asking to halt further deployment in other environments should a concern be identified based on your existing integration.
We appreciate your patience and understanding. As always, if you have questions relating to or issues following the upgrade with your existing integration, please write to support@jpmmps.com
Apr 25, 202421:15-22:15 CEST
The invoices for the month of March 2024 will be delayed due to an internal accounting system problem. We are working on a fix and we hope to deliver the invoices as soon as possible.
This is the service-status and incident communication site for J.P. Morgan Mobility Payments Systems GmbH. This service is jointly operated with J.P. Morgan Mobility Payments Solutions S.A. Updates and planned maintenance announcements are communicated here. Please use the "subscribe to updates" button to receive email notifications.
EUROPE LIVE
Under Maintenance
EU Production API
?
Under Maintenance
EU Merchant Panel
Under Maintenance
EU E-Wallet Portal
?
Under Maintenance
EU Payment Gateway
?
Operational
EU Production SFTP
Operational
EUROPE TEST
Operational
EU Sandbox API
?
Operational
EU Prerelease-Sandbox API
?
Operational
EU Sandbox E-Wallet Portal
?
Operational
EU Sandbox Merchant Panel
Operational
EU Prerelease-Sandbox E-Wallet Portal
?
Operational
EU Test Payment Gateway
?
Operational
EU SmartPay
Under Maintenance
EU SmartPay LIVE
Under Maintenance
EU SmartPay SANDBOX
Operational
Statuspage
Operational
Statuspage SMS Notifications
Operational
Statuspage Email Notifications
Operational
EUROPE SmartPay Subscriptions
Under Maintenance
EU SmartPay Subscriptions - TEST
Operational
EU SmartPay Subscriptions - LIVE
Under Maintenance
In an effort to continue providing the best possible service, CRIF will be conducting a planned maintenance affecting the components listed below.
- Sanctions Screening
All maintenance work can be considered completed once this has been announced on the status page i.e. please assume the environment is undergoing maintenance until you receive confirmation of successful conclusion.
We appreciate your patience and understanding. As always, if you have questions or issues, please write to support-vwpayments@vwfs.com Posted on
Jan 04, 2024 - 11:03 CET
In an effort to continue providing the best possible service, CRIF will be conducting a planned maintenance affecting the components listed below.
This issue affects all users of all CRIF based services including Debtor Management, Address Check and Compliance services.
All maintenance work can be considered complete once this has been announced on the status page i.e. please assume the environment is undergoing maintenance until you receive confirmation of successful conclusion.
We appreciate your patience and understanding. As always, if you have questions or issues, please write to support-vwpayments@vwfs.com Posted on
Jan 04, 2024 - 10:15 CET
In an effort to continue providing the best possible service, CRIF will be conducting a planned maintenance affecting the components listed below.
- Sanctions Screening
All maintenance work can be considered completed once this has been announced on the status page i.e. please assume the environment is undergoing maintenance until you receive confirmation of successful conclusion.
We appreciate your patience and understanding. As always, if you have questions or issues, please write to support-vwpayments@vwfs.com Posted on
Jan 04, 2024 - 11:04 CET
In an effort to continue providing the best possible service, CRIF will be conducting a planned maintenance affecting the components listed below.
- Sanctions Screening
All maintenance work can be considered completed once this has been announced on the status page i.e. please assume the environment is undergoing maintenance until you receive confirmation of successful conclusion.
We appreciate your patience and understanding. As always, if you have questions or issues, please write to support-vwpayments@vwfs.com Posted on
Jan 04, 2024 - 11:04 CET
In an effort to continue providing the best possible service, CRIF will be conducting a planned maintenance affecting the components listed below.
This issue affects all users of all CRIF based services including Debtor Management, Address Check and Compliance services.
All maintenance work can be considered complete once this has been announced on the status page i.e. please assume the environment is undergoing maintenance until you receive confirmation of successful conclusion.
We appreciate your patience and understanding. As always, if you have questions or issues, please write to support-vwpayments@vwfs.com Posted on
Jan 04, 2024 - 10:16 CET
In an effort to continue providing the best possible service, CRIF will be conducting a planned maintenance affecting the components listed below.
- Sanctions Screening
All maintenance work can be considered completed once this has been announced on the status page i.e. please assume the environment is undergoing maintenance until you receive confirmation of successful conclusion.
We appreciate your patience and understanding. As always, if you have questions or issues, please write to support-vwpayments@vwfs.com Posted on
Jan 04, 2024 - 11:05 CET
In an effort to continue providing the best possible service, CRIF will be conducting a planned maintenance affecting the components listed below.
- Sanctions Screening
All maintenance work can be considered completed once this has been announced on the status page i.e. please assume the environment is undergoing maintenance until you receive confirmation of successful conclusion.
We appreciate your patience and understanding. As always, if you have questions or issues, please write to support-vwpayments@vwfs.com Posted on
Jan 04, 2024 - 11:06 CET
Completed -
The scheduled maintenance has been completed.
Apr 24, 16:30 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 24, 16:00 CEST
Scheduled -
A patch including required fixes will be deployed to the affected components below.
We expect a downtime for the duration of this intervention, with all requests responding with the HTTP Response code 503; we apologize for any inconvenience this may cause in the meantime.
Rollback possible: Yes
All maintenance work can be considered complete once this has been announced on the status page i.e. please assume the environment is undergoing maintenance until you receive confirmation of successful conclusion.
Unless otherwise stated, we do not expect any incompatibility to be introduced by this change, despite this, to ensure your customer base continues to enjoy the same experience prior to the introduction of this change in other environments, we recommend executing regression tests immediately following the successful conclusion of this deployment and raising a service request explicitly asking to halt further deployment in other environments should a concern be identified based on your existing integration.
We appreciate your patience and understanding. As always, if you have questions relating to or issues following the upgrade with your existing integration, please write to support@jpmmps.com
Apr 23, 17:27 CEST
Completed -
The scheduled maintenance has been completed.
Apr 23, 17:07 CEST
Verifying -
Verification is currently underway for the maintenance items.
Apr 23, 17:03 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 23, 16:15 CEST
Scheduled -
A patch including required fixes will be deployed to the affected components below.
We expect a downtime for the duration of this intervention, with all requests responding with the HTTP Response code 503; we apologize for any inconvenience this may cause in the meantime.
Rollback possible: Yes
All maintenance work can be considered complete once this has been announced on the status page i.e. please assume the environment is undergoing maintenance until you receive confirmation of successful conclusion.
Unless otherwise stated, we do not expect any incompatibility to be introduced by this change, despite this, to ensure your customer base continues to enjoy the same experience prior to the introduction of this change in other environments, we recommend executing regression tests immediately following the successful conclusion of this deployment and raising a service request explicitly asking to halt further deployment in other environments should a concern be identified based on your existing integration.
We appreciate your patience and understanding. As always, if you have questions relating to or issues following the upgrade with your existing integration, please write to your Payment Solutions Specialist.
Apr 23, 15:40 CEST
Completed -
The scheduled maintenance has been completed.
Apr 18, 18:31 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 18, 17:00 CEST
Update -
Please note, the following typing mistake has been corrected. This change applies to both SANDBOX and PRODUCTION announcements of upcoming maintenance and their changes. 0619 has been corrected to 0629.
SmartPay customers do not need to take any action.
New Validation and API Response Code
A validation with response code 0629 has been introduced to the API Call Complete Add Stored Payment Option. It prevents storing a Payment Option for a PaymentOptionCode different than the one provided in the related Init Add Stored Payment Option request.
We appreciate your patience and understanding. As always, if you have questions relating to or issues following the upgrade with your existing integration, please write to support@jpmmps.com
Apr 16, 11:47 CEST
Scheduled -
The latest version of the platform is here, affecting the components listed below.
As this is a major release, we expect a downtime for the duration of this intervention, with all requests responding with the HTTP Response code 503; we apologize for any inconvenience this may cause in the meantime.
What’s new & Improvements
This version includes performance improvements and bug fixes.
Merchant Panel
Chargeback Transactions Custom Fields
For Chargeback transactions, the fields Custom1, Custom2, and Custom3, provided with the original transaction will be displayed in the Merchant Panel
Failed Authorizations
When an Authorization has failed, for example, due to errors in 3D Secure User Authentication, it is now visible with the Transaction Status "Failed" in the Merchant Panel.
Web API
New Status "Failed" for Failed Authorizations
When a transaction fails during the authorization process, the transaction will be marked as status "Failed". Failed Authorizations are visible in the Merchant Panel.
New Validation and API Response Code
A validation with response code 0629 has been introduced to the API Call Complete Add Stored Payment Option. It prevents storing a Payment Option for a PaymentOptionCode different than the one provided in the related Init Add Stored Payment Option request.
Dot-less Domain Support for Dev Environments
URL Input Validation has been altered to allow dot-less domains for flexibility in development environments. This means, for example, URLs such as https://localhost/test are allowed for development purposes.
For the best compatibility with the widest range of external systems and payment providers, it's still strongly recommended for Merchants to use HTTPS Absolute URLs, including a top-level domain.
General Changes
Rate Limiting
Rate Limiting of all API Requests has been implemented to avoid instability due to unexpected peaks in demand, for example "Black Friday" Sales events. In case you are expecting high demand, please reach out to your Customer Relationship Manager.
SDK Change
Dot-less Domain Support for Dev Environments
URL Input Validation has been altered to allow dot-less domains for flexibility in development environments. This means, for example, URLs such as https://localhost/test are allowed for development purposes.
For the best compatibility with the widest range of external systems and payment providers, it's still strongly recommended for Merchants to use HTTPS Absolute URLs, including a top-level domain.
SDKs Latest Versions
Periodically updates are released to the web and mobile SDKs, which can include new functionality, bug fixes, and security updates.
We urge all stakeholders to update integrated SDK versions to the newest version as soon as these are available as the following link.
The latest SDK version is always available from our documentation website.
The latest version numbers are: Web – v9.0 iOS – v9.0 Android – v9.0
SmartPay customers do not need to take any action.
Rollback possible: Yes
All maintenance work can be considered complete once this has been announced on the status page i.e. please assume the environment is undergoing maintenance until you receive confirmation of successful conclusion.
Unless otherwise stated, we do not expect any incompatibility to be introduced by this change, despite this, to ensure your customer base continues to enjoy the same experience prior to the introduction of this change in other environments, we recommend executing regression tests immediately following the successful conclusion of this deployment and raising a service request explicitly asking to halt further deployment in other environments should a concern be identified based on your existing integration.
We appreciate your patience and understanding. As always, if you have questions relating to or issues following the upgrade with your existing integration, please write to support@jpmmps.com
Apr 9, 17:57 CEST
Completed -
The scheduled maintenance has been completed.
Apr 18, 16:47 CEST
Verifying -
Verification is currently underway for the maintenance items.
Apr 18, 16:46 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 18, 16:00 CEST
Scheduled -
A patch including required fixes will be deployed to the affected components below.
We expect a downtime for the duration of this intervention, with all requests responding with the HTTP Response code 503; we apologize for any inconvenience this may cause in the meantime.
Rollback possible: Yes
All maintenance work can be considered complete once this has been announced on the status page i.e. please assume the environment is undergoing maintenance until you receive confirmation of successful conclusion.
Unless otherwise stated, we do not expect any incompatibility to be introduced by this change, despite this, to ensure your customer base continues to enjoy the same experience prior to the introduction of this change in other environments, we recommend executing regression tests immediately following the successful conclusion of this deployment and raising a service request explicitly asking to halt further deployment in other environments should a concern be identified based on your existing integration.
We appreciate your patience and understanding. As always, if you have questions relating to or issues following the upgrade with your existing integration, please write to your Payment Solutions Specialist.
Apr 18, 09:25 CEST
Completed -
The scheduled maintenance has been completed.
Apr 16, 16:55 CEST
Verifying -
Verification is currently underway for the maintenance items.
Apr 16, 16:51 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 16, 16:00 CEST
Scheduled -
A patch including required fixes will be deployed to the affected components below.
We expect a downtime for the duration of this intervention, with all requests responding with the HTTP Response code 503; we apologize for any inconvenience this may cause in the meantime.
Rollback possible: Yes
All maintenance work can be considered complete once this has been announced on the status page i.e. please assume the environment is undergoing maintenance until you receive confirmation of successful conclusion.
Unless otherwise stated, we do not expect any incompatibility to be introduced by this change, despite this, to ensure your customer base continues to enjoy the same experience prior to the introduction of this change in other environments, we recommend executing regression tests immediately following the successful conclusion of this deployment and raising a service request explicitly asking to halt further deployment in other environments should a concern be identified based on your existing integration.
We appreciate your patience and understanding. As always, if you have questions relating to or issues following the upgrade with your existing integration, please write to your Payment Solutions Specialist.
Apr 16, 13:52 CEST
Resolved -
The incident has been resolved. The issue was on the acquirer side and the root cause was a change on one of their processors.
Apr 15, 13:03 CEST
Monitoring -
A fix has been implemented and we are monitoring the results.
Apr 15, 10:45 CEST
Update -
We identified that Credit Card Payments and also adding credit card payments is currently interrupted with the error:
no response from connector/acquirer [uncertain result] (900.100.300)
We are investigating with our providers.
Apr 15, 09:09 CEST
Investigating -
We're experiencing an elevated level of API errors and are currently looking into the issue and will provide further updates as soon as possible.