Has anyone successfully integrated the web payments sdk with Angular 12? I’ve tried separate npm’s and cannot find anything that successfully can initialize the card. I’m trying to find examples or what the correct npm packages I should use; however, there is not much out there on what works.
1 Like
Unfortunately, we don’t have an example in Angular 12 nor am I currently aware of anyone integrating with the Web Payments SDK. We’re constantly working to improve our features based on feedback like this, so I’ll be sure to share your request to the API product team. 
So the existing SqPaymentForm has been deprecated for some time now, and in fact will stop working in May but there is no confirmed case of someone integrating the new Web Payment SDK into their Angular application. How smart is that !
I too find it difficult to use with angular and may be forced to change the payment provider to avoid service interruption.
Currently we don’t have an example of either product in Angular. We’re constantly working to improve our features based on feedback like this, so I’ll be sure to share your request to the API product team.
Also what sort of issues are you having while trying to integrate it with Angular?
I have been using it in AngularJS and am struggling to integrate the Web Payments SDK.
Is there an actual reason the existing sqPaymentForm is being deprecated?
The Web Payments SDK was created to make integration with your web application simpler and provide better performance. The SDK provides the following advantages:
Granular configuration. You only need to write configuration code for the payment methods that your application accepts. Each payment method has its own objects with configuration options appropriate for the method.
Promise-based pattern. The async/await pattern is used in place of the callback pattern of earlier payment libraries. This pattern lets your application react to events in a more reasonable way with less code.
Automatic localization. The SDK determines the locale of the buyer’s browser automatically. However, your application can override localization by setting a configuration option.
Also the Web Payments SDK supports all the new payment methods.
When you have to paste about 100 lines of code it’s not really “with less code”. It’s literally more code than the previous version. It also has less customisation than the previous version.
It’s just a woeful attempt top copy what Stripe have done.
Also, buying Afterpay has destroyed your share price and now it’s destroying your product.