feat: add Customers resource, deprecate Receivers (v2.4.0) - #30
Merged
Conversation
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Mirrors blindpay-node v3.11.0:
- New Customers/ resource (parallel to Receivers/, targets /customers/* API paths)
- BankAccounts, VirtualAccounts, BlockchainWallets, OfframpWallets, CustodialWallets
now hit /customers/{customer_id}/... and take customerId named arg
- BlindPay::$customers accessor added
- BlindPay::$receivers marked @deprecated
https://www.blindpay.com/changelog/2026-06-04-customers-rename
Folds the api-sync content into the customers-resource minor:
- New createSepa method (POSTs type=sepa to /customers/{customer_id}/bank-accounts)
- CreateSepaInput + CreateSepaResponse readonly types
- sepaBeneficiaryBic field on BankAccount, GetBankAccountResponse,
CreateInternationalSwiftInput
- New Resources/Ownership/Ownership.php (instance ownership migration)
- ManualExecutionStatus type + field on Payin
- billingFeeAmount + cpnPaymentId fields on Payout
- receiver.delete WebhookEvent
- BlindPay::VERSION bumped 2.3.0 → 2.4.0
…bugs found via live QA
Three bugs caught by live QA against dev instance:
- ListBankAccountsResponse::fromArray expected {data: [...]} but the
API returns a plain array (mirrors node SDK #56)
- IndividualWith*KYC $aipriseValidationKey typed as 'string' but the
API returns null when absent — switched to ?string
- Rail enum was missing 'sepa' and 'ted' cases that the API returns
Test fixture for it_lists_bank_accounts updated to match real API
response shape (plain array, not data-wrapped).
…data,pagination})
alvseven
force-pushed
the
alves/customers-resource
branch
from
June 16, 2026 03:54
6168188 to
e57d72a
Compare
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
2 participants
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.
No description provided.