feat: migrate receivers → customers in CLI - #12
Closed
alvseven wants to merge 8 commits into
Closed
Conversation
- rename all receiver commands to customer (listCustomers, createCustomer, etc.) - update API paths from /receivers to /customers - rename command group from 'receivers' to 'customers' - update all user-facing labels and descriptions
- Rename all exported functions: getReceiver→getCustomer, createReceiver→createCustomer, updateReceiver→updateCustomer, deleteReceiver→deleteCustomer, getReceiverLimits→getCustomerLimits, getReceiverLimitsIncreaseRequests→getCustomerLimitIncreaseRequests - Rename option param receiverId→customerId across all sub-resource functions (bank-accounts, blockchain-wallets, virtual-accounts, offramp-wallets, wallets) - Add create_limit_increase subcommand under customers - Restore missing functions removed in prior commit: createCustomerLimitIncrease, listWallets, getWallet, getWalletBalance, createWallet, deleteWallet, listTransfers, getTransfer, createTransfer, trackTransfer, createTransferQuote, getInstanceFees, initiateTos, uploadFile - Update all --receiver-id flags to --customer-id across bank_accounts, blockchain_wallets, virtual_accounts, offramp_wallets, wallets commands - Update schema.ts: receivers→customers resource, receiver_id→customer_id field names - Fix initiateTos to send customer_id body key instead of receiver_id
alvseven
force-pushed
the
alves/migrate-receivers-to-customers
branch
from
June 16, 2026 04:20
b9ed77a to
fa38efb
Compare
The receivers→customers rename over-renamed the Terms-of-Service body FK to customer_id, but the /tos endpoint still expects receiver_id — node and the Swift SDK both send receiver_id there, and the changelog lists only payins/payouts as accepting both names. Keep the clean --customer-id flag but map it to receiver_id on the wire; update the test assertion to match.
The receivers→customers rename changed the resource path and name but NOT the ID prefix — customer IDs are still re_(nanoid) per the changelog (https://www.blindpay.com/changelog/2026-06-04-customers-rename). Replace the incorrect cu_ example IDs (cu_xyz/cu_1/cu_new) with re_ in the resource tests.
The SEPA bank-account create only wired up 3 of node's 9 sepa_beneficiary_* fields (iban, bic, legal-name), leaving the required address_line_1, city, postal_code and country — plus optional address_line_2 and state_province_region — unreachable from the CLI. Add the missing flags + body mapping and a test covering the full field set (mirrors blindpay-node #50).
This was referenced Jun 17, 2026
Contributor
Author
|
Closing as superseded. The receivers→customers rename already landed on |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
receiverscommands tocustomers(customers list/get/create/update/delete)customers limits,customers limits_increase_requests,customers create_limit_increasebank_accounts,blockchain_wallets,virtual_accountsto use--customer-idinstead of--receiver-id/limits/customers/{id}(was wrong/customers/{id}/limits)/customers/{id}/limit-increaseschema.tsresource name and field namesTest plan
bun run typecheckcleanblindpay customers listworksblindpay customers limits <id>returns limitsblindpay bank_accounts list --customer-id <id>works