Activities of "enisn"

Hi @joe@tronactive.com

Currently, the SaaS module depends on Core features of Payment module to serve subscription feature.

There is a way to remove those tables from your database and ignore them permanently. But I do not suggest it, because if you'll use subscription feature in future, you'll need to add them manually again.

1. Go to your DbContext builder
2. Add the following lines:

builder.Ignore<GatewayPlan>();
builder.Ignore<PaymentRequest>();
builder.Ignore<PaymentRequestProducts>();
builder.Ignore<Plan>();

3. Then you can create migrations and you'll see those tables won't be included in your migrations or it'll be removed if you have added them before.

Webhook operations such as your second & third operations will be solved in your situation.

The first : When you make a subscription everything goes well, the Payment/GatewaySelection page redirects to Payment/Stripe/PrePayment but this last page does not redirect to the stripe payment page. No errors in the logs. We can retrieve payment url from stripe logs and make payment however.

Payment redirection is made with javascript after the page is loaded. If you don't see any error on console, redirection should be done after a while

We've discovered an issue on our side. We'll release a patch version for it.

Also your credit is refunded.

Hi @willignicolas@gmail.com

Can you find the payload of webhook request from Stripe dashboard?

The error says there are has some invalid arguments. If you can share the payload, we can investigate which one is it.

Hi @christophe.baille

You can't use Volo.Payment.Web and Volo.Payment.Stripe.Web packages inside your Blazor WebAssembly. Web layers are only compatible with Blazor Server.

Thank you for your answer, I'll plan to publish an article about making payments in Blazor UI.

Blazor Server works hybrid. it includes MVC endpoints too. If you redirect to /GatewaySelection?paymentRequestId=THE_ID_OF_PAYMENTREQUEST after creating a PaymentRequest, an MVC page will handle and a page will be shown for payment provider selection.

Before doing that, make sure your project has reference to Volo.Payment.Web and Volo.Payment.Stripe.Web. If you include Web layers in a Blazor project, it will switch to razor pages when required.

Please use forceLoad while redirecting with NavigationManager:

NavigationManager.NavigateTo("/GatewaySelection?paymentRequestId=X", forceLoad: true);

You can see an already built example form identity module: https://github.com/abpframework/abp/blob/afc99acdb94aff74ed4745a6f3910f99c3f2119b/modules/identity/src/Volo.Abp.Identity.Blazor/Pages/Identity/UserManagement.razor#L22-L30

And columns were configured like this: https://github.com/abpframework/abp/blob/afc99acdb94aff74ed4745a6f3910f99c3f2119b/modules/identity/src/Volo.Abp.Identity.Blazor/Pages/Identity/RoleManagement.razor.cs#L78-L92

We'll work on those endpoints in the next milestone. It'll be compatible with distributed systems and tiered solutions.

You can review how we do in eShopOnAbp. All logic will work on HttpApi instead of Web layer

Can you check if Account Pro module is updated too or any dependency which depends on account module is updated?

For now, you can include AbpPaymentApplicationModule in your Web project as a workaround until we'll release an update for it