I hope you’re doing well. I wanted to check if there are any updates on adding Apple Pay, Google Pay, MobilePay, and other wallet-based payment options to the Stripe integration in Amelia.
Since Stripe natively supports these payment methods, it’s expected behavior that they would be available when using Stripe within Amelia. However, at the moment, it seems these options are missing.
Could you provide insight into:
Are there plans to enable Apple Pay, Google Pay, and MobilePay soon?
If not, is there a reason why these are not yet supported despite being part of Stripe’s standard offerings?
These payment options are widely used and expected by customers, so enabling them would greatly improve the checkout experience. I hope this feature will be implemented soon.
Unfortunately, there is no such option currently in Amelia. When using Stripe as a payment method, only credit card payments are supported. Of course, we are planning to add other payment options in future updates, but unfortunately, we can't provide an ETA at this moment. We are aware that these options are often used by customers and that it would improve the checkout experience. However, adding them requires integration and development, which can be a complex process. We will make sure to inform everyone by updating our changelog page, so please keep an eye on it.
Thank you for your response. I understand that adding additional payment options to the Stripe integration is not currently supported and that there is no ETA for this feature.
Since I hold an Elite license, which I understood to include access to the source code, could you provide the JavaScript code related to the checkout and payment methods? I would like to implement the changes myself to enhance the checkout experience for our customers.
I believe this approach would be a win-win solution, allowing us to meet our needs without waiting for a future update. Please let me know if this is possible and if you need any further information from my side.
Unfortunately, there is no such option available. We don't currently offer customization options, but the source code is included (I can send it to you if needed).
As mentioned previously, we recommend submitting this as a feature suggestion on our feature suggestion page.
The package.json file should already be included in the source files, but I just received information that Apple Pay will be supported in the next update. We don’t have an exact ETA at the moment, but we’re working to release it as soon as possible. It might be best to wait for the official release.
Stefan is out of the office so I will step in for him.
Please do not write more than once on the ticket because it sends it to the end of the queue.
We work on the tickets in order as they arrive, and each of your new replies sends a ticket to the end of the queue. Please open a separate ticket for each question or issue and wait for us to respond and we will try to help as best as we can to resolve the issue effectively and as soon as possible.
When you have several questions or issues which are not related to the title of the active ticket, please open a new ticket, and we will help you there. In that way, issues and questions that are related to different subjects will be in separate tickets so other customers or our support agents can find them easily.
-
Our policy is to have one issue or question per ticket because of the reasons that are described already.
-
Thank you for understanding.
For MobilePay or other Nordic-focused payment solution unfortunately, currently we do not have such plans for immediate future to be honest. Implementation if the features often depends on market requirement. In light of this, we encourage you to kindly consider submitting this valuable suggestion as a feature request through the following link: https://features.wpamelia.com/. The prioritization of feature development is greatly influenced by the number of customer requests received. By participating and expressing your support, you contribute significantly to the potential expedited implementation of this feature.
As for composer at this time, we cannot share details about future development plans due to company policy. However, we continuously work on improving our system, including dependency management and security updates, to ensure optimal performance and long-term stability.
That said, we truly appreciate your feedback, and we will make sure to forward your suggestions to our development team for consideration.
Should you have any further inquiries, we kindly request that you open separate tickets for each question and we will gladly help you there.
We wish you all the best and hope you have a wonderful day ahead.
I appreciate your response, but I would prefer to discuss these matters with Stefan or someone who can provide a more constructive and technically informed reply.
I understand your ticketing policy, but I want to clarify that I did not intend to bypass the queue—just to ensure clarity in communication. If the system automatically pushes tickets back in the queue for each reply, I would strongly recommend reconsidering this approach, as it discourages meaningful discussion and follow-ups.
1. Composer & Dependency Management
I understand that you cannot disclose full development plans due to company policy. However, I have received the source code, and from what I see, many dependencies are outdated, and updates are difficult because code has been patched directly inside the vendor/ directory instead of being properly managed via composer.json.
I am not just asking whether a proper composer.json is under consideration—I am asking why there are outdated dependencies and a lack of structured security updates.
Are you actively maintaining security updates for dependencies?
If so, how is this done without a structured composer.json?
Can you confirm if there are plans to move away from patching inside vendor/ and instead manage updates properly?
Security is not just a feature—it is a responsibility. Given Amelia’s 70,000 customers, it is reasonable to expect structured dependency management and regular security updates.
2. Stripe’s Full Payment Provider Support
I want to clarify that I am not asking for a custom integration of MobilePay or other Nordic solutions. I am only asking for Amelia to properly implement Stripe’s own native payment providers.
Currently, Amelia has built its own custom Stripe integration that only supports credit card payments, while Stripe itself already natively supports MobilePay, Swish, Vipps, and other regional payment solutions.
Since Amelia already integrates with Stripe, can you explain why the decision was made to limit Stripe to only credit card payments?
Is there a technical reason preventing the use of Stripe’s native payment providers?
Are there plans to align the Stripe implementation with Stripe’s full feature set?
I appreciate your time and look forward to your response.
Thank you for your patience and for taking the time to provide such detailed feedback. We truly appreciate your insights and understand your concerns.
Regarding the dependency management and Composer-related questions, I will forward your feedback to the relevant team. If they determine that we can share and need to share this, we will follow up accordingly. However, please note that while we continuously work on improving our system, our development team does not always provide direct responses to such inquiries. Once we receive feedback from them that this is ok to cover this will be forwarded to our Dev team.
As for Stripe, Amelia’s built-in integration currently supports only credit card payments due to technical reasons. If you need access to Stripe’s full range of payment providers, such as MobilePay, Swish, or Vipps, the best approach would be to use Amelia in combination with WooCommerce, which offers broader Stripe support.
We always value constructive discussions and suggestions, and we appreciate your effort to share your perspective. If there’s anything else we can clarify, feel free to let us know.
Best regards. We wish you all the best and hope you have a wonderful weekend ahead.
We just got the feedback from our colleagues and they have told us that we do plan to update certain dependencies where possible, but some updates are limited due to the minimum required PHP version, which we believe is currently 7.4.
That being said, we are continuously working on improving and maintaining the stability and security of the system, ensuring that updates are implemented where feasible.
Best regards and should you have any further inquiries, we kindly request that you open separate tickets for each question and we will gladly help you there.
We wish you all the best and hope you have a wonderful day ahead.
Dear Amelia Support Team,
I hope you’re doing well. I wanted to check if there are any updates on adding Apple Pay, Google Pay, MobilePay, and other wallet-based payment options to the Stripe integration in Amelia.
Since Stripe natively supports these payment methods, it’s expected behavior that they would be available when using Stripe within Amelia. However, at the moment, it seems these options are missing.
Could you provide insight into:
These payment options are widely used and expected by customers, so enabling them would greatly improve the checkout experience. I hope this feature will be implemented soon.
Looking forward to your response.
Best regards,
Martin
Hi Martin,
Unfortunately, there is no such option currently in Amelia. When using Stripe as a payment method, only credit card payments are supported. Of course, we are planning to add other payment options in future updates, but unfortunately, we can't provide an ETA at this moment. We are aware that these options are often used by customers and that it would improve the checkout experience. However, adding them requires integration and development, which can be a complex process. We will make sure to inform everyone by updating our changelog page, so please keep an eye on it.
Link to Changelog
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Stefan,
Thank you for your response. I understand that adding additional payment options to the Stripe integration is not currently supported and that there is no ETA for this feature.
Since I hold an Elite license, which I understood to include access to the source code, could you provide the JavaScript code related to the checkout and payment methods? I would like to implement the changes myself to enhance the checkout experience for our customers.
I believe this approach would be a win-win solution, allowing us to meet our needs without waiting for a future update. Please let me know if this is possible and if you need any further information from my side.
Looking forward to your response.
Best regards,
Martin
Hi Martin,
Unfortunately, there is no such option available. We don't currently offer customization options, but the source code is included (I can send it to you if needed).
As mentioned previously, we recommend submitting this as a feature suggestion on our feature suggestion page.
Apologies for the inconvenience.
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Stefan,
Yes, thanks! I would like to receive the source code where the JavaScript is not obfuscated. Please send it to me at your earliest convenience.
Thanks,
Martin
Hi Martin,
You are welcome.
If you have any other questions, please open a new ticket and we will gladly help you there.
Have a nice day.
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Martin,
The package.json file should already be included in the source files, but I just received information that Apple Pay will be supported in the next update. We don’t have an exact ETA at the moment, but we’re working to release it as soon as possible. It might be best to wait for the official release.
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Stefan,
Thank you for the update regarding Apple Pay. That’s good to hear.
However, since we rely on Nordic payment methods, I’d like to clarify:
Looking forward to your insights.
Best regards,
Martin
Hello there.
Stefan is out of the office so I will step in for him.
Please do not write more than once on the ticket because it sends it to the end of the queue.
We work on the tickets in order as they arrive, and each of your new replies sends a ticket to the end of the queue. Please open a separate ticket for each question or issue and wait for us to respond and we will try to help as best as we can to resolve the issue effectively and as soon as possible.
When you have several questions or issues which are not related to the title of the active ticket, please open a new ticket, and we will help you there. In that way, issues and questions that are related to different subjects will be in separate tickets so other customers or our support agents can find them easily.
-
Our policy is to have one issue or question per ticket because of the reasons that are described already.
-
Thank you for understanding.
For MobilePay or other Nordic-focused payment solution unfortunately, currently we do not have such plans for immediate future to be honest. Implementation if the features often depends on market requirement. In light of this, we encourage you to kindly consider submitting this valuable suggestion as a feature request through the following link: https://features.wpamelia.com/. The prioritization of feature development is greatly influenced by the number of customer requests received. By participating and expressing your support, you contribute significantly to the potential expedited implementation of this feature.
As for composer at this time, we cannot share details about future development plans due to company policy. However, we continuously work on improving our system, including dependency management and security updates, to ensure optimal performance and long-term stability.
That said, we truly appreciate your feedback, and we will make sure to forward your suggestions to our development team for consideration.
Should you have any further inquiries, we kindly request that you open separate tickets for each question and we will gladly help you there.
We wish you all the best and hope you have a wonderful day ahead.
Kind Regards,
Marko Davidovic [email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, floor plans, choropleth maps, and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Outdated Dependencies, Composer Management & Stripe Payment Providers
Hi Marko,
I appreciate your response, but I would prefer to discuss these matters with Stefan or someone who can provide a more constructive and technically informed reply.
I understand your ticketing policy, but I want to clarify that I did not intend to bypass the queue—just to ensure clarity in communication. If the system automatically pushes tickets back in the queue for each reply, I would strongly recommend reconsidering this approach, as it discourages meaningful discussion and follow-ups.
1. Composer & Dependency ManagementI understand that you cannot disclose full development plans due to company policy. However, I have received the source code, and from what I see, many dependencies are outdated, and updates are difficult because code has been patched directly inside the vendor/ directory instead of being properly managed via composer.json.
I am not just asking whether a proper composer.json is under consideration—I am asking why there are outdated dependencies and a lack of structured security updates.
Security is not just a feature—it is a responsibility. Given Amelia’s 70,000 customers, it is reasonable to expect structured dependency management and regular security updates.
2. Stripe’s Full Payment Provider SupportI want to clarify that I am not asking for a custom integration of MobilePay or other Nordic solutions. I am only asking for Amelia to properly implement Stripe’s own native payment providers.
Currently, Amelia has built its own custom Stripe integration that only supports credit card payments, while Stripe itself already natively supports MobilePay, Swish, Vipps, and other regional payment solutions.
Since Amelia already integrates with Stripe, can you explain why the decision was made to limit Stripe to only credit card payments?
I appreciate your time and look forward to your response.
Best regards,
Martin
Hello Martin,
Thank you for your patience and for taking the time to provide such detailed feedback. We truly appreciate your insights and understand your concerns.
Regarding the dependency management and Composer-related questions, I will forward your feedback to the relevant team. If they determine that we can share and need to share this, we will follow up accordingly. However, please note that while we continuously work on improving our system, our development team does not always provide direct responses to such inquiries. Once we receive feedback from them that this is ok to cover this will be forwarded to our Dev team.
As for Stripe, Amelia’s built-in integration currently supports only credit card payments due to technical reasons. If you need access to Stripe’s full range of payment providers, such as MobilePay, Swish, or Vipps, the best approach would be to use Amelia in combination with WooCommerce, which offers broader Stripe support.
We always value constructive discussions and suggestions, and we appreciate your effort to share your perspective. If there’s anything else we can clarify, feel free to let us know.
Best regards. We wish you all the best and hope you have a wonderful weekend ahead.
Kind Regards,
Marko Davidovic [email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, floor plans, choropleth maps, and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hello Martin,
We just got the feedback from our colleagues and they have told us that we do plan to update certain dependencies where possible, but some updates are limited due to the minimum required PHP version, which we believe is currently 7.4.
That being said, we are continuously working on improving and maintaining the stability and security of the system, ensuring that updates are implemented where feasible.
Best regards and should you have any further inquiries, we kindly request that you open separate tickets for each question and we will gladly help you there.
We wish you all the best and hope you have a wonderful day ahead.
Kind Regards,
Marko Davidovic [email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, floor plans, choropleth maps, and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables