Feature Suggestion – Batch Payment Validation for Blink

[blinkbitcoinbot]

Migrated from GaloyMoney/blink#4804
Originally created by @Divoar on 4/17/2025, 7:16:45 AM

Hello Blink Team,

It would be a huge improvement to have a validation feature within the batch payment option, where the system can identify and return errors for invalid usernames upon uploading the .csv file. This would make it easier to detect and fix incorrect addresses before proceeding with the payment.

I’m currently trying to disburse sats to over 130 Blink addresses for The Core Cohort 6 graduates, and it’s quite difficult to identify the one or two incorrect entries that block the entire batch. Additionally, some students delay in confirming their usernames, which slows down the whole process.

Having this feature would make disbursements much smoother and faster, especially for educators or project leads managing bulk payments.

Thanks so much for all the great work you're doing at Blink — it’s really powering grassroots Bitcoin adoption.

Best
Felix

[pretyflaco]

Additional issues reported with batch payments:

• usernames that contain "_" underscore cause an error despite being valid usernames
• uploading CSV with more than 100 usernames gives error
• uploading a sheet with erroneous username gives too generic error without specifying culprit which makes it very hard to find the misspelled / invalid usernames

[k9ert]

Just had a discussion with claude about it. Here is the result:

Deep Dive: Batch Payment Validation

Relevant Files

File	Purpose
`apps/dashboard/components/batch-payments/index.tsx`	Main component, orchestrates file upload and payment processing
`apps/dashboard/app/batch-payments/utils.ts`	Primary suspect - `validateCSV()` and `processRecords()` functions
`apps/dashboard/app/batch-payments/index.types.ts`	Type definitions (CSVRecord, ProcessedRecords)
`apps/dashboard/app/batch-payments/get-user-details-action.ts`	Server action - looks up walletId by username
`services/graphql/queries/get-user-wallet-id.ts`	GraphQL query `accountDefaultWallet(username)`

Current Flow (utils.ts)

1. `validateCSV()` (L24-140): Parses CSV, validates headers/fields, aggregates totals

   • Returns generic errors: 'Invalid CSV Format', 'Missing required headers', 'Record with missing required field found'
   • Does NOT validate usernames at this stage

2. `processRecords()` (L142-177): Validates usernames one-by-one via GraphQL

   • HERE IS THE BUG: On first invalid username, returns error and stops
   • Error: `No wallet found for the user ${record.username}`
   • Does NOT continue to check remaining usernames

Root Cause Hypothesis

The feature request maps to this code path:
```
processRecords() → getUserDetailsAction() → getWalletDetailsByUsername()
```

When a username is invalid, the function returns immediately (L156-157):
```typescript
if (getDefaultWalletID.error) {
return new Error(getDefaultWalletID.message)
}
```

This stops processing at the first bad username instead of collecting all errors.

Issues From @pretyflaco's Comment

1. Underscore usernames fail - Likely GraphQL/backend Username regex validation issue
2. >100 usernames error - No explicit limit in frontend code; may be backend rate limiting
3. Generic errors - Confirmed in code: errors don't identify which username failed

Related Issues

• Batch Payments with google spreadsheet link #59: Batch Payments with Google spreadsheet link
• Recurring / scheduled (batch) payments #61: Recurring/scheduled (batch) payments
• Batch Payments to Lightning Address #62: Batch Payments to Lightning Address

Implementation Approach (for future dev)

To fix, `processRecords()` should:

1. Collect all username validation errors in an array
2. Continue processing all records
3. Return detailed error with list of invalid usernames
4. UI should display which specific usernames failed validation"

[grimen]

@pretyflaco You can also use "Assign to Copilot" and work that way through GitHub integrated tools as a workflow.

[grimen]

Additional issues reported with batch payments:

• usernames that contain "_" underscore cause an error despite being valid usernames
• uploading CSV with more than 100 usernames gives error
• uploading a sheet with erroneous username gives too generic error without specifying culprit which makes it very hard to find the misspelled / invalid usernames

Regarding these issues they seem to not be directly tied to this feature request, so it would make sense to break this out to BUG ticket(s) to not mash it all under one for atomicity.

[Divoar]

Yeah Had to manually check.

…

On Wed, 17 Dec 2025, 14:05 Jonas Grimfelt, ***@***.***> wrote: *grimen* left a comment (blinkbitcoin/blink#69) <#69 (comment)> Additional issues reported with batch payments: - usernames that contain "_" underscore cause an error despite being valid usernames - uploading CSV with more than 100 usernames gives error - uploading a sheet with erroneous username gives too generic error without specifying culprit which makes it very hard to find the misspelled / invalid usernames Regarding these issues they seem to not be directly tied to this feature request, so it would make sense to break this out to BUG ticket(s) to not mash it all under one for atomicity. — Reply to this email directly, view it on GitHub <#69 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZQV5IWTJRECS7CT6HFX5VD4CE2IVAVCNFSM6AAAAACPJMTVW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNRUHA2DCNZRGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[pretyflaco]

Shared with me today: https://tools.afribit.africa/fastlight
Afribit Kibera / Fastlight vibecoded a workaround for the troubles with the batch payments bugs mentioned here 🥲