Wave 1: customer.* webhook events, customer_id filters, live-bug fixes

[ericviana]

What

Ships the part of the receivers-to-customers rename that the currently deployed BlindPay API already accepts, ahead of blindpay-v2 PR #1799 (still open, not deployed). Verified field-by-field against the deployed openapi.json vs the PR #1799 spec.

• WebhookEvents (the active enum used by CreateWebhookEndpointInput/WebhookEndpoint) gains CUSTOMER_NEW = 'customer.new', CUSTOMER_UPDATE = 'customer.update', CUSTOMER_DELETE = 'customer.delete', purely additive. RECEIVER_NEW/RECEIVER_UPDATE are kept and marked @deprecated (same idiom already used for $receivers in BlindPay.php).
• ListPayinsInput and ListPayoutsInput gain an additive customerId filter (mapped to customer_id) alongside the existing receiverId/receiver_id.
• Two live bugs fixed in Customers.php (not future work, broken today in shipped v2.4.0): Owner::fromArray and LimitIncreaseRequest::fromArray were reading $data['customer_id'] for nested response fields the deployed API still keys receiver_id (no dual-emit at that nesting level). Since both are non-nullable string constructor params, this threw a TypeError for any business customer with owners, and for every call to getLimitIncreaseRequests(). Both now read receiver_id again, matching what the deployed API actually returns.
• Deleted src/Types/WebhookEvent.php: a dead, unused duplicate of the events enum (confirmed zero references) that also failed php -l from a duplicated RECEIVER_DELETE case.
• Documented the Customers/CustomersWrapper resource in CLAUDE.md (it existed since an earlier commit but was never mentioned), noted Receivers as deprecated, and fixed a few doc examples that still referenced receivers/receiverId paths that no longer match the shipped code (bank-accounts nesting and blockchain wallet list already take customerId).
• Bumped VERSION in BlindPay.php from 2.4.0 to 2.5.0 (minor, additive only).

Why the webhook additions are safe today

The deployed WebhookEndpointIn.events enum in openapi.json already lists customer.new / customer.update / customer.delete alongside the receiver.* values, and the API dual-emits both event families. Subscribing to the new values works against production right now with no server-side changes needed.

What is deliberately NOT in this PR

The remaining wave-2 renames are held back because the deployed API does not accept them until blindpay-v2 PR #1799 ships:

• 11 field renames (customer_local_amount, customer_wallet_address, customer_network, customer_token, customer_invite_redirect_url, customer_rfi_emails_enabled, customers_amount, customer_type, customer_kyc_status, customer_aiprise_session_id, customer_aiprise_user_profile_id) - six of these aren't modeled in this SDK at all today, nothing to rename yet.
• RECEIVERS_* -> CUSTOMERS_* error codes - this SDK has no error-code enum (errors are a generic passthrough string), so N/A.
• Removing the legacy Receivers resource.
• Removing receiver.* from the webhook event enums.

Shipping any of that today would break every SDK user, since the deployed API doesn't have the corresponding server-side support yet.

Explicitly preserved (verified untouched)

receiver_amount (singular) on Payin, CreateEvmPayinResponse, Payout, Transfer, and both quote response types, plus CurrencyType::RECEIVER = 'receiver', are all unchanged - these mean "amount the receiving side gets" / currency_type value, not a reference to the customer resource, and are not part of this migration.

Build output

$ composer install --prefer-dist --no-progress --ignore-platform-req=php
... (installs cleanly; --ignore-platform-req=php needed only because the local test
environment runs PHP 8.5, newer than paratest's ~8.4 constraint in composer.lock -
pre-existing, unrelated to this change)

$ composer run test
  Tests:    91 deprecated (712 assertions)
  Duration: 0.17s
(all passing; "deprecated" here is PHPUnit flagging ReflectionProperty::setAccessible()
as a no-op deprecation under PHP 8.5 in the test harness itself, pre-existing across
the whole suite and unrelated to this change - baseline run before any edits showed
the identical 90 deprecated / 0 failed)

$ composer run lint:check
    PASS   .......................................................... 83 files

https://claude.ai/code/session_01F1stiNzuNtJXoXtiW9ZCbs

[BernardoSM]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.