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