Activities of "Spospisil"
Hi,
One of the main reasons we purchased the commercial license was so we could easily integrate black box functions such as the Payment module with minimal coding to integrate into our solution.
Based on the responses here it leaves the impression that at this point the Payment Module is not something that fits that model as the module itself should contain all logic to not only persist the payment requests to the DB but also handle the all the UI to process a payment as the documentation outlines (https://docs.abp.io/en/commercial/latest/modules/payment).
Since I'm am following the code samples provided in the payment module documentation which appears to not be appropriate for a tiered/MVC solution and your suggested fix to my issue appears to implement persisting the payment request data myself vs having the Payment Module handle it (like it's advertised it should) as well as the subsequent ui involved in creating either a one time payment or recurring payment, I would like to get an idea of when the Payment Module will be a production ready module that can be integrated just like the other commercial modules we have purchased.
I will need a timeline so I can set expectations with my employer.
Thanks.
Hi,
My issue was I had previously generated migrations that had the prefix in there before I added the logic to remove the prefixes. I had not deleted the migrations and it was just reapplying them.
Thanks for the help.
AbpPermissionManagementDbProperties.DbTablePrefix = "NewPrefix"Can you try this code?
I already have and it doesn't work as expected.
Yes, it's an MVC Tiered solution, however your suggestion did not resolve the issue. Can you please explain how the payment application service can be called directly from the web projects code?
What I find a little odd is in you Volo.Payment.Application source you have 3 App Services defined for the Payment Module as shown below.
However in the Volo.Payment.HttpAPI source there is a Gateway and Plan controller that essentially call the application services as shown above but you don't have a 'PaymentRequestController' in the HttpAPI project as shown below.
Why is that?
Hi @Spospisil Payment operations are done by directly Web project for some security reasons. But in that case, you're right. It seems PaymentRequestController is missing. If we provide endpoints for that AppService, there will be a security problem. Because all complete or endpoints that perform update operations on PaymentReuqest will be accessible publicly. We'll
work on this in the next version.
Also your credit is refunded
I'm a little confused by your response given that the ABP documentation actually shows this PaymentRequestAppService being called directly from a MVC/Razor page thus implying that it's intent was to be a publicly accessible endpoint.
Why would a action being called for the PaymentRequest app service be a security risk when it's sole purpose is to update/insert into a local database presumably behind a firewall, etc?
hi
The 5.0 is using the static proxy. The structure of the project has also changed. It may not be compatible with the old version. You can consider to download the source code of 4.4.4 or upgrade to 5.0.
https://github.com/abpframework/abp/pull/9905
My main solution is all version ABP 4.4.4. I do not want to upgrade to 5.0 (at this point) to resolve this issue. Are you saying the ABP 4.4.4 Payment Module does not work for an MVC/Tiered application?
Hi,
I have sent you a email with a google drive link. Please let me know what you find.
Steve
Hi,
Can I get an update to this issue please.
Thanks.
Hi,
Well to test out if ABP 5.0.1 would solve my problem, I tried generating a MVC/Tiered solution using ABP suite and then adding the Payment Module (as a package) to the generated solution and then tried creating a recurring payment and get essentially the same issue with the injection of the IPaymentRequestAppService interface. See link below.
At this point the Payment Module does not work with a tiered solution either with ABP 4.4.4 and 5.0.1, so I'll need this resolved pretty quickly.
Please advise.
https://support.abp.io/QA/Questions/2373/Payment-ModuleRecurring-Payment-Not-Working
So your suggestion is to upgrade to v5.0 in order to fix this issue? Let me remind you that it's the IPaymentRequestAppService not the IPaymentRequestAdminAppService that seems to be the issue.
I'll also remind you that there is no 'controller' defined in the Volo.Payment.HttpApi project for the payment requests as there are for the Gateway and Plans as I mentioned above.
