manojr13

Payments aren't harder than database drivers. The industry just never standardized it. While we were inspired by previous initiatives on similar lines: active-merchant (Ruby), omnipay (PHP) - we also ensured that Prism is

(I) Polyglot ready: The protobuf spec is made as the interface, allowing for extensions across many programming languages . (II) Flexible to use: Dual deployment mode (embedded and gRPC from the same core). Also PCI compliance can be managed by the user, or outsourced to a PCI compliant third party. (II) Hardened with real traffic: We extracted the integrations from a production-grade payment orchestrator at scale, and did not design from scratch. And we will continue to use it in production with regular updates, similar to how we have been consistently delivering for the last 4 years on Juspay hyperswitch - open source payment platform.

Ask me anything..

Payments aren't harder than database drivers. The industry just never standardized it.

While we were inspired by previous initiatives on similar lines: active-merchant (Ruby), omnipay (PHP) - we also ensured that Prism is

(I) Polyglot ready: The protobuf spec is made as the interface, allowing for extensions across many programming languages . (II) Flexible to use: Dual deployment mode (embedded and gRPC from the same core). Also PCI compliance can be managed by the user, or outsourced to a PCI compliant third party. (II) Hardened with real traffic: We extracted the integrations from a production-grade payment orchestrator at scale, and did not design from scratch. And we will continue to use it in production with regular updates, similar to how we have been consistently delivering for the last 4 years on Juspay hyperswitch - open source payment platform.

Ask me anything..

Payments aren't harder than database drivers. The industry just never standardized it.

While we were inspired by previous initiatives on similar lines: active-merchant (Ruby), omnipay (PHP) - we also ensured that Prism is

(I) Polyglot ready: The protobuf spec is made as the interface, allowing for extensions across many programming languages . (II) Flexible to use: Dual deployment mode (embedded and gRPC from the same core). Also PCI compliance can be managed by the user, or outsourced to a PCI compliant third party. (II) Hardened with real traffic: We extracted the integrations from a production-grade payment orchestrator at scale, and did not design from scratch. And we will continue to use it in production with regular updates, similar to how we have been consistently delivering for the last 4 years on Juspay hyperswitch - open source payment platform.

Ask me anything..

Payments aren't harder than database drivers. The industry just never standardized it.

While we were inspired by previous initiatives on similar lines: active-merchant (Ruby), omnipay (PHP) - we also ensured that Prism is

(I) Polyglot ready: The protobuf spec is made as the interface, allowing for extensions across many programming languages . (II) Flexible to use: Dual deployment mode (embedded and gRPC from the same core). Also PCI compliance can be managed by the user, or outsourced to a PCI compliant third party. (II) Hardened with real traffic: We extracted the integrations from a production-grade payment orchestrator at scale, and did not design from scratch. And we will continue to use it in production with regular updates, similar to how we have been consistently delivering for the last 4 years on Juspay hyperswitch - open source payment platform.

Ask me anything..

Payments aren't harder than database drivers. The industry just never standardized it.

While we were inspired by previous initiatives on similar lines: active-merchant (Ruby), omnipay (PHP) - we also ensured that Prism is

(I) Polyglot ready: The protobuf spec is made as the interface, allowing for extensions across many programming languages . (II) Flexible to use: Dual deployment mode (embedded and gRPC from the same core). Also PCI compliance can be managed by the user, or outsourced to a PCI compliant third party. (II) Hardened with real traffic: We extracted the integrations from a production-grade payment orchestrator at scale, and did not design from scratch. And we will continue to use it in production with regular updates, similar to how we have been consistently delivering for the last 4 years on Juspay hyperswitch - open source payment platform.

Ask me anything..

More contributors to the opensource project

Interesting solution to a pertinent problem. If I want to use this solution in the subscription workflow, is it mandatory that one uses the same APIs for the customer login use case also?

Thats the goal of the post. No solution will cover every problem for scaled up businesses; hence no-code is always a myth and code needs to be written.

The larger goal of the payment solution is not be be fully complete and call itself as the one-and-only no code. It is to create open source and reusable code to avoid the repetitive work for developers..

It is open for public repos, so practically free

Makes sense. What's the point in pay bumps, when there is a high chance of layoff expected!

Just hang in there! It won't be very far away

Got it

Chocolates, Coffee are equally harmful frequently self-administered addiction drugs. So why compare with them?

"Transactional models are flexible pricing where customers only pay for what they have used during the period. In the UB subscription model, customers commit to their desired level of usage."

How does that make usage based pricing better than transactional? Is it because the commitment in UB pricing will reduce the unit price comparatively?

What?? Why was this even built? To scam users by collecting credit cards?

Let's the servers cool down for sometime. Might have been working very hard.

Yes. The devil is in the details. Small businesses should better opt for a merchant on record who can manage all such complexity.

Thanks for the feedback

Great resources. Thanks.

Thanks. Too many details make the developers run away from the 101 class ;-)

But will definitely cover tm in 102

Fednow has the potential to create a similar UPI like impact on US

That would be a payments switch like https://hyperswitch.io/

Agree. But covered cards because it is the most complex form of payment with a lot of intermediaries. So understanding the longest path, will help to prepare as developer for payments industry

It is indeed explained through eight steps in the second half of the article

Absolutely. Just trying to tame such devils using open source and community as the tools

What would that be?

A result of gen Z syndrome https://nypost.com/2023/04/21/gen-z-is-the-most-difficult-ge...

Visited egypt recently. This project originates from upper egypt's Lake Nasser (near Abu Simbel) which is a very large water body.

This is not only about the cooling part. It also talks calculated the water spent in generating the energy behind it

Any level of income growth at the expense of income disparity and safety is not worth it. US will slowly become a net emigration center during this decade. The symptoms are already mushrooming.