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.
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.
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.
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.
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.
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..
"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?
(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..