Skip to content

v3.0.0

Latest
Latest

Choose a tag to compare

View all tags
@ericviana ericviana released this 18 Jun 14:57
v3.0.0
e277c90
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Breaking changes

This is a major release that makes customers the canonical resource and removes the deprecated receivers surface (mirrors blindpay-node #55). Code still using the receiver APIs from v2.x must migrate.

Removed

  • ReceiversService and all receiver methods/accessors on the BlindPay client and InstancesService (createReceiver, listReceivers, getReceiver, updateReceiver, deleteReceiver, getReceiverLimits, requestLimitIncrease, listLimitIncreaseRequests, and receivers(receiverId:)).

Renamed (Receiver* → Customer*)

  • Model types: Receiver → Customer, ReceiverOwner → CustomerOwner, ReceiverType → CustomerType, Create/Update/DeleteReceiver* → Create/Update/DeleteCustomer*, ReceiverLimits* → CustomerLimits*, ListReceiversResponse → ListCustomersResponse.
  • Files: Receiver.swift → Customer.swift, ReceiverLimits.swift → CustomerLimits.swift. The transitional Customer* alias file is dropped.
  • Sub-resource FK fields receiver_id → customer_id on BlockchainWallet, OfframpWallet, CustomerOwner, and LimitIncreaseRequest. Payins/payouts keep receiver_id (the API accepts both there).

Migration notes

  • Use blindpay.customers(customerId:) and the createCustomer / listCustomers / getCustomer / updateCustomer / deleteCustomer methods in place of the removed receiver equivalents.
  • listCustomers maps the clean customerId / customerName params to the receiver_id / receiver_name wire keys the API filter schema still expects, so the wire format is unchanged.

Full changelog: v2.10.0...v3.0.0

Assets 2
Loading