You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 14, 2020. It is now read-only.
This will be heavily based on osu!'s supporter system, and we will leverage PCI-compliant transaction handlers for this.
the supporter system is a voluntary, non-subcription pledge service that allows people to name their price on the platform. The only cap we have for supporter is 5 USD for minimum, which equates to one month.
Being said so, we have a flow that would allow Sayonika to understand the transactions went well:
On supporter page, have them pick a specific pledge amount, 5 being the minimum, custom being the last option.
If picked from predetermined values: Invoice them with the amount stated.
If custom, Invoice with their own valued cost.
Listen to the callback the provider returns in-API. Show a Error page if not successful, show a successful page if successful, of course
When successful, set supporter badge and time it based on the pledge amount. Reminder that 5US$ is equivalent to 1 month, as to be fair with our development efforts for this.
The text was updated successfully, but these errors were encountered:
Related: #16
This will be heavily based on osu!'s supporter system, and we will leverage PCI-compliant transaction handlers for this.
the supporter system is a voluntary, non-subcription pledge service that allows people to name their price on the platform. The only cap we have for supporter is 5 USD for minimum, which equates to one month.
Being said so, we have a flow that would allow Sayonika to understand the transactions went well:
The text was updated successfully, but these errors were encountered: