Skip to content
Last updated

Changelog

June 2026

5 June

May 2026

27 May

18 May

  • Improve consistency regarding KYC review fields across the documentation.
  • Document correct return response from the KYC review endpoints
  • Improve wording in the Update KYC review endpoint

14 May

12 May

11 May

  • Added sandbox support for transfer refund webhooks. Simulating funds_refunded now triggers a transfers#refund webhook with a simulated refund amount.

8 May

6 May

4 May

April 2026

21 April

20 April

13 April

  • Add structured addresses and previous_instructing_agents in swift-in#credit webhook v4.0.0.

9 April

  • Add keyId field to Get Wise public signing key endpoint.
  • Documented global X-External-Correlation-Id header on all API operations. See correlation ID guide.
  • Documented global x-trace-id header on all API operations.
  • Documented 429 Too Many Requests response with Retry-After and X-Rate-Limited-By headers on all API operations.

March 2026

31 March

  • Consolidated Client Credentials Token and User Tokens into a single OAuth Token endpoint

30 March

26 March

18 March

  • Add new Event Ordering guide. Webhook events may not be delivered in the order they occurred — this guide explains how to use ordering fields to reconcile the correct sequence.
  • Add schema version 4.0.0 for all webhook event types. This version provides consistent millisecond-precision timestamps across all events, making it easier to determine event order. We recommend updating your subscriptions to use 4.0.0 to order events reliably.

12 March

9 March

3 March

February 2026

26 February

20 February

  • Adds support for providing the following on originators of third-party transfers
    • nationality: for PRIVATE originators
    • businessRegistrationDate: for BUSINESS originators

January 2026

15 January

  • Multiple ID fields are now explicitly documented as int64 (64-bit integer). Please ensure your integration stores these IDs using the appropriate 64-bit type (e.g., Long in Java, BIGINT in SQL).

    Key fields to note:

    • transfer ID - approaching the int32 upper bound
    • recipient ID - approaching the int32 upper bound
    • card transaction ID - past the int32 upper bound
    • user ID
    • profile ID
    • balance ID