Users and platforms will support a variety of backend payment platforms to facilitate the transfer of value from one account to another. This proposal is for an API that abstracts platform, ledger and account mappings to insulate end users and applications from these details. Senders, Receivers and the Platform that originates the transaction should all be able to set policies that must be satisfied for the transaction complete.
Example: Alice sends Bob $5.00
Alice has a policy enabling PayPal and Bitcoin as a payment providers and a limit of $50
Bob has a policy enabling PayPal and Stripe as a payment provider and only receives USD
Platform has a policy that only allows transactions under $100 and through PayPal, Stripe and their own internal payment engine
Transaction gets submitted through PayPal, Bob receives $5 USD.
Explain the suggestion with enough detail that someone familiar with the process and environment of the project can understand the suggestion and explain it to others.
It should include at least one end-to-end example of how the community will use it along with the specific details with outlying use cases.
If there is any new terminology, it should be defined here.
What are the advantages of the suggestion?
Explain the advantages of using this suggestion
What are the disadvantages of the suggestion?
Explain any disadvantages or trade-offs to using this suggestion
How will this be work within the O3DE project?
Explain how this suggestion will be work within the foundation or its groups.
Are there any alternatives to this suggestion?
Provide any other alternative ways that have been considered.
Explain what the impact might be of not implementing this suggestion.
If there are other similar suggestions previously used, list them and explain which parts may have solved some or all of this problem.
What is the strategy for adoption?
Explain how new and existing users will adopt this suggestion.
Point out any efforts needed if it requires coordination with multiple SIGs or other projects.
Explain how it would be taught to new and existing users.
Summary:
Payment API that facilitates a payment from one party to another party that abstracts the underlying payment infrastructure.
What is the motivation for this suggestion?
Why is this important?
This is solved in the industry and we need to Identify Microtransaction Systems that have solved this issue
What are the use cases for this suggestion? What should the outcome be if this suggestion is implemented?
Suggestion design description:
https://lists.openmv.org/g/fig-transactions/viewrow?id=37930&rowid=3238259&lv=1&p=RowNum%2C%2C%2C50%2C1%2C0%2C3238259
Users and platforms will support a variety of backend payment platforms to facilitate the transfer of value from one account to another. This proposal is for an API that abstracts platform, ledger and account mappings to insulate end users and applications from these details. Senders, Receivers and the Platform that originates the transaction should all be able to set policies that must be satisfied for the transaction complete.
Example: Alice sends Bob $5.00
Alice has a policy enabling PayPal and Bitcoin as a payment providers and a limit of $50 Bob has a policy enabling PayPal and Stripe as a payment provider and only receives USD Platform has a policy that only allows transactions under $100 and through PayPal, Stripe and their own internal payment engine
Transaction gets submitted through PayPal, Bob receives $5 USD.
Explain the suggestion with enough detail that someone familiar with the process and environment of the project can understand the suggestion and explain it to others.
It should include at least one end-to-end example of how the community will use it along with the specific details with outlying use cases.
If there is any new terminology, it should be defined here.
What are the advantages of the suggestion?
What are the disadvantages of the suggestion?
How will this be work within the O3DE project?
Are there any alternatives to this suggestion?
What is the strategy for adoption?