generated: '2026-07-19'
method: searched
source: https://developer.fin.com/changelogs/2026-04-20
versioning:
  scheme: uri-path
  versions: [v1, v2, v3]
  current: v2 (customers/virtual-accounts/transactions), v3 (beneficiaries)
  docs: https://developer.fin.com/
deprecation:
  policy_url: https://developer.fin.com/changelogs/2026-04-20
  deadline: '2026-05-20'
  sunset_header: false
  summary: >-
    An April 20, 2026 migration guide set a May 20, 2026 deprecation deadline
    moving several v1 endpoints to v2 and v2 beneficiary creation to v3. Business
    customer statuses were remapped (QUEUED -> PROCESSING), capabilities moved to
    a dedicated GET /v2/customers/{customer_id}/capabilities endpoint, and new
    beneficiary status values were introduced.
  migrations:
    - from: POST /v1/customers/business
      to: POST /v2/customers/business
    - from: POST /v1/customers/business/attach
      to: POST /v2/customers/{customer_id}/business/attach
    - from: POST /v1/customers/associated-parties/individual/attach
      to: POST /v2/customers/{customer_id}/associated-parties/individual/attach
    - from: GET /v1/customers
      to: GET /v2/customers
    - from: GET /v1/customers/{customer_id}
      to: GET /v2/customers/{customer_id}
    - from: POST /v2/beneficiaries
      to: POST /v3/beneficiaries
    - from: GET /v1/beneficiaries/details
      to: GET /v2/beneficiaries/details
    - from: v1 virtual-account endpoints
      to: v2 virtual-account endpoints
status_page: https://fin.instatus.com
operational_information:
  bank_holidays: https://developer.fin.com/operational-information/bank-holidays-2026
  processing_windows: https://developer.fin.com/operational-information/processing-windows-and-cutoffs
  compliance_sla: https://developer.fin.com/operational-information/sla-for-compliance
changelog_ref: changelog/fin-changelog.yml