<aside> 🚧 Please note this is an early release and there may be some variance in names and terminology between these guides and the API reference. Please don’t hesitate to reach out to the RubyPay technical team for assistance or clarification. Thank you for your patience and understanding.

</aside>

V1

RubyPay will be releasing it’s V1 as an early release beta. Because of the number and size of changes in the following release, we have opted for this to be as a separately hosted version, simply as api.vivamo.io.

V1 will continue to be fully supported and will not be deprecated until we are confident all clients have migrated away. Additionally, V1 will continue to have full test coverage and maintenance applied during the transition period.

V2

As mentioned, V2 will be released as api.vivamo.io (Vivamo SDK)

More details will follow about what the exact differences between V1 and V2 are, however some of the high level changes will include:

Listing and selecting payment types will be handed by the SDK according to what is available to the client.
Listing and storing payment methods will be fully handled by the SDK - client-side code will be required.
A more simplified UI/UX flow - where the amount of API calls will be significantly reduced and more of the UI will be embedded through the SDK.
Refactoring of naming and terminologies
…and more (TBC)