Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Valora] Investigate Methods for identifying for Merchant Payments and Mirror Refunds in Valora Feed #8842

Closed
aslawson opened this issue Oct 25, 2021 · 1 comment
Labels
Applications Applications circle tasks mobile payments Celo Payments Protocol Priority: P2 Major stale

Comments

@aslawson
Copy link
Contributor

aslawson commented Oct 25, 2021

Need to figure out how to identify merchant payments and refunds so we can indicate them in the transaction feed. Mirror transactions are auto-refunds from the FirstDAG address.

  • Amount will vary because gasfees deducted from refund, so cannot use exact fund amount for matching

1 Idea:
Valora currently has TokenTransactionType to indicate various transaction types. Can we leverage this to store and indicate merchant transaction in the feed?

  • Longer term offchain storage or other mechanism to for First to send transaction with referenceID
@aslawson aslawson added Applications Applications circle tasks mobile payments Celo Payments Protocol labels Oct 25, 2021
@aslawson aslawson added the Priority: P2 Major label Nov 29, 2021
@aslawson aslawson changed the title [Valora] Investigate TokenTransactionType for Merchant Payments and Mirror Refunds [Valora] Investigate Methods for identifying for Merchant Payments and Mirror Refunds in Valora Feed Nov 29, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Feb 4, 2023

This issue is stale and will be closed in 30 days without activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Applications Applications circle tasks mobile payments Celo Payments Protocol Priority: P2 Major stale
Projects
None yet
Development

No branches or pull requests

1 participant