<aside> ⚠️ This is an early documentation specification of the Open Payment SDK and meant to be used as reference. This feature is not yet published within Spare and final documentation is likely to change on release.
</aside>
Currently Spare only supports Stripe as a native payment processor. The Open Payment SDK is designed to solve this problem by allowing 3rd party developers to integrate their own payments apps into Spare experiences.
In order to achieve the goal of open payments with any payment app, the system works by redirecting the rider into a web-based payment experience. Through this web-based payment experience, the rider inputs their payment details and the 3rd party payment app processes the payment. Once the payment is processed, the web-based experience will redirect the web view back into Spare systems. Once redirected back to Spare systems, the rider experience will complete the their purchase.
Here is an example mock up of how the flow could look like. We can see that in this case the 3rd party developers registered a new payment app with Spare called MyFavoriteGateway.
Spare will interact with the third party payment app in the following way whenever there is a reason for payment. Currently Spare provides the following experiences that require the payment flows: