From f26844015a29ba065f4dbbc0d01bcefaac321d20 Mon Sep 17 00:00:00 2001 From: Ovi Trif Date: Wed, 21 Oct 2026 16:24:31 +0200 Subject: [PATCH 1/2] chore: usdt review journey and changelog match android --- changelog.d/next/1060.fixed.md | 2 +- journeys/paykit-quoted-usdt.xml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/changelog.d/next/1060.fixed.md b/changelog.d/next/1060.fixed.md index 20d4ac9e6..e43aae596 100644 --- a/changelog.d/next/1060.fixed.md +++ b/changelog.d/next/1060.fixed.md @@ -1 +1 @@ -The USDT payment details now fit the longest set of details, scrolling above a pinned Swipe To Pay. +On the expanded USDT payment review, the fee note no longer crowds Hide Details, and long details scroll above a pinned Swipe To Pay. diff --git a/journeys/paykit-quoted-usdt.xml b/journeys/paykit-quoted-usdt.xml index 31882089d..0b48eb02a 100644 --- a/journeys/paykit-quoted-usdt.xml +++ b/journeys/paykit-quoted-usdt.xml @@ -18,7 +18,7 @@ Repeat the subscription USDT and Savings switches four times without editing. Verify every return to Bitcoin shows exactly 12,345 sats and USDT is never selected with a Bitcoin rail. Edit the amount to 10 USD, repeat the switches and verify every return to USDT shows exactly 10 USD. Select Savings only and propose to the linked contact. On the payer, verify the proposal offers Savings but not Spending or USDT, then close before subscribing. Open a linked USDT-only contact that has published a private payment list. Verify the amount screen offers only USDT, enter 0.01, and verify the balance is labeled AVAILABLE rather than AVAILABLE (SPENDING). Compare with direct USDT Send: the amount, balance, USDT chip and Continue use the same typography; the balance stays close below the amount and the keypad uses the remaining space without clipping Continue. Close without continuing to review. Open a USD payment request for 150.50 that is payable in USDT. Verify its preset USDT input retains two decimal places, including 150,50 in a comma locale. Continue to payment review and verify those decimal places remain visible while the fee quote loads and after a quote failure. Close without paying. Edit an existing USD or USDT request for the same amount and verify the input retains those cents. A six-decimal USDT amount must remain exact, and the serialized request amount must not change merely because its input formatting changed. - Open an unpaid USDT payment request from a linked contact whose invoice note is long enough to wrap. Continue to payment review and tap Show Details. Verify Contact, Address and Invoice Note appear, scroll past them and verify Hide Details and then the fee note "All fees are paid in USDT. Final fee may be lower." follow with space between them, never overlapping. Verify Swipe To Pay stays pinned and fully visible above the navigation area while the details scroll. Close without paying. + Using the local USDT fixture for quotes, open an unpaid USDT payment request from a linked contact whose invoice note is long enough to wrap. Continue to payment review and tap Show Details. Verify Contact, Address and Invoice Note appear, scroll past them and verify Hide Details and then the fee note "All fees are paid in USDT. Final fee may be lower." follow with space between them, never overlapping. Verify Swipe To Pay stays pinned and fully visible above the navigation area while the details scroll. Close without paying. On a comma-decimal locale, open direct USDT Send, USDT Receive amount entry and a USDT contact payment. Verify each decimal key is a comma and entering 5,5 shows 5,5. Close each flow without paying or sharing a deposit request. From fbe1d64539be0a55b4dd700abff77a5ab29c9739 Mon Sep 17 00:00:00 2001 From: Ovi Trif Date: Wed, 21 Oct 2026 16:31:33 +0200 Subject: [PATCH 2/2] chore: usdt review journey and changelog match android Paykit USDT Amount journey step matches the Bitcoin amount layout. --- journeys/paykit-quoted-usdt.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/journeys/paykit-quoted-usdt.xml b/journeys/paykit-quoted-usdt.xml index 0b48eb02a..c27e2b767 100644 --- a/journeys/paykit-quoted-usdt.xml +++ b/journeys/paykit-quoted-usdt.xml @@ -16,7 +16,7 @@ Create a USD subscription for 150,50 on a comma-decimal locale. Verify the amount review shows 150,50 USD and editing preserves that amount. Verify Accepted Payments appears below frequency, with USDT selected and any available Savings and Spending chips unselected. Verify the description and icon controls are side by side. Propose it to the linked contact. On the payer, verify the subscription card and details show 150,50 USD, then review its recurrence and USDT-only payment method. Verify the subscription swipe uses USDT teal, then close before subscribing. Create a BTC subscription for 12,345 sats and verify available Savings and Spending chips start selected and USDT is unselected. Deselect each selected Bitcoin chip and verify Choose Recipient is disabled when none remain. Select Savings (id "SubscriptionAccept-savings"), then USDT (id "SubscriptionAccept-usdt"); verify the amount converts to USD and only USDT is selected. Select Savings again; verify the amount returns to exactly 12,345 sats and only Savings is selected. If Spending is available, select it (id "SubscriptionAccept-spending") and verify both Bitcoin rails can be selected together, with USDT still unselected. Repeat the subscription USDT and Savings switches four times without editing. Verify every return to Bitcoin shows exactly 12,345 sats and USDT is never selected with a Bitcoin rail. Edit the amount to 10 USD, repeat the switches and verify every return to USDT shows exactly 10 USD. Select Savings only and propose to the linked contact. On the payer, verify the proposal offers Savings but not Spending or USDT, then close before subscribing. - Open a linked USDT-only contact that has published a private payment list. Verify the amount screen offers only USDT, enter 0.01, and verify the balance is labeled AVAILABLE rather than AVAILABLE (SPENDING). Compare with direct USDT Send: the amount, balance, USDT chip and Continue use the same typography; the balance stays close below the amount and the keypad uses the remaining space without clipping Continue. Close without continuing to review. + Open a linked USDT-only contact that has published a private payment list. Verify the amount screen offers only USDT, enter 0.01, and verify the balance is labeled AVAILABLE rather than AVAILABLE (SPENDING). Compare with direct USDT Send: the amount, balance, USDT chip and Continue use the same typography; the balance, chips and keypad sit at the bottom above Continue, as on direct USDT Send. Close without continuing to review. Open a USD payment request for 150.50 that is payable in USDT. Verify its preset USDT input retains two decimal places, including 150,50 in a comma locale. Continue to payment review and verify those decimal places remain visible while the fee quote loads and after a quote failure. Close without paying. Edit an existing USD or USDT request for the same amount and verify the input retains those cents. A six-decimal USDT amount must remain exact, and the serialized request amount must not change merely because its input formatting changed. Using the local USDT fixture for quotes, open an unpaid USDT payment request from a linked contact whose invoice note is long enough to wrap. Continue to payment review and tap Show Details. Verify Contact, Address and Invoice Note appear, scroll past them and verify Hide Details and then the fee note "All fees are paid in USDT. Final fee may be lower." follow with space between them, never overlapping. Verify Swipe To Pay stays pinned and fully visible above the navigation area while the details scroll. Close without paying. On a comma-decimal locale, open direct USDT Send, USDT Receive amount entry and a USDT contact payment. Verify each decimal key is a comma and entering 5,5 shows 5,5. Close each flow without paying or sharing a deposit request.