|
| 1 | +--- |
| 2 | +title: 22 May 2025 |
| 3 | +type: release |
| 4 | +--- |
| 5 | + |
| 6 | +## New features |
| 7 | + |
| 8 | +💳 You can now disable users from updating their card settings in Swan's Web Banking from your **Dashboard** > **Web banking** settings tab. |
| 9 | +When disabled, users with the `CanUpdateCards` permission can only update card limits through your product, not Web Banking. |
| 10 | + |
| 11 | +## Improvements |
| 12 | + |
| 13 | +🧭 We've made several improvements to your **Dashboard**: |
| 14 | +- The Dashboard search now returns more **accurate results**. |
| 15 | +Results automatically narrow as you type and add more details. |
| 16 | +This update is available on the Account Holders, Onboarding, Account, Account Memberships, and Capital Deposits pages. |
| 17 | +- **Filters** have a new look across all Dashboard pages to help you find data more efficiently. |
| 18 | +We added **quick filters** for all **verification statuses** on the Account Holders page based on user feedback. |
| 19 | +We **removed the Verifications page** because the new filters provide the same information in a more accessible way. |
| 20 | + |
| 21 | +🔍 We've added [new filters](https://api-reference.swan.io/inputs/transactions-filters-input/) to enhance searching for [transaction information](/topics/payments/overview/guide-get-transaction-info/) by **amount** and **execution date** in the **API**: |
| 22 | + |
| 23 | +- **Amount** filters: we added `isAboveAmount` and `isBelowAmount`. We also updated the `amount` filter to return an exact match. |
| 24 | +These filters are now cumulative and will replace the current `amount` field in the transactions search filter (*see upcoming breaking change*). |
| 25 | +- **Execution date** filters: we added `isAfterExecutionDate` and `isBeforeExecutionDate`. |
| 26 | + |
| 27 | +✍️ The `requestMerchantPaymentMethods` mutation now validates your [SEPA Creditor Identifier (SCI)](/topics/merchants/online/sdd/#sci) when you request [SEPA Direct Debit](/topics/merchants/online/sdd/guide-request/). |
| 28 | +If the SCI is invalid, the mutation will reject it, helping you avoid blocked transactions in the future. |
| 29 | + |
| 30 | +📝 You can now retrieve all transactions initiated by a standing order using the `standingOrder.transactions` [query](https://api-reference.swan.io/objects/standing-order/#standingordertransactionstransactionconnection-). |
| 31 | + |
| 32 | +## API updates |
| 33 | + |
| 34 | +### Upcoming breaking changes |
| 35 | +👥 Starting **June 19th**, the `amount` field will be removed from the transactions `search` filter. |
| 36 | +Please use the amount filters to refine your search. |
| 37 | + |
| 38 | +💸 Starting **June 19th**, the `beneficiaryId` and `isMyOwnIban` input fields will be removed from the `initiateCreditTransfers` mutation. |
| 39 | +The `isMyOwnIban` field will become optional. |
| 40 | + |
| 41 | +🛑 Starting **June 19th**, a new rejection type, `ValidationRejection`, will be used to validate an input in the `initiateCreditTransfers` mutation. |
| 42 | + |
| 43 | +🚫 Starting **June 19th**, calls to `scheduleStandingOrder` with an invalid `reference` will be rejected. |
| 44 | +See the [API reference](https://api-reference.swan.io/inputs/schedule-standing-order-input#schedulestandingorderinputreferencestring-) for the regex pattern. |
0 commit comments