Skip to content

Add gift card transfer flow#906

Open
gudnuf wants to merge 1 commit intoadd-buy-transfer-typesfrom
gift-card-add-funds
Open

Add gift card transfer flow#906
gudnuf wants to merge 1 commit intoadd-buy-transfer-typesfrom
gift-card-add-funds

Conversation

@gudnuf
Copy link
Contributor

@gudnuf gudnuf commented Mar 3, 2026

Adds the ability to top up gift cards by transferring funds between accounts via Lightning. Builds on input-refactoring.

@vercel
Copy link

vercel bot commented Mar 3, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
agicash Ready Ready Preview, Comment Mar 5, 2026 9:38pm

Request Review

@supabase
Copy link

supabase bot commented Mar 3, 2026

This pull request has been ignored for the connected project hrebgkfhjpkbxpztqqke because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

Copy link
Collaborator

@jbojcic1 jbojcic1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a way to tell that some transfer was actually done via transfer ui as opposed to getting an ln invoice from receive flow and paying it via send flow?

);

// TODO: Talk to Josip — this manually transitions DRAFT→PENDING after creation.
// Ideally the receive quote would be created as PENDING from the start (like CASHU_TOKEN),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah we definitely should me manually transitioning it

@jbojcic1
Copy link
Collaborator

jbojcic1 commented Mar 3, 2026

we have more and more stuff that we place under features that depends on other features. this means we kind of failed atm with vertically slicing the portions of the app and still ended up with everything depending on everything. it's more like a folder structure only atm and that was not my initial intention

nothing to act on this here but I will need to think about this a bit more and see if I can come up with some plan to break things up

@gudnuf
Copy link
Contributor Author

gudnuf commented Mar 3, 2026

is there a way to tell that some transfer was actually done via transfer ui as opposed to getting an ln invoice from receive flow and paying it via send flow?

Not sure what you mean. We know the transfer is completed when the receive quote is paid

@gudnuf gudnuf force-pushed the gift-card-add-funds branch from 981d83c to 84ce5b0 Compare March 5, 2026 07:31
@gudnuf gudnuf changed the title Add funds to gift cards via cross-account transfer Add gift card transfer flow Mar 5, 2026
@gudnuf gudnuf changed the base branch from input-refactoring to add-buy-transfer-types March 5, 2026 07:31
<LinkWithViewTransition
to={buildLinkWithSearchParams('/receive', {
accountId: card.id,
redirectTo: `/gift-cards/${card.id}`,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@claude this redirectTo should not have been removed. We still want to reidrect back when the transfer is completed

Copy link

@claude claude bot Mar 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude finished @gudnuf's task in 54s —— View job


Restored redirectTo on gift card transfer link

  • Read the current file and diff to understand the removed code
  • Restore the redirectTo parameter
  • Push the fix

The "Add" button's link was missing the redirectTo search param. Restored it using buildLinkWithSearchParams (same pattern as the "Send" button), so navigating back after transfer completion works correctly.

Commit: 46c27c4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants