# Release notes We continually improve Access Worldpay with new features and upgrades. Here's a summary of our latest releases. ## Checkout SDK ### React Native version 4 (20 November 2025) In React Native version 4.0.1 we have added: * **Auto-linking for a simpler integration** We have introduced auto-linking to link the native iOS and Android dependencies automatically without manual configuration and therefore simplifying your integration * **Support for placeholder color customization** We have added a support for [customizing the placeholder color](/products/checkout/react-native/optional-configuration#properties) within the (`AccessCheckoutTextInput`) allowing you to match the placeholder color with your application design. * **Updated underlying SDKs to latest version** * updated base Android SDK to 4.2.1 * updated base iOS SDK to 4.1 ## APMs API ### Release of Alipay+ (17 November 2025) You can now start using: - [Alipay+](/products/apms/alipayuni) ## Payments API ### Multiple features (14 November 2025) * **Partial authorization** You can now enable partial authorization by setting the [`acceptPartialAuthorization` key:value](/products/payments/openapi/payment/payment#payment/payment/t=request&path=instruction&d=0/value/acceptpartialamount) to `true`. This allows you to accept a partial payment if the full amount is not available, and then charge the remaining balance using a different payment method through a new authorization request. * **Payment reversal** You can now [reverse a payment](/products/payments/openapi/manage-payments/reversal) using a new [next action link](/products/payments/openapi/payment/payment#payment/payment/t=response&c=201&path=&d=0/_actions/reversepayment) received in your authorization response. * **Payment ID in responses** We now return a [`paymentId` in the responses](/products/payments/openapi/payment/payment#payment/payment/t=response&c=201&path=&d=0/paymentid) on the following authorization outcomes: `authorized`, `refused`, `sentForSettlement`, `sentForCancellation`, `sentForRefund`, `sentForPartialRefund`. The `paymentId` is a unique identifier for a payment that ties together payment lifecycle events. ## Account Payouts API ### Additional paymentState values (12 November 2025) You may now receive the following new [paymentState values](/products/account-payouts/openapi/get-payouts-by-payout-request-id/getbypayoutrequestid#get-payouts-by-payout-request-id/getbypayoutrequestid/t=response&c=200&path=paymentstate): * `IN_REVIEW` - the payout is under compliance review * `RFI_IN_PROGRESS` - the payout is on hold pending compliance review * `AWAITING_LIQUIDITY` - the payout is on hold due to insufficient funds The paymentState `RFI_IN_PROGRESS` and `AWAITING_LIQUIDITY` are not enabled by default. Please contact your Implementation Manager. ## Card Payments API ### Fast refunds (11 November 2025) [Fast refunds](/products/card-payments/features/fast-refunds) allow for refunds to credit a cardholder's account within 30 minutes, where the account accepts fast funds disbursements. ## Account Payouts API ### New daily reminder for insufficient liquidity (10 November 2025) You can now receive a [daily event reminding you that your account remains in deficit](/products/account-payouts/account-events#supported-event-webhooks) and must be credited to release pending payouts. ## APMs API ### Release of Bizum and release of preview docs for Alipay+ (06 November 2025) You can now: - start using [Bizum](/products/apms/bizum) and - preview [Alipay+](/products/apms/alipayuni) ## Card Payments API ### Multiple features (05 November 2025) * **Specify UnionPay as your customer's preferredCardBrand** When taking payment with a co-branded card, you can now specify `unionPay` as your customer’s [`preferredCardBrand`](/products/card-payments/openapi/other/recurring#other/recurring/t=request&path=instruction/routing/preferredcardbrand). * **New unionPay element in response** You now receive `unionPay` in your [response](/products/card-payments/openapi/other/authorize#other/authorize/t=response&c=201&path=&d=0/paymentinstrument/cardbrand) when processing a UnionPay payment. * **Update to challengePreference field** We have updated the `challengePreference` field to enable you to indicate `noChallengeRequestedTRAPerformed` in your [payment request](/products/card-payments/openapi/other/authorize#other/authorize/t=request&path=authentication/threeds/challengepreference). This update meets new standards required for Cartes Bancaires processing. ## Checkout SDK ### Android version 5 (30 October 2025) * **Co-branded cards** [This feature](/products/checkout/android/co-branded-cards) gives your customers a choice of card brands they can pay with in line with the [European Union (EU) Interchange Fee Regulation (IFR) 2015/751](https://eur-lex.europa.eu/eli/reg/2015/751). * **Simplified validation initializer** We have moved all available functions under `AccessCheckoutClient` to [initialize validation](/products/checkout/android/card-validator#function-and-parameter-descriptions) and create sessions. Before you had to use both the `AccessCheckoutValidationInitialiser` and `AccessCheckoutClient`. ## Checkout SDK ### iOS version 5 (30 October 2025) * **Co-branded cards** [This feature](/products/checkout/ios/co-branded-cards) gives your customers a choice of card brands they can pay with in line with the [European Union (EU) Interchange Fee Regulation (IFR) 2015/751](https://eur-lex.europa.eu/eli/reg/2015/751). * **Simplified validation initializer** We have moved all available functions under `AccessCheckoutClient` to [initialize validation](/products/checkout/ios/card-validator#function-and-parameter-descriptions) and create sessions. Before you had to use both the `AccessCheckoutValidationInitialiser` and `AccessCheckoutClient`. ## Payments API ### Multiple features (29 October 2025) * **SCA exemptions in authentication** You can now set an [`instruction.exemption.capability`](/products/payments/openapi/payment/payment#payment/payment/t=request&path=instruction&d=0/exemption) value of `authenticationOnly` or `authorizationAndAuthentication` to allow exemptions in authentication (3DS) to be returned. [See details](/products/payments/enable-features/sca-exemptions/) * **3DS support for encrypted Google Pay payments** You can now use [`instruction.threeDS`](/products/payments/openapi/payment/payment#payment/payment/t=request&path=instruction&d=2/threeds) with encrypted Google Pay payments. `PAN_ONLY` (non Android device tokens) payments can now automatically be prompted for 3DS authentication. [See details](/products/payments/google-pay/) * **Payment facilitator sub-merchant URL** You can now send a [`merchant.paymentFacilitator.subMerchant.url`](/products/payments/openapi/payment/payment#payment/payment/t=request&path=merchant/paymentfacilitator/submerchant/url) key:value in your payment request. This allows you to be compliant with scheme requirements. * **Additional 3DS outcome details in response** We now include additional details on `3dsUnavailable` outcome in the response. This includes `eci` and `version`. See the [full response body](/products/payments/openapi/3ds-actions/supply3dsdevicedata#3ds-actions/supply3dsdevicedata/t=response&c=201&path=&d=0/threeds). * **Customer's ipAddress is now used in authorization** We now use the [`instruction.customer.ipAddress` key:value](/products/payments/openapi/payment/payment#payment/payment/t=request&path=instruction&d=0/customer/ipaddress) in the authorization process for Customer Initiated Transactions. Previously the value was only used for 3DS authentication. ## Checkout Android SDK ### Version 4.2.1 - new XML properties and methods available to customize your views (28 October 2025) In version 4.2.1 of our [Checkout Android SDK](/products/checkout/android), we have introduced additional XML properties and methods supported by `AccessCheckoutEditText`. This enables you to further customize your views. Please refer to our [Optional configuration page](/products/checkout/android/optional-configuration) for details. ## Events API ### New and updated events (28 October 2025) * **New `requestExpired` event** We have added a new [`requestExpired` event](/products/events/openapi/payment/requestexpiredpayment) for all APMs. This allows you to find the events for which payment requests were initiated but expired due to customer inactivity. You can use this event for reconciliation purposes. * **New `tokenCreated` event for SEPA** You now receive a [`tokenCreated` event](/products/events/openapi/payment/tokencreated) with a SEPA token for successful SEPA payments. You can use this token to take recurring SEPA payments. * **Updated `tokenCreated` event for iDEAL** We have also updated our [`tokenCreated` event](/products/events/openapi/payment/tokencreated) to return an email address field for iDEAL payments. You can use this field to find stored token details that you have created to take recurring iDEAL payments. ## Card Payments API ### New object in post payment actions (27 October 2025) You can now submit a `reference` in your [refund](/products/card-payments/openapi/manage-payments/refund#manage-payments/refund/t=request&path=reference), [settle](/products/card-payments/openapi/manage-payments/settle#manage-payments/settle/t=request&path=reference) and [cancelation](/products/card-payments/openapi/manage-payments/cancel#manage-payments/cancel/t=request&path=reference) request. This allows you to identify a payment throughout its lifecycle. ## Card Payments API ### Toss Pay now available (22 October 2025) You can now include a [`customerData` object](/products/card-payments/openapi/other/authorize#other/authorize/t=request&path=authentication/customerdata) in your `authentication` object. This allows you to submit additional customer details necessary to meet local authentication, as required by country-specific regulations. Currently, the `customerData` object is used solely for domestic Toss Pay payments in South Korea. ## Card Payments API ### Fast refunds (20 October 2025) You can now submit the `fastRefund` object in your full or partial [refund](/products/card-payments/manage-payments##fully-refund-a-payment) request. This allows for refunds to be credited to a cardholder's account within 30 minutes, where the account accepts fast funds disbursements. To enable this feature, please speak to your Implementation Manager. ## Payment Queries API ### Last event, command ID and payment ID now in response (17 October 2025) You now receive a [`lastEvent`](/products/payment-queries/openapi/other/retrievebypaymentid#other/retrievebypaymentid/t=response&c=200&path=lastevent) in your response when [querying by `transactionReference`](/products/payment-queries/openapi/other/querybydaterange#other/querybydaterange/t=request&in=query&path=transactionreference) and [retrieving a payment](/products/payment-queries/openapi/other/retrievebypaymentid) using the `paymentId`. You now also receive a `commandId` when [retrieving a payment](/products/payment-queries/openapi/other/retrievebypaymentid) by `paymentId`. We now also include the `paymentId` in all responses. ## Account Payouts API ### Release of channel and routedChannel (09 October 2025) You can now submit a [`channel`](/products/account-payouts/openapi/single-payout/postpayout#single-payout/postpayout/t=request&path=instruction/channel) in your account payout request to send your payout down your preferred route. `channel` replaces the use of the `fastPayment` property which will continue to work for existing customers but will be removed in the next version. br We now also return a `routedChannel` in your GET response to advise which channel was used to route your payout. ## Beneficiary Account Verifications API ### Launch (09 October 2025) We have now released version 2025-01-01 of our new [Beneficiary Account Verifications API](/products/account-verifications/openapi). ## Card Payouts API ### Fast Access preferred card brand support (08 October 2025) You can now submit a `preferredCardBrand` in your [Fast Access request](/products/card-payouts/payouts#routing-your-fast-access-request). This allows you to request that your card payout is routed to your preferred card scheme (currently Maestro/Mastercard only). We have also added a new [`outcome` of `inReview`](/products/card-payouts/payouts#possible-outcomes). You might receive this outcome if your card payout request is being reviewed for legal or compliance reasons. ## Checkout Android SDK ### Version 4.2.0 - support for Android API level 24 (06 October 2025) * In version 4.2.0 of our [Checkout Android SDK](/products/checkout/android/v4), we have reduced the minimum supported version of Android from API level 26 to API level 24. * Please note that whilst Android API level 24 is now the minimum version supported by the Android SDK, some properties of the `AccessCheckoutEditText` component are not available on this API level. For more guidance regarding which properties are supported by the different Android API levels, please refer to our [methods table](/products/checkout/android/v4/optional-configuration#methods). ## APMs API ### New lastEvent value (01 October 2025) * We have added a new `lastEvent` value of `requestExpired`. See [Manage your APM](/products/apms/manage#PossiblelastEventvalues) for details. ## Exemptions API ### Exemption in authentication support (30 September 2025) * You can now set an [`exemption.capability`](/products/sca-exemptions/openapi/other/assessment#other/assessment/t=request&path=exemption) value of `authenticationOnly` or `authorizationAndAuthentication` to allow exemptions in authentication (3DS) to be returned. This was previously defaulted to `authorizationOnly`. * You can now also specify the `exemption.placement` and `exemption.type` per request. See [Exemption assessment](/products/sca-exemptions/assessment) for details. ## FraudSight API ### Exemption in authentication support (30 September 2025) * You can now set an [`exemption.capability`](/products/fraudsight/openapi/other/assessment#other/assessment/t=request&path=exemption) value of `authenticationOnly` or `authorizationAndAuthentication` to allow exemptions in authentication (3DS) to be returned. This was previously defaulted to `authorizationOnly`. * You can now also specify the `exemption.placement` and `exemption.type` per request. See [FraudSight assessment](/products/fraudsight/assessment) for details. ## APMs API ### Release of ACH and EFT (24 September 2025) You can now start using: - [ACH/eCHeck](/products/apms/ach) and - [EFT](/products/apms/eft) ## Card Payments API ### Additional fields in request (22 September 2025) You can now submit: * [`emailAddress`](/products/card-payments/openapi/other/authorize#other/authorize/t=request&path=customer/emailaddress) - allowing your customer to receive an email with the transaction outcome (if configured) * [`ipAddress`](/products/card-payments/openapi/other/authorize#other/authorize/t=request&path=customer/ipaddress) - as required for certain jurisdictions and/or MCCs * `phoneNumber` - added for future enhancements for Amex ## Card Payments API ### Surcharge and convenience fees (18 September 2025) You can now submit a [`surchargeAmount`](/products/card-payments/openapi/other/authorize#other/authorize/t=request&path=instruction/value/surchargeamount) and [`convenienceAmount`](/products/card-payments/openapi/other/authorize#other/authorize/t=request&path=instruction/value/convenienceamount) in your authorization, settlement and refund requests within the `value` object. This allows you to report the amount charged for card processing or online booking fees to remain compliant with scheme mandates. Ensure that the surcharge or convenience fee complies with local regulations and card network rules before applying. ## Card BIN Data API ### US debit network support (15 September 2025) We have now extended [`brand`](/products/card-bin/openapi/other/panlookup#other/panlookup/t=response&c=200&path=brand) to support the following US debit networks: * interlink * interac * jeanie * nyce * pavd * pulse * shazam * starAccess * star * accel * affn * ath * culiance ## Card Verifications API ### Payfac URL support in requests (all versions) (11 September 2025) If you are a PayFac merchant, you can now optionally supply a `submerchant.url` in your [card verification request](/products/card-verifications/openapi/other/cardverify#other/cardverify/request/body). This allows you to be compliant with scheme requirements. ## Events ### New payment events for Klarna (09 September 2025) We have added the following [Klarna](/products/apms/klarna) specific payment events: * [`chargedBack` event](/products/events/openapi/payment/chargedbackpayment) * [`cancelledByCustomer` event](/products/events/openapi/payment/cancelledbycustomerpayment) ## Account Payouts API ### Event webhook updates (28 August 2025) We have released a new ["RFI in Progress" webhook](/products/account-payouts/account-events#payout-rfi-in-progress) advising you that a payout is on hold pending a compliance review. We have also released preview documentation for: * [low balance](/products/account-payouts/account-events#low-balance) * [insufficient liquidity](/products/account-payouts/account-events#insufficient-liquidity) * [payout in review](/products/account-payouts/account-events#payout-in-review) and * [payout screening release](/products/account-payouts/account-events#payout-released) events. Additionally, you can preview documentation for extra fields, `channel` and `routedChannel`, we have added to our [success](/products/account-payouts/account-events#payout-success) and [reversal](/products/account-payouts/account-events#payout-reversal) webhooks. ## Account Payouts API ### Notification Of Change (NOC) US (26 August 2025) You may now receive a [Notification Of Change (NOC)](/products/account-payouts/account-events) to indicate that a beneficiary's bank details have changed for US Payouts. ## Card Payments API ### Partial authorization (16 July 2025) You can now enable partial authorization by setting the [`acceptPartialAuthorization` object](/products/card-payments/openapi/other/authorize#other/authorize/t=request&path=instruction/value/acceptpartialamount) to `true`. This allows you to accept a partial payment if the full amount is not available, and then charge the remaining balance using a different payment method through a new authorization request. ## Card Payments API ### Split funding (15 July 2025) You can now send a `splitFundingReference` in your [settlement](/products/card-payments/openapi/manage-payments/partialsettlement#manage-payments/partialsettlement/t=request&path=merchant/marketplace) and [refund requests](/products/card-payments/openapi/manage-payments/partialrefund#manage-payments/partialrefund/t=request&path=marketplace). Available for marketplaces and other merchant types, a `splitFundingReference` allows you to split acquiring funding into your secondary bank account. ## Payments API ### Authentication outage (15 July 2025) We can now auto-apply an [`authenticationOutage` exemption](/products/payments/openapi/payment/payment#payment/payment/t=response&c=201&path=&d=0/threeds) in authorization when we receive an `authenticationOutage` outcome from 3DS due to downstream issues (Visa/Mastercard etc). This is currently not enabled by default, speak to your Implementation Manager to be set up for `authenticationOutage` responses. ## HPP API ### Allowing MIT setup (14 July 2025) You can now submit ["subscription" payments](/products/hosted-payment-pages/openapi) allowing you to setup for future recurring Merchant Initiated Transactions through our [Payments API](/products/payments/). ## Card Payments API ### Payment facilitator sub-merchant URL (14 July 2025) You can now send a `paymentFacilitator.subMerchant.url` field in your [authorization request](/products/card-payments/authorize-a-payment). ## Payment Queries API ### Multiple additions to the response schema (09 July 2025) We now return additional payment information for [queries by date range](/products/payment-queries/query-by-date-range), [queries by transaction reference](/products/payment-queries/query-by-trans-ref), and [retrieving a single payment](/products/payment-queries/retrieve-by-payment-id), where this information is returned following your card payment authorization request made with either the [Payments API](/products/payments) or the modular [Card Payments API](/products/card-payments): - `scheme.reference` - `issuer.authorizationCode` - `paymentInstrument.card.number.cardBin` - `paymentInstrument.card.category` - `paymentInstrument.card.expiryDate` - `paymentInstrument.card.countryCode` - `paymentInstrument.card.issuerName` - `paymentInstrument.card.paymentAccountReference` - `updatedPaymentInstrument` ## APMs API ### Release of Bancontact, Open Banking and paysafecard (09 July 2025) You can now start using: - [Bancontact](/products/apms/bancontact) - [Open Banking](/products/apms/open-banking) - [PaysafeCard](/products/apms/paysafecard) You can now also start using [iDEAL recurring](/products/apms/ideal#example-requests). ## Events ### New payment events for Pix (02 July 2025) We have added the following [Pix](/products/apms/pix) specific payment events: * [`settlementInstructed` event](/products/events/openapi/payment/settlementinstructedpayment) * [`settlementRejected` event](/products/events/openapi/payment/settlementrejectedpayment) * [`topUpAccepted` event](/products/events/openapi/payment/topupacceptedpayment) * [`topUpRejected` event](/products/events/openapi/payment/topuprejectedpayment) You can use these events for reconciliation purposes. You must request for this to be enabled through [Celcoin](https://www.celcoin.com.br/cel_payments/pix/). ## APMs API ### Release of Pix preview docs (02 July 2025) You can now preview: - [Pix](/products/apms/pix) ## Split Payments API ### Version 2025-06-25 launch (02 July 2025) Launch of version 2025-06-25 of the [Split Payments API](/products/split-payments/). ## Payments API ### Multiple features (25 June 2025) * **Account updater support** You can now request real-time account updates (Visa cards only) when using a [previously stored card](/products/payments/store-a-card) using `instruction.requestAccountUpdater`. If the supplied card has been updated, we will return updated card details in the `updatedPaymentInstrument` object in the authorization response. * **`sequence` support in partial settle request** You can now provide the [`sequence.number` and `sequence.total` key:values](/products/payments/openapi/manage-payments/partialsettle#manage-payments/partialsettle/t=request&path=sequence) in the partial settle request. This represents the sequence number and total number of expected partial settlement requests for the payment. * **Relaxed email field validation to accept `"+"` character** You can now provide email address values containing the `"+"` character in front of the `"@"` (e.g. `paymentsAPI+test@worldpay.com`). ## Checkout SDK ### Support for co-branded cards in Web SDK (24 June 2025) You can now listen to the `wp:card-brands:change` event hook which will return the brands associated with the card number entered by your customer. This field replaces `wp:card:change` which will be deprecated in the next major version. ## APMs API ### Release of iDEAL and new field in SEPA (16 June 2025) You can now start using: - [iDEAL](/products/apms/ideal) Additionally, you can create [SEPA](/products/apms/sepa) mandates for non-EEA countries by sending `swiftBic` in your requests. ## Card Payments API ### Debit network returned in response (10 June 2025) You now receive a `paymentInstrument.debitNetwork` field in your [authorization response](/products/card-payments/openapi/other/authorize). This field advises which debit network the transaction was routed through. Receiving this field requires additional configuration, please contact your Implementation Manager. ## Checkout SDK ### New optional iOS configurations (09 June 2025) In the `AccessCheckoutUITextField`, we have added: * support for [`textContentType`](/products/checkout/ios/optional-configuration#properties) - this property allows to inform the system about the expected content type * support for [`inputAccessoryView`](/products/checkout/ios/optional-configuration#properties) - this property attaches an accessory view to the system keyboard * a new method [`setOnFocusChangedListener`](/products/checkout/ios/optional-configuration#methods) - allowing the UI to benefit from dynamic customization We have also fixed validation behavior to align with our other mobile SDKs to ensure a consistent user experience across our SDKs. ## Hosted Payment Pages ### Additional functionality (09 June 2025) We have released a number of [features](/products/hosted-payment-pages/openapi/other/create): * `settlement.auto` - allows you to disable auto settlement following a successful authorization * `threeDS.type` - allows you to "disable" 3DS on a per transaction basis * `fraud.type` - allows you to "disable" FraudSight on a per transaction basis. * `cancelOn.cvcNotMatched` - allows you to control skip auto-cancel behavior for CVC mismatch on a per transaction basis * `locale` - allows you specify supported locales, so that payment pages can load up in the specified language * `hostedCustomization` - additional CSS properties that allow you specify customization * `hostedProperties` - properties that allow you specify functionality ## Payments API ### Multiple features (5 June 2025) * **Co-branded card support** You can now [submit a `preferredCardBrand` value](/products/payments/openapi/payment/payment#payment/payment/t=request&path=instruction&d=0/paymentinstrument&d=0/routing) allowing the transaction to be processed through either of its payment networks. * **Cartes Bancaires support** You can now submit a payment request using a Cartes Bancaires card brand. * **Additional 3DS outcome details in response** We now include additional details from the 3DS authentication in the response. This includes `eci`, `version`, `status` and `dsTransactionId`. See the [full response body](/products/payments/openapi/3ds-actions/supply3dsdevicedata#3ds-actions/supply3dsdevicedata/t=response&c=201&path=&d=0/threeds). * **Sender date of birth for funds transfers (AFTs)** You can now send the date of birth of the sender in your [funds transfer](/products/payments/openapi/payment/payment#payment/payment/t=request&path=instruction&d=0/fundstransfer/sender/dateofbirth) (AFT) requests. This is required for some cross border funding transactions. * **Relax validation to support `moto` payments with a Checkout SDK session** You can now send a `"channel": "moto"` payment request along with a `paymentInstrument.type` of `checkout`. * **Revenue boost indicator added to response** `updatedPaymentInstrument.appliedNetworkToken` is set to `true` when a network token is automatically applied ## FX API ### New field in request (05 June 2025) You can now submit a `customerReference` field when [creating an external FX contract](/products/fx/openapi/other/postcontract). You can use this field to represent the payer who funds the FX contract. ## Hosted Payment Pages ### Payment query link in response (04 June 2025) You now receive a payment query `href` in [your response](/products/hosted-payment-pages/openapi/other/create#other/create/response&c=200) which allows you to check the status of the payment and follow on with the appropriate next actions. ## Checkout SDK ### New optional Android configurations (02 June 2025) We have added support for: * `autofillHints` - allowing for credit card information to be auto-filled * `onFocus` events - allowing the UI to benefit from dynamic customization Additionally, we have implemented a fix to ensure the SDK provides appropriate `AccessCheckoutExceptions` instead of `IllegalArgumentExceptions`. ## Marketplaces ### Preview docs (14 May 2025) We have released the first draft documentation for our [Marketplaces flow](/products/marketplaces/). This includes: #### New APIs: * [Parties API](/products/parties/) * [Split Payments API](/products/split-payments/) #### New API versions of: * [Account Payouts API](/products/account-payouts/) * [Balances API](/products/balance/) * [Account Transfers API](/products/transfers/) * [Statements API](/products/statements/) ## Events ### New tokenCreated event for iDEAL (13 May 2025) You now receive a [`tokenCreated` event](/products/events/openapi/payment/tokencreated) with an iDEAL token for successful iDEAL payments. You can use this token to take recurring iDEAL payments. ## Events ### Additional optional fields in APM authorized event (13 May 2025) You will now receive additional APM specific fields in the `authorized` event [webhooks](/products/events/openapi/payment/authorizedpayment) for Klarna, iDEAL, MyBank and Open Banking payments. These fields are not always returned by the APM. ## Card verifications ### Scheme reference in every verification response (12 May 2025) You now receive a scheme reference in your [card verification response](/products/card-verifications/openapi/other/cardverify#other/cardverify/response&c=201/body) irrespective of the outcome. We previously only returned this in `verified` responses. This advises you that a card was tokenized even though the card verification itself failed. ## APMs API ### Release of BLIK and Przelewy24 (08 May 2025) You can now start using: - [BLIK](/products/apms/blik) - [Przelewy24](/products/apms/przelewy24) ## Card Payments API ### Sender date of birth for funds transfers (AFTs) (28 April 2025) You can now send the date of birth of the sender in your [funds transfer](/products/card-payments/openapi/other/authorize#other/authorize/t=request&path=instruction/fundstransfer) (AFT) requests which is required for some cross border funding transactions. ## Card Payments API ### Command ID and Payment ID in responses (24 April 2025) We now return a `commandId` and a `paymentId` in the following responses: * [CIT authorization response](/products/card-payments/openapi/other/authorize#other/authorize/response&c=201) * [MIT authorization response](/products/card-payments/openapi/other/recurring#other/recurring/response&c=201) * [settle](/products/card-payments/openapi/manage-payments/settle#manage-payments/settle/response&c=202) * [partial settle](/products/card-payments/openapi/manage-payments/partialsettlement#manage-payments/partialsettlement/response&c=202) * [refund](/products/card-payments/openapi/manage-payments/refund#manage-payments/refund/response&c=202) * [partial refund](/products/card-payments/openapi/manage-payments/partialrefund#manage-payments/partialrefund/response&c=202) The `paymentId` is a unique identifier for a payment that ties together payment lifecycle events. The `commandId` is a unique identifier for a single instance of an interaction with our API. This will support new future business type flows. ## Tokens API ### Deleting Network Payment Tokens (NPTs) (23 April 2025) You can now [delete NPTs](/products/tokens/querying-network-tokens-and-provisioning-cryptograms#deleting-network-tokens). A typical use case, why you might want to do this, is if your customer withdraws their consent to store their card details. ## Card Payments API ### Exemption fields in authorization request (22 April 2025) In your [authorization request](/products/card-payments/authorize-a-payment#sca-exemptions), you can now include: * a 3rd party Transaction Risk Analysis (TRA) tool exemption * a 3DS `authenticationOutage` exemption (if returned by 3DS), to increase the chance of an authorized outcome (no liability shift is granted) Both require additional configuration and permission, please contact your Implementation Manager. ## 3DS API ### Authentication outage (22 April 2025) Receive an `authenticationOutage` outcome in the [authentication](/products/3ds/web/authentication) response if there are downstream issues (Visa/Mastercard etc). You can use this as a prompt to apply an `authenticationOutage` exemption in the payment authorization request. ## FraudSight API ### Partial payment instrument support (11 April 2025) Perform a risk assessment without the full card number. You can now use our `card/plain+masked` paymentInstrument in your [assessment request](/products/fraudsight/assessment). ## APMs API ### New commandId field in responses (08 April 2025) You now receive a [`commandId`](/products/apms/openapi/other/payment#other/payment/t=response&c=201&path=commandid) in responses. This action ID is generated by us and identifies a single merchant interaction (authorization, settlement etc). We use it across multiple APIs, allowing to tie a payments lifecycle events together. ## Payments API ### Account Funds Transfer (AFT) support (03 April 2025) You can now send a [`fundsTransfer`](/products/payments/openapi/payment) object in your payment requests. This unlocks the ability to process AFTs compliant with card scheme requirements. AFTs are used to transfer funds from a card account to another destination, rather than for the provision of goods or services. ## Account Payouts API ### Estimated payout date (27 March 2025) You will now receive `estimatedSettlementDate` in your [account payout notifications](/products/account-payouts/v2/notifications). This gives you an estimate date of when the beneficiary will receive their funds. ## FX API ### New intent value (26 March 2025) You can submit an `intent` of "PAYOUT LIVE RATE" when [getting an FX rate](/products/fx/openapi/other/getfxrates#other/getfxrates/t=request&in=query&path=intent) or [creating an FX quote](/products/fx/openapi/other/postfxquote#other/postfxquote/t=request&path=intent). This allows you to get real-time FX rates. ## Payments API ### Auto-provision cryptogram for NPTs (26 March 2025) You can now submit a Customer Initiated Transaction (CIT) using a Network Token provisioned by us [without providing a `cryptogram`](/products/payments/openapi/payment). ## Card Payments API ### Google Pay decrypted payments (26 March 2025) You can now use the "card/networkToken+googlepay" `paymentInstrument` in your [authorization request](/products/card-payments/authorize-a-payment) to process decrypted Google Pay payments. ## Card Payments API ### Additional funds transfer types (25 March 2025) You can now send additional fund transfer [`type` and `purpose` values](/products/card-payments/openapi/other/authorize#other/authorize/t=request&path=instruction/fundstransfer) in the `fundsTransfer` object in your [authorization request](/products/card-payments/authorize-a-payment). This allows you to be compliant with card scheme requirements for fund transfers. ## Card Verifications API ### Additional funds transfer types (13 March 2025) You can now send an additional fund transfer [`type` and `purpose` values](/products/card-verifications/openapi/other/cardverify#other/cardverify/t=request&path=&oneof=0/instruction/fundstransfer/type) in the `fundsTransfer` object in your [verification request](/products/card-verifications/verifications#example-request). This allows you to be compliant with card scheme requirements for fund transfers. ## Checkout SDKs ### Flutter support (12 March 2025) We have now released supporting documentation on how to integrate either our [Checkout Web](/products/checkout/web) or [Native Android](/products/checkout/android) & [iOS SDKs](/products/checkout/ios) into your Flutter application. ## Card Payments API ### Incremental authorization and partial cancellation support (25 February 2025) You can now submit an [incremental authorization](/products/card-payments/openapi/other/authorize#other/authorize/t=request&path=instruction/value/estimated) for an estimated initial authorization. You can now also [cancel an authorization partially](/products/card-payments/manage-payments#partially-cancel-an-authorization) using a new next action link received in your authorization response. ## 3DS API ### New challenge preference value (19 February 2025) You can now submit a `challenge.preference` value of `noChallengeRequestedTRAPerformed` in your [3DS authentication request](/products/3ds/openapi/other/authenticate#other/authenticate/t=request&path=challenge/preference). You can use this when Transaction Risk Analysis (TRA) has been performed using an approved third party vendor and an SCA exemption has been recommended for the authentication. ## APMs API ### Release of AlipayCN, WeChat Pay and MyBank (19 February 2025) On version 2024-07-01 you can now start using: - [AlipayCN](/products/apms/alipaycn) - [WeChat Pay](/products/apms/wechatpay) On version 2023-06-01 you can now start using: - [MyBank](/products/apms/20230601/mybank) ## Payments API ### SCA exemptions in authorization (18 February 2025) You can now request [SCA exemptions in authorization](/products/payments/enable-features/sca-exemptions/) from Worldpay and have them automatically applied in the payment. ## Payments API ### MOTO payments support (05 February 2025) You can now process Mail Order/Telephone Order payments by submitting [`"channel": "moto"` key:value](/products/payments/enable-features/moto/). ## Payments API ### Payment facilitator support (28 January 2025) You can now facilitate transactions on behalf of your sub-merchants using [the `merchant.paymentFacilitator` object](/products/payments/enable-features/payment-facilitator/). ## Payments API ### Disable automatic sentForCancellation outcome based on CVC/AVS (17 January 2025) You can now set `settlement.cancelOn.cvcNotMatched` or `settlement.cancelOn.avsNotMatched` to `disabled` in the [auto settlement](/products/payments/enable-features/auto-settlement/) flow to prevent a payment outcome of `sentForCancellation`. Disabling these fields means that a transaction will not automatically be cancelled when CVC/AVS checks fail. ## Events ### New tokenCreated event for Klarna (14 January 2025) You now receive a [`tokenCreated` event](/products/events/openapi/payment/tokencreated) with a Klarna token for successful Klarna payments. You can use this token to take recurring Klarna payments. ## APMs API ### Release of Klarna and Konbini on version 2024-07-01 (14 January 2025) You can now start using: - [Klarna](/products/apms/klarna) and - [Konbini](/products/apms/konbini) ## Card BIN API ### Visa Flexible Credentials (VFC) service support (10 January 2025) We have now added support for [Visa's Multi Access Account](/products/card-bin/openapi/other/panlookup#other/panlookup/t=response&c=200&path=multipleaccountaccess) indicator. This service gives each participating Visa issuer the capability to link a single Visa credential it has issued, to two or more accounts. details summary Releases 2024 ## FraudSight API ### Refusal description and refusal code in the update payment request (17 December 2024) You can now add the `refusalCode` and `refusalDescription` to the [payment update](/products/fraudsight/update/payment) request. ## Card Payments API ### Preferred card brand in requests (04 December 2024) You can now submit `preferredCardBrand` in your [authorization request](/products/card-payments/authorize-a-payment) to honor your customer's card brand choice for co-badged cards. ## Card Payments API ### L2/L3 and airline data (22 November 2024) You can now submit additional [L2/L3](/products/card-payments/authorize-a-payment#level-2-/-level-3-data) and [airline](/products/card-payments/authorize-a-payment#airline-itinerary-data) data in your authorization or settlement request. Supplying this information means you may benefit from reduced cost and more efficient processing. ## Card Verifications API ### Optional billing address (21 November 2024) You can now send an optional `billingAddress` object in your [verification request](/products/card-verifications/verifications#example-request) for `card/token`, `card/networkToken` and `card/networkToken+ApplePay` payment instrument types. ## Payments API ### Network token support (21 November 2024) You can now submit a `paymentInstrument.type` of `networkToken` in a [stored card](/products/payments/use-a-stored-card/) flow. You must provide the `paymentInstrument.cryptogram` value as part of the request. ## Payment Queries API ### Multi-entity support (18 November 2024) You can provide [multiple entity references in date range queries](/products/payment-queries/query-by-date-range) to query payments based on `entityReference` (also known as `entity`). ## APMs API ### Release of AlipayHK and SEPA on version 2024-07-01 (13 November 2024) You can now start using: - [Alipay Hong Kong](/products/apms/alipayhk) and - [SEPA](/products/apms/sepa) ## Card Payments API ### New reason codes for repeat payments (MITs) (23 October 2024) You can now submit the following additional values for `customerAgreement.type` in your [MIT request](/products/card-payments/repeat-payments): * `reauthorization` - use this where the original authorization has expired before funds could be sent for settlement * `resubmission` - use this where the original authorization was declined due to insufficient funds, but the customer has already received goods or services * `noShow` - use this to charge a customer who fails to attend a previously-made reservation (in line with a pre-agreed cancellation policy) e.g. a guaranteed reservation is made at a restaurant but the customer does not turn up * `delayedCharge` - use this to charge a customer for additional items after you have processed an original CIT payment (in line with previously agreed terms), e.g. charges for hotel mini-bar usage after the customer has checked-out and the original payment has been sent for settlement ## Payments API ### Installment and unscheduled MIT payments (17 October 2024) You can now setup [installment plans](/products/payments/recurring-first/) by submitting a `customerAgreement.type` of `installment`. A typical use case would be, to spread the cost of a larger payment over time. Additionally, this unlocks installment payments in [Latin America](/products/payments/enable-features/latam-installments/). You can now setup also [unscheduled MIT agreements](/products/payments/recurring-subsequent/) by submitting a `customerAgreement.type` of `unscheduled`. A typical use case for this, might be an automatic top-up when the account value falls below a threshold. ## APMs API ### Version 2024-07-01 (10 October 2024) We've revamped [our API](/products/apms) to be clearer and more intuitive for you. The new design aligns with our other APIs, making it easier for you to integrate multiple services. This update also standardizes the JSON structure and field validations across all our APIs. This ensures a consistent and reliable experience. ## Payments API ### React Native support (08 October 2024) We have documented [code samples](/products/payments/enable-features/3ds-authentication/react-native) showing you how to integrate 3DS within a Payments API flow, in a React Native application. ## 3DS API ### React Native support (08 October 2024) We have documented [code samples](/products/3ds/react-native/) showing you how to integrate our 3DS flow in a React Native application. ## Card Payments API ### Account updater requests (30 September 2024) You can now request real-time account updates (Visa cards only) when using a previously [stored card using `instruction.requestAccountUpdater`](/products/card-payments/authorize-a-payment#store-a-card). If the supplied card has been updated, we will return updated card details in the `updatedPaymentInstrument` object in the authorization response. ## Checkout SDK ### Use of Shadow DOM with Web SDK (19 September 2024) You can now use the Access Checkout Web SDK in a [Shadow DOM](/products/checkout/web/shadow-dom). This can be useful when implementing custom elements. ## Card Payments API ### New request fields for payments in Latin America (09 September 2024) You can submit the following fields: * `fundingType` - allows you to specify either `credit` or `debit` as the funding source in "combo cards" issued in Latin America * `salesTax` - allows you to specify the sales tax of a transaction ## Card Payouts API ### Network Token support (v2,v3 and v4) (29 August 2024) You can now use the `card/networkToken` paymentInstrument in your [payout request](/products/card-payouts/payouts). ## Money Transfers API ### Mastercard Send support for non-staged digital wallets (29 August 2024) You can now push [funds to a Mastercard](/products/money-transfers/make-money-transfer) using either a plain or tokenized card. ## Payments API ### Recurring subscription support (29 August 2024) You can now [set up a subscription payment](/products/payments/recurring-first) and make [subsequent recurring payments](/products/payments/recurring-subsequent). This includes a subscription agreement with no initial value (e.g. free trial). ## Payments API ### Store a card only support (29 August 2024) You can now [store a card](/products/payments/store-a-card) for future Customer Initiated Transactions (CIT) without an initial payment. You can use this for adding a card to an ecommerce account. ## Payments API ### 3DS deviceData channel (29 August 2024) You can specify [threeDS.deviceData.channel](/products/payments/enable-features/3ds-authentication#emvco-required-values) as `browser` to indicate the integration for web or native for iOS/Android. We strongly recommend you provide this to keep authentication rates as high as possible. ## Checkout SDK ### Checkout iOS SDK version 4 (23 August 2024) #### PCI-SSF assessment and certification The [Checkout iOS SDK](/products/checkout/ios/v4) has gone through a thorough assessment against the PCI-SSF standard and is now certified PCI-SSF compliant. This will help you reduce the scope of your own PCI assessments. #### Minimum version requirements: - The minimum iOS version supported by the SDK for the purpose of providing a PCI-SSF compliant solution is iOS 15 - Although the SDK supports iOS 12 to iOS 14 it is not PCI-SSF compliant for these versions. This is because Apple has stopped supporting/delivering security fixes for these versions #### Version 3 functionality we have removed in version 4: - Support for using `UITextField`. `AccessCheckoutUITextField` must be used instead. This component is dedicated to capturing and encapsulating your customer's card details to minimize your exposure to PCI Data - Support for passing card details directly to create an instance of `CardDetails` - Support for using `merchantId()` in `AccessCheckoutClientBuilder` to pass your Checkout ID. This is replaced by `checkoutId()` ## Checkout SDK ### Checkout Android SDK Version 4 (23 August 2024) #### PCI-SSF assessment and certification The [Checkout Android SDK](/products/checkout/android/v4) has gone through a thorough assessment against the PCI-SSF standard and is now certified PCI-SSF compliant. This will help you reduce the scope of your own PCI assessments. #### Minimum version requirements: - The minimum Android version supported by the SDK for the purpose of providing a PCI-SSF compliant solution is Android 12 - Although the SDK supports Android 8 to 11 it is not PCI-SSF compliant for these versions. This is because Google has stopped supporting/delivering security fixes for these versions. #### Version 3 functionality we have removed in version 4: - Support for using `EditText`. `AccessCheckoutEditText` must be used instead. This component is dedicated to capturing and encapsulating your customer's card details to minimize your exposure to PCI Data - Support for passing card details directly to create an instance of `CardDetails` - Support for using `merchantId()` in `AccessCheckoutClientBuilder` to pass your Checkout ID. This is replaced by `checkoutId()`. ## Card Verifications API ### Cardholder name inquiries (25 July 2024) You can now make a `nameInquiry` for Visa cards with our [Card Verifications API](/products/card-verifications/verifications). This allows you to check the validity of the cardholder name provided. ## Payments API ### Financial Services MCC6012 support (22 July 2024) You can now provide, `debtRepayment`, `consumerBillPayment` and `recipient` information in your [payment request](/products/payments/enable-features/financial-services-mcc6012-mcc6051) ## FX API ### Markup FX API (22 July 2024) If you are a Multi-Currency Pricing customer, you can now [add a markup](/products/fx/fx-markup) to your FX rate. ## Payment Queries API ### New API launch (18 July 2024) Make smart decisions by querying your card payments data in real-time, based on a variety of parameters. We return: - information relating to the transaction and payment instrument - an array of timestamped events - action links allowing you to perform payment actions (such as refunds) ## Exemptions API ### Network token support (17 July 2024) You can now use our `card/networkToken` paymentInstrument in your [assessment request](/products/sca-exemptions/assessment). ## FraudSight API ### Network token support (17 July 2024) You can now use our `card/networkToken` paymentInstrument in your [assessment request](/products/fraudsight/assessment). ## 3DS API ### Additional browser fields for authentication requests (17 July 2024) You can now submit the following fields in your [authentication request](/products/3ds/web/authentication): - `deviceData.timeZone` - `deviceData.browserScreenWidth` - `deviceData.browserScreenHeight` - `deviceData.browserColorDepth` - `deviceData.javascriptBrowserEnabled` - `deviceData.javaBrowserEnabled` ## FX API ### New forward FX rate endpoint (09 July 2024) You can now [lock a forward FX rate](/products/fx/forward-fxrates) for a specific currency pairing and amount for a future date up to 30 days. ## Card Verifications API ### Card Verifications Version 6 (27 June 2024) The new [Card Verifications](/products/card-verifications) API introduces a new single endpoints and consistent JSON structure to simplify your integration. * removal of separate endpoints for intelligent and dynamic verifications * field value based routing for one time vs card on file * request and response field name changes to align with industry standard * added support for network payment tokens * added support for AFT related optional fields ## APMs API ### Release of WeChat Pay (26 June 2024) You can now start using: - [WeChat Pay](/products/apms/20230601/wechatpay) ## Events ### New downStreamReference in webhook (25 June 2024) You now receive a `downStreamReference` in your payment [webhooks](/products/events). You can use this reference for reconciliation purposes, as it directly maps to the Payment ID shown in your Worldpay reports. ## Card BIN API ### Release of our Card BIN API (24 June 2024) You can now use our [card BIN service](/products/card-bin) to request data to optimize your checkout experience, reduce risk and comply with regulations. ## APMs API ### Release of WeChat Pay documentation (06 June 2024) You can now view the documentation: - [WeChat Pay](/products/apms/20230601/wechatpay). ## APMs API ### Release of Alipay Hong Kong (05 June 2024) You can now start using: - [Alipay Hong Kong](/products/apms/20230601/alipayhk) ## APMs API ### Release of BLIK (30 May 2024) You can now start using: - [BLIK](/products/apms/20230601/blik) ## Events ### Additional Events (20 May 2024) We have added the following events: * settled * settlementFailed * refunded * informationRequested These events are dependent on certain use cases and we don't always return them. Please speak to your Implementation Manager for further information. ## Checkout SDK ### React Native Version 3 (15 May 2024) **Support for SAQ-compliance** - We have added a new UI Component (`AccessCheckoutUITextField`) dedicated to capturing and encapsulating your customer's card details to minimize your exposure to PCI Data. **Simpler integration with useAccessCheckout() hook** - introducing a `useAccessCheckout()` hook where the merchant configuration for sessions and validation is provided #### Version 2 functionality that is deprecated in version 3: - Support for standard `TextInput` components has been removed. You must now use `AccessCheckoutTextInput` components - Support for the `AccessCheckout` class and the `useCardValidation` / `useCvcOnlyValidation` has been removed and is replaced by the `useAccessCheckout()` hook ## Card Payments API ### Merchant Initiated Transactions (30 April 2024) We have now added support for [Merchant Initiated Transactions](/products/card-payments/repeat-payments) (MIT) to Card Payments Version 7. ## Card Payments API ### Funds transfers (30 April 2024) You can now submit funds transfers (otherwise known as Account Funding Transactions or AFTs) using the `instruction.fundsTransfer` object in your [authorization request](/products/card-payments/authorize-a-payment#optional-parameters). Non-purchase money movements from a Visa or Mastercard to another account should typically use this. ## Checkout SDK ### Session without CVC (25 April 2024) You can now [omit CVC](/products/checkout/web/card-only#create-a-session-without-cvc) when creating a card session with our Web SDK. ## APMs API ### Release of Multibanco (11 April 2024) You can now start using: - [Multibanco](/products/apms/20230601/multibanco) ## All APIs (except Payouts API) ### ELO and EFTPOS support (09 April 2024) You can now accept ELO and EFTPOS as a payment method. ## Card Payments API ### Consumer Bill Payment flag (09 April 2024) You can now submit a `consumerBillPayment` flag in your [authorization request](/products/card-payments/authorize-a-payment/#optional-parameters). If you are registered with Visa as a Consumer Bill Payment Service provider, you must set this to `true` for any payments taken for the purpose of paying consumer bills. ## Card Payments API ### Latin America Installments (04 April 2024) You can now submit Latin America installment payments using the `instruction.customerAgreement` object in your [authorization request](/products/card-payments/authorize-a-payment#optional-parameters). This allows your customers to opt to pay the full value in installments. ## Card Payments API ### Latin America Document Reference (04 April 2024) You can now submit the `customer.documentReference` in your [authorization request](/products/card-payments/authorize-a-payment#optional-parameters). This is used in some Latin America regions to verify the identity of the cardholder using a tax or document reference. It is strongly recommended to include this for Brazil domestic processing. ## Card Payments API ### Recipient fields (MCC 6012) (04 April 2024) You can now submit the `recipient` object in your [authorization request](/products/card-payments/authorize-a-payment#optional-parameters). If you are using MCC 6012 in Europe, you should include data about the recipient of financial services within this object. ## APMs API ### Release of new APMs (20 March 2024) You can now start using: - [Euteller](/products/apms/20230601/euteller) - [paysafecard](/products/apms/20230601/paysafecard) - [SafetyPay](/products/apms/20230601/safetypay) You can now view documentation for: - [Alipay HK](/products/apms/20230601/alipayhk) - [BLIK](/products/apms/20230601/blik) ## Account Verifications API ### New optional consumerBillPayment field in instruction object (v5) (25 March 2024) You can now send a `consumerBillPayment` field in [your Verification request](/products/card-verifications/v5/verifications). You must set this to `true` for any verifications made for the purpose of paying consumer bills in the future. ## Events API ### Additional IPs (07 March 2024) We have added additional IPs for outgoing traffic. You must whitelist [all of our IPs](/products/events#network-access) on your Web Application Firewall (WAF) to allow webhooks to be received by 8th April 2024. details summary List of additional IPs ``` 3.11.50.124 3.11.213.43 3.14.190.43 3.121.172.32 3.125.11.252 3.126.98.120 3.139.153.185 3.139.255.63 13.200.51.10 13.200.56.25 13.232.151.127 34.236.63.10 34.253.172.98 35.170.209.108 35.177.246.6 52.4.68.25 52.51.12.88 108.129.30.203 ``` ## APMs API ### Release of Bancontact and Przelewy25 (29 February 2024) You can now start using: - [Bancontact](/products/apms/20230601/bancontact) - [Przelewy24](/products/apms/20230601/przelewy24) ## Verified Token API ### New Verified Tokens endpoint (all version) (28 February 2024) We have added a new [`oneTime` endpoint](/products/verified-tokens/create-verified-token). You can use this endpoint if PSD2 regulations apply to you (primarily if you are located in the UK, EEA, and Gibraltar). If you intend to keep the token for future payments, proceed to a `challengeMandated` 3DS flow to remain SCA compliant, before taking a payment. You can also use this, if you want to take a one-off payment. You must delete the token afterwards. ## APMs API ### Release of Trustly (26 February 2024) You can now start using: - [Trustly](/products/apms/20230601/trustly) ## Card Payments API ### Card Payments Version 7 (20 February 2024) The new Card Payments API introduces new endpoints to simplify your integration. To upgrade, read through our [migration guide](/products/card-payments/v7-migration-guide) which holds a summary of the changes/new features. ## APMs API ### Release of Open Banking (23 January 2024) You can now start using: - [Open Banking](/products/apms/20230601/open-banking) ## Checkout SDK ### Checkout iOS and Android SDK Version 3 (22 January 2024) We have released Version 3 of our [iOS](/products/checkout/ios/v3) and [Android](/products/checkout/android/v3) SDKs. ### Enhanced card session support - The SDKs now return a card session URL in the form of `https://access.worldpay-bsh.securedataplatform.com/sessions/...`. Previously, the card session URL looked like this: `https://access.worldpay-bsh.securedataplatform.com/verifiedTokens/sessions/...` The format of the new card session URL supports our new upcoming Payments API, whilst also remaining compatible with our Verified Tokens API. ### SAQ-A compliance support - We have added a new UI Component (`AccessCheckoutEditText`) dedicated to capturing and encapsulating your customer's card details to minimize your exposure to PCI Data. ### Version 2 functionality that is deprecated in version 3: - Support for using `EditText`(Android)/`UITextField` (iOS) (planned removal in version 4) - Support for directly passing card details to create an instance of `CardDetails` (planned removal in version 4) - Support for using `merchantId()` in `AccessCheckoutClientBuilder` to pass your Checkout ID is deprecated and replaced by `checkoutId()` (planned removal of `merchantId()` in version 4) ### Checkout SDK ### Checkout Web and React Native SDK Version 2 (22 January 2024) We have released Version 2 of our [Web](/products/checkout/web) and [React Native](/products/checkout/react-native/v2) SDKs. - The SDKs now return a card session URL in the form of `https://access.worldpay-bsh.securedataplatform.com/sessions/...`. Previously, the card session URL looked like this: `https://access.worldpay-bsh.securedataplatform.com/verifiedTokens/sessions/...` The format of the new card session URL supports our new upcoming Payments API, whilst also remaining compatible with our Verified Tokens API. ## Account Verifications API ### New optional recipient object in Verification request (18 January 2024) You now have the option to send a `recipient` object within your [Verification request](/products/card-verifications/v5/verifications). You should send this if your MCC is 6012 or 6051 to remain PSD2 compliant and avoid acquirers refusing your payment. ## 3DS API ### Network Payment Token support for 3DS authentications (17 January 2024) You can now authenticate a Network Payment Token using the "card/networkToken" `paymentInstrument` via the 3DS [SDK](/products/3ds/android-ios/authentication#authentication-example-request) and [Web](/products/3ds/web/authentication#authentication-example-request) flow. ## 3DS and Card Payments API ### Added support for Cartes Bancaires in 3DS2 authentications (10 January 2024) We now provide additional values in the [authentication and 3DS verification responses](/products/3ds/web/authentication#authentication-responses) when the card brand is Cartes Bancaires. These additional values must then be applied in the [authorization request](/products/card-payments/authorize-a-payment). details summary Releases 2023 ## APMs API ### Release of Konbini, UnionPay and SEPA (12/07/2023) You can now start using: - [China UnionPay](/products/apms/20230601/unionpay) - [Konbini](/products/apms/20230601/konbini) - [SEPA](/products/apms/20230601/sepa) ## All APIs ### New rawCode in refused responses (11/28/2023) You can now receive a `rawCode` in refusal responses. See [raw response codes](/products/reference/refusal-response/scheme-codes) for more information. ## 3DS API ### Acquirer Id in 3DS request (11/28/2023) You can now supply the `merchant.acquirerId` in your [authentication request](/products/3ds/web/authentication). This flags to the issuer that the following authorization will be done with an external acquirer. ## Payments API ### Magic values for online refunds (11/27/2023) Use our [magic values](/products/card-payments/testing#online-refund-test-values) to test your online refunds. ## Payments API ### Apple Pay decrypted support for authorization endpoint (v6) (11/06/2023) You can now use our `card/networkToken+applepay` paymentInstrument with our [one time authorization](/products/card-payments/v6/authorize-a-payment) endpoint. ## Payments API ### Additional fields returned in payment response (v6) (11/06/2023) You now receive a `paymentInstrument` object in authorized responses to your [authorization request](/products/card-payments/v6/authorize-a-payment), and Sent for Settlement responses to your [sale request](/products/card-payments/v6/migrate-cardonfile-sale) for `card/plain`, `card/token`, and `card/checkout`. ## Payments API ### Card network token support in payment request (v6) (11/06/2023) You can now use our `card/networkToken` paymentInstrument in our [authorization](/products/card-payments/v6/authorize-a-payment) and [migrateCardOnFileAuthorize](//products/card-payments/@v6/authorise-a-cardonfile-payment.md#card-on-file-without-verification-authorization-request) endpoints. ## FX PI ### Release of the new FX API (10/24/2023) You can now [create an FX quote](/products/fx/create-fxquote) or retrieve and [FX rate](/products/fx/fxrate) or [FX quote](/products/fx/retrieve-fxquote). ## All APIs ### New rawCode in refused responses (10/12/2023) You can now receive a `rawCode` in refusal responses. See [raw response codes](/products/reference/refusal-response/scheme-codes) for more information. ## HPP ### New conditional field in HPP request (v1) (10/12/2023) You can now submit the `expiry` in a [hosted payment pages request](/products/hosted-payment-pages/setup-a-payment#optional-parameterss). This allows you to configure the duration your customer can access the payment link. An example of when you might use this, is issuing invoices or putting a hold time on an order. ## Verifications API ### New rawCode field in Verification response (10/06/2023) You may now receive the `rawCode` in our [Verification response](/products/card-verifications/v5/verifications#verifications-response). This allows merchants with multiple PSPs to have a common retry logic using the raw response code from the card scheme. ## Payouts API ### Payouts Version 4 (09/11/2023) * Version 4 introduces Mastercard Send. This allows you to send funds directly to a consumer's bank account within 30 minutes or less using fastAccess endpoint. This change introduces updates to the Payouts responses. * Additionally, Version 4 removes the "queryRequired" value as the `outcome`, so that the next actions for an inconclusive payout are more clear to you. ## All APIs ### New optional email and telephone fields in Payment Facilitator merchant block (08/24/2023) * You now have the option to send an `email` and `telephone` field within your payment facilitator merchant object. ## All APIs ### Payment Facilitator Sub-Merchant ID max length increased to 15 (08/16/2023) * The paymentFacilitator `merchantId` now has a maximum digit length of 15. The previous limit was 7. ## APMs API ### Release of iDEAL and Paypal (12 August 2023) You can now start using: - [iDEAL](/products/apms/20230601/ideal) - [PayPal](/products/apms/20230601/paypal) ## Account API ### Launch of Account Transfers, Statements and Balances API (07/27/2023) * You can now use our [Account Transfers](/products/transfers/v1),[Statements](/products/statements/v1) and [Balances](/products/balance/v1) APIs. ## Payments API ### New intent for card on file endpoints (07/06/2023) * You can now submit a new `intent` value of `subscription` in your [card on file](/products/card-payments/v6/authorise-a-cardonfile-payment) request. ## Events ### New public certificate for Events service (06/29/2023) * You must update your public certificate for [the Events service](/products/events/certificate) by 6th July 2023. ## HPP/ Docs ### Hosted Payment Pages/ Documentation landing page update (06/15/2023) * We have released our [Hosted Payment Pages](/products/hosted-payment-pages) API documentation. Alongside, we have redesigned our [landing page](/) to make the decision, which integration is for you, easier. ## ALL APIs ### Updated security best practices (05/31/2023) * We have added [information on our Web Application Firewall](/products/reference/security) and how you should handle traffic using our Fully Qualified Domain Names. ## Tokens API ### Added PAR support for Network Tokens (05/18/2023) * We have now added `paymentAccountReference` (PAR) support for [network payment tokens](/products/tokens/querying-network-tokens-and-provisioning-cryptograms). ## Payments API ### New action link in partial refund response (05/11/2023) * The [response of a partial refund request](/products/card-payments/v6/manage-payments#partially-refund-a-payment) returns a link to allow you to perform another partial refund. ## Payments API ### New Mastercard test values (04/20/2023) * We have added a new set of Mastercard `refusalAdvice` [magic values](/products/card-payments/testing). This enables to you to test the different refusal outcomes in your Payment response. ## Verifications API ### New optional refusalAdvice field in refusal response (04/20/2023) * You will now receive a Merchant Advice Code (MAC) as `overrideName` in the [not verified response](/products/card-verifications/v5/verifications#verifications-response), if you have requested to receive this. ## APMs API ### Optional billing address and email address for Paypal (04/03/2023) * The `billingAddress` and `shopperEmailAddress` are now optional in your [Paypal sale request](/products/apms/20230601/paypal). ## Tokens API ### Increase allowed Token updates (03/15/2023) * We have increased the number of updates you can make to a [token](/products/tokens/create-a-token) in a rolling 30 day period, from 10 updates to 50. ## Payments API ### New Payment Facilitator fields (03/14/2023) * You can now supply payment facilitator subMerchant email and telephone number in your [Card Payments authorization request](/products/card-payments/v6/authorize-a-payment). ## Payments API ### Payment Facilitator field state validation change (03/14/2023) * The payment facilitator `state` field in the [Card Payments authorization request](/products/card-payments/v6/authorize-a-payment) now supports 1-3 alphanumeric characters. ## Tokens API ### New fundingType field in Token response (03/08/2023) * You now receive a new `fundingType` field in your [token response](/products/tokens/create-a-token#responses) with possible values of: * `debit` * `credit` * `unknown` ## Verifications API ### Additional fundingType values in response (v4 + v5) (03/01/2023) * The field `fundingType` in the `paymentInstrument` object of your [Verification response](/products/card-verifications/v5/verifications) can now have the following additional values: * `chargeCard` * `prepaid` * `deferreddebit` * We have added these to the already existing values of `debit` and `credit`. ## Verifications API ### New optional category field in response (v4 + v5) (03/01/2023) * You now have an additional field of `category` in the card section of your [oneTime response](/products/card-verifications/v5/verifications#verifications-response) if you have opted in to receive it. ## Checkout SDK ### Release of React Native SDK (02/28/2023) * You can now integrate our React Native SDK into your native app to create uniquely styled and branded checkout forms. ## FraudSight ### Optional IP address field in fraud assessment request (02/15/2023) * You now have the option to send the IP address of your customer's device in the [fraud assessment request](/products/fraudsight/assessment#assessment-example-request). * If you are not supplying device data via ThreatMetrix, you can send the IP address in this field and create manual fraud rules. ## 3DS API ### Optional override field for authentication requests (02/15/2023) * You now have the option to send `overrideName` in your authentication request with our [3DS Web API](/products/3ds/web/authentication). This field allows you to override the merchant name sent to the issuer. ## 3DS API ### Optional shipping address fields in 3DS authentication request (v2/v3) (02/15/2023) * You now have the option to send the shipping address in the authentication request for our 3DS [Web API](/products/3ds/web/authentication) and [Android-iOS SDKs](/products/3ds/android-ios/authentication). Tip: We recommend you send these details, if the shipping address is different to the billing address. ## Verified Tokens API ### Extended expiry for tokens and verified tokens (01/31/2023) * The default expiry date/time of a token is 7 days in Try and 4 years in the Live environment. This expiry is extended by 7 days or 4 years after any use of the token, if under half of the time remains on the token. ## Docs ### New documentation menu (01/30/2023) * We have changed the left hand navigation of our documentation. This will help you to find the right API documentation quicker. ## ALL APIs ### Updated security best practice (01/23/2023) * We have updated our "certificate handling" page to a [security best practices guide](/products/reference/security). * We have now included a set of our latest secure set of ciphers. Additionally, you will find information on our Client Authority. Our certificates will switch from presenting certificates signed by DigiCert to Sectigo. ## Payments API ### Network tokens (v3) (01/06/2023) * You can now create [network tokens and cryptograms](/products/tokens/create-a-network-token) with our Tokens API. You can use these for card on file sale payments. * You can also use these tokens across other service providers or payment gateways. details summary Releases 2022 ### Optional shopperId field in fraud assessment request (12/15/2022) * You now have the option to send a `shopperId` field with account risk data in the [fraud assessment request](/products/fraudsight/assessment#additional-fields-in-assessment-request). * Use `shopperId` to create manual fraud rules and identify your customers. ### Money Transfers (12/07/2022) * You can now push funds to an eligible card using our [Money Transfers](/products/money-transfers/make-money-transfer) API. ### MOTO payments (v6) (11/29/2022) * You now have the option to accept Mail Order Telephone Order (MOTO) payments with our [authorize](/products/card-payments/v6/authorize-a-payment#additional-parameter-descriptions), [migrateCardOnFileAuthorize](/products/card-payments/v6/authorise-a-cardonfile-payment#optional-parameter-description) and [migrateCardOnFileSale](/products/card-payments/v6/migrate-cardonfile-sale#additional-optional-fields) endpoints. ### Caret color customization and numeric keypad (Web Checkout SDK) (11/07/2022) * You can now customize the [caret color](/products/checkout/web/styles#allowed-css-properties) in PAN, Expiry date and CVC input fields with the new version of our Web SDK 1.11.0. * On mobile devices, these input fields now display a numeric keypad as the customer enters their card details. ### ACH verification (v5) (11/07/2022) * You can now verify the accounts of your US-based customers with our [ACH verification](/products/card-verifications/v5/verifications) service. ## 3DS API ### 3DS1 test values unavailability (10/18/2022) * 3DS1 test values are no longer available by default as 3DS1 has been decommissioned by the card schemes. We can enable these test values if required. ### Optional shipping address field in PayPal sale request (10/12/2022) Sending shipping address details is now optional in [PayPal sale request](/products/apms/20230601/paypal). ### Optional cardholder name field in 3DS authentication request (10/12/2022) Sending the cardholder name is now optional in [3DS authentication request](/products/3ds). ### Optional CVC field in the verification request (v5) (10/11/2022) You now have the option to submit the CVC in the one-time and card on file [verification requests with a token](/products/card-verifications/v5/verifications). Providing the CVC value can improve the verification acceptance rate. ### Optional device data fields in 3DS authentication request (v2/v3) (10/10/2022) You now have the option to send the browser language and IP address details of your customer's device in the authentication request for our [3DS Web API](/products/3ds/web/authentication) and our [Android-iOS SDKs](/products/3ds/android-ios/authentication). In case of unsuccessful device data collection, providing these values increases the chances of successful authentication. ### riskProfile in card on file (with verification) payment requests (v6) (07/04/2022) You can now submit your `riskProfile` to our [card on file (with verification)](/products/card-payments/v6/authorise-a-cardonfile-payment#card-on-file-authorization-with-verification) endpoint in your payment requests. You then receive an exemption result and reason in the response. Use it to apply the [SCA exemption](/products/sca-exemptions) in the payment request and update the [FraudSight](/products/fraudsight) data model to benefit future payments. ### Optional field in verification requests for cardOnFile resource (06/20/2022) You can now supply `storedCredentials.reason` as an optional field in the [cardOnFile intelligent verification request](/products/card-verifications/v5/verifications#cardOnFile-intelligent-verification) and [dynamicCardOnFile verification request](/products/card-verifications/v5/verifications#dynamiccardonfile-verification). This optional field in the verification request allows you to indicate the reason for merchant initiated transactions using stored credentials. ### Swift package manager support (version 2.4.0 onwards) (06/15/2022) [Swift package manager](/products/checkout/ios#swift-package-manager) support is now available for our iOS SDK version 2.4.0 onwards. ### Partial refund for iDEAL payments (05/31/2022) You can now take [partial refunds](/products/apms/20230601/manage#partial-refund) for iDEAL payments. ### Partial refund for PayPal payments (05/25/2022) You can now take partial refunds for [PayPal payments](/products/apms/20230601/paypal) ### Refund request URI update (iDEAL) (05/06/2022) We have updated the refund request URI for you to process the [full refund](/products/apms/20230601/manage#refund) for iDEAL payments. ### Release of iDEAL (03/17/2022) You can now take payments using [iDEAL](/products/apms/20230601/ideal). ### Release of PayPal (03/08/2022) You can now take payments using [PayPal](/products/apms/20230601/paypal). ### Additional elements for not verified token response (all versions) (03/08/2022) - In version 3, we now create unverified tokens in case of account verification failure and return `code` and `description` as part of the ["not verified" token response](/products/verified-tokens/create-verified-token#responses). - In version 2, we now create a unverified token `href` in case of account verification failure and return `code` and `description` as part of the ["not verified" token response](/products/verified-tokens/v2/create-verified-token#responses). - In version 1, we now create a unverified token `href` in case of account verification failure as part of the ["not verified" token response](/products/tokens/v1/create-a-token#responses). ### React.js integration example for our Web SDK (02/24/2022) We have added an [integration example using a React.js application](/products/checkout/web/integration-react) to our Web SDK documentation. ### New remove feature for our Web SDK (02/24/2022) We have added a feature allowing you to [remove the Web SDK](/products/checkout/web/card-and-cvc#removing-the-sdk) from a page. details summary Releases 2021 ### Tokens version 3 (12/28/2021) Version 3 is introduced to successfully process entity based billing. You must now supply the new mandatory field `merchant.entity` in your [create token request](/products/tokens/create-a-token). ### Vue.js integration example for our Web SDK (12/08/2021) We have added an [integration example using a Vue.js application](/products/checkout/web/integration-vue-js) to our Web SDK documentation. ### Network token for card on file sale requests (11/09/2021) You can now use our `card/networkToken` paymentInstrument in our [`payments:migrateCardOnFileSale](/products/card-payments/v6/migrate-cardonfile-sale) endpoint. A network token uses a 16-digit token number, provided by the schemes, to replace an original card number. ### Scheme reference for card on file token requests (09/10/2021) You can now submit the scheme `reference` in your [migrateCardOnFile token](/products/card-payments/v6/authorise-a-cardonfile-payment#card-on-file-without-verification-authorization-request) and [migrateCardOnFileSale token](/products/card-payments/v6/migrate-cardonfile-sale#additional-optional-fields) requests. This request parameter allows you to take a repeat payment with our APIs, linking to an agreement established with a different PSP. ### PAN formatting feature for Checkout SDK (09/06/2021) You can now use PAN formatting for our [Android](/products/checkout/android/card-validator#pan-formatting), [iOS](/products/checkout/ios/card-validator#pan-formatting) and [Web](/products/checkout/web/formatting) SDK. The card number formats as the customer types when you implement this feature. ### Payouts to wallets (06/11/2021) You can now make a [payout to a wallet](/products/card-payouts/wallets). ### Release of Canadian EFT (05/25/2021) You can now take payments using [Canadian Electronic Funds Transfer (EFT)](/products/apms/20230601/paydirect/eft). ### Exemption result for one time auth (05/25/2021) You now receive an exemption result result and reason in your [authorization response](/products/card-payments/v6/authorize-a-payment#response) if you have provided a riskProfile in your request. v6 ### 3DS version 3 (05/12/2021) Version 3 of our 3DS API has a new set of magic values used by the Cardinal Sandbox. It also comes with an improved look for the challenge display. ### Risk factor results (04/09/2021) You now receive a `verificationFailed` result in your [authorization response](/products/card-payments/v6/authorize-a-payment#response) if the issuer identifies a conflict. ### Optional narrative field in verified token request (03/19/2021) You now have the option to supply a narrative in your [verified token request](/products/verified-tokens/create-verified-token), allowing your customers to clearly see where the verified token request is coming from and helping to avoid confusion. ### Card brand configuration for our iOS and Android SDK (03/15/2021) You can now customize your checkout further by configuring your card brands. This new and optional feature allows you to restrict the cards that you accept on your checkout form for our [android](/products/checkout/android/card-validator#card-brand-restriction-optional-) and [iOS](/products/checkout/ios/card-validator#card-brand-restriction-optional-) SDK. ### Optional narrative field in verified token request (03/09/2021) Sending the cardholder name is now optional for our [Payments](/products/card-payments/v6), [Verifications](/products/card-verifications/v5/verifications) and [Payouts service](/products/card-payouts). Whilst we still recommend that you send this information, you now have the option to omit it. ### Card brand configuration for our Web SDK (02/15/2021) Control the cards you want to accept on your checkout form with our [card brand configuration feature](/products/checkout/web/card-brands) for our Checkout Web SDK. ### Optional statement narrative for verifications (02/15/2021) We've made the statement narrative element for our [Verification service](/products/card-verifications/v5/verifications) optional. This now defaults to 'Active Card Check' if you don't supply a narrative. ### Payouts to a Wallet with Apple Pay decrypted (01/27/2021) Send funds to your customers' Apple Pay accounts using our [Apple Pay decrypted payment instrument for Payouts](/products/card-payouts/payouts). ### Customization for our Checkout iOS SDK validator (01/11/2021) We have released a new version of the iOS SDK - 2.1.0. This version allows for `UITextField`s in the [validation feature](/products/checkout/ios/v3/card-validator). details summary Releases 2020 ### Apple Pay decrypted for recurring payments (11/27/2020) Use the decrypted model for [Apple Pay Merchant Initiated Transactions](/products/card-payments/v6/authorise-a-recurring-payment#recurring-authorization-without-verification) to submit a payment request using Network Token details - useful if you're using tokens across multiple providers. ### Apple Pay decrypted verifications (11/23/2020) Use the [decrypted model](/products/card-verifications/v5/verifications#apple-pay-decrypted) for Apple Pay to verify accounts and submit a payment request using Network Token details - useful if you're using tokens across multiple providers. ### Release of our first APM - ACH/ eCheck (11/19/2020) We've created a new [APMs (Alternative Payment Methods) section](/products/apms/20230601) in our docs under the 'pay' product category which contains individual guides for each APM as we release them. With that comes our first APM guide for [ACH](/products/apms/20230601/paydirect/ach/sale), also known as eCheck payments - a popular credit transfer and Direct Debit payment method for our US customers. ### Apple Pay decrypted for card on file payments (11/17/2020) Use the decrypted model for [Apple Pay Customer Initiated Transactions](/products/card-payments/v6/authorise-a-cardonfile-payment#-migratecardonfile-authorization-request) to submit a payment request using Network Token details - useful if you're using tokens across multiple providers ### Accessibility feature for Web SDK (11/10/2020) Set your [accessibility configuration](/products/checkout/web/accessibility) to set the language of an element for screen readers and help ensure your checkout meets an AA rating against [WCAG standards](https://www.w3.org/WAI/standards-guidelines/wcag/?mkt_tok=eyJpIjoiTVdKa09UZzBZVEF5T1RSaiIsInQiOiIzbUNmMzJPTnhmbnJDa1wvTVFpaytIMnpUVldrek9JemZsNkFyTXRrWVVXNEZUXC9QSU1PdlhlK1gwSDhiMDBPam1vczhQVVlNZFU3MWFmSUpXUHRjeVpzQkpKQ3l6S1Jic2pvWmRVblZMb0ZOSXE2Nm0xRzRRemU0cUpSUURkYzNMIn0%3D). ### Clear form feature Web SDK (11/10/2020) Use clear form on our [Checkout Web SDK](/products/checkout/web) to input multiple sets of card details without reloading the SDK. ### CVC session lifespan increase (10/19/2020) The lifespan of the CVC session for our [Checkout SDK](/products/checkout) has increased to 15 minutes, giving you longer to take a payment. ### Optional billing address in Mobile Wallet requests (10/06/2020) You now submit your customer's billing address details in your [requests for Mobile Wallet payments](/products/card-payments/v6/authorize-a-payment#optional-fields-in-an-authorization-request). ### AVS results in Mobile Wallet responses (09/22/2020) You now get AVS results returned in our [responses for Mobile Wallet payments](/products/card-payments/v6/authorize-a-payment#response). This helps your business understand risk factors where your customer's AVS is unchecked, unmatched, or unsupplied. ### Querying Mobile Wallet tokens (09/01/2020) We've included instructions on how to query card network tokens in our [Tokens documentation](/products/tokens/querying-and-updating-tokens) - Use this to show the tokenized card details to your customer on a payment page, or if you need a next available action link to update your customer's details. ### Verified Tokens version 3 (08/18/2020) We've released Version 3 of our [Verified Tokens service](/products/verified-tokens/create-verified-token#responses), helping you analyze transactions with card data returned in our Verified Token responses. ### Checkout SDK version 2 (07/30/2020) You can now [create a CVC session](/products/checkout) for iOS and Android when submitting a payment alongside a new or card on file Verified Token. This provides extra security and is required for MCC 7995, 7800, 7801, 7802 and 9406, if you are not authenticating your customer. ### Verifications version 5 (06/18/2020) You must now submit `narrative` in your [intelligent](/products/card-verifications/v5/verifications#intelligent-verification) and [dynamic](/products/card-verifications/v5/verifications#dynamic-verification) verification requests. ### Tokens version 2 (06/08/2020) Our new [Tokens version 2](/products/tokens/create-a-token#responses) API gives you improved analytics - returning the BIN and card brand extra data alongside the token content. ### Scheme reference submission (05/28/2020) You can now submit the scheme `reference` in your [repeat payment requests](/products/card-payments/v6/authorise-a-recurring-payment#recurring-authorization-without-verification). This allows you to take a repeat payment with our APIs, linking to an agreement established with a different PSP. ### 3DS version 2 (05/26/2020) We have introduced a new error for invalid card numbers and have changed the formatting of all our error messages within the [3DS service](/products/3ds/v2/web/authentication). Our authentication responses now also include a payload, ready in support for a native mobile integration. And, useful for tracing, we are now sending the `transactionId` in our `signatureFailed` outcome response. ### Cancel links for partially settled payments (05/20/2020) We'll now send you a [cancel link](/products/card-payments/v6/manage-payments#partially-settle-an-authorization) for a partially settled payment to let you release funds. ### Payouts version 3 (05/11/2020) Version 3 introduces updates to the merchant response. The curies array block now **only** lives **inside** the `_links` JSON block. ### Payouts response format changes (5/11/2020) The curies array block has been updated to live **inside** the `_links` JSON block as well as **outside**. ### New character for transactionReference (05/05/2020) You can now accept + as a character in the `transactionReference` field. Click [here](/products/reference/formatting) to see more information on our formatting rules.