Release Notes

We have increased the number of updates you can make to atokenin a rolling 30 day period, from 10 updates to 50.

You can now supply payment facilitator subMerchant email and telephone number in yourCard Payments authorization request.

The payment facilitator state field in theCard Payments authorization requestnow supports 1-3 alphanumeric characters.

You now receive a new fundingType field in yourtoken responsewith possible values of:

• debit
• credit
• unknown

The field fundingType in the paymentInstrument object of yourVerification responsecan now have the following additional values:

• chargeCard
• prepaid
• deferreddebit

We have added these to the already existing values of debit and credit.

You now have an additional field of category in the card section of youroneTime responseif you have opted in to receive it.

You can now integrate our React Native SDK into your native app to create uniquely styled and branded checkout forms.

You now have the option to send the IP address of your customer's device in thefraud asssessment request.

If you are not supplying device data via ThreatMetrix, you can send the IP address in this field and create manual fraud rules.

You now have the option to send overrideName in your authentication request with our3DS Web API. This field allows you to override the merchant name sent to the issuer.

You now have the option to send the shipping address in the authentication request for our 3DSWeb APIandAndroid-iOS SDKs.

We recommend you send these details, if the shipping address is different to the billing address.

You can now provide your customer's verification result in the authentication JSON block forpullFromCard requests.

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.

We have changed the left hand navigation of our documentation. This will help you to find the right API documentation quicker.

We have updated our "certificate handling" page to asecurity best practices guide.

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.

We have re-ordered and updated:

• next action name in the _links object and
• curies name in the curies array block

in ourPayPal responses.

You can now createnetwork tokens and cryptogramswith 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.

You now have the option to send a shopperId field with account risk data in thefraud assessment request.

Use shopperId to create manual fraud rules and identify your customers.

You can now push funds to an eligible card and pull funds from a card using ourMoney TransfersAPI.

You now have the option to accept Mail Order Telephone Order (MOTO) payments with ourauthorize,migrateCardOnFileAuthorizeandmigrateCardOnFileSaleendpoints.

You can now customize thecaret colorin 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.

You can now verify the accounts of your US-based customers with ourACH verificationservice.

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.

Sending shipping address details is now optional inPayPal sale request.

Sending the cardholder name is now optional in3DS authentication request.

You now have the option to submit the CVC in the one-time and card on fileverification requests with a token.

Providing the CVC value can improve the verification acceptance rate.

You now have the option to send the browser language and IP address details of your customer's device in the authentication request for our3DS Web APIand ourAndroid-iOS SDKs.

In case of unsuccessful device data collection, providing these values increases the chances of successful authentication.

You can now submit your riskProfile to ourcard on file (with verification)endpoint in your payment requests. You then receive an exemption result and reason in the response.

Use it to apply theSCA exemptionin the payment request and update theFraudSightdata model to benefit future payments.

You can now supply storedCredentials.reason as an optional field in thecardOnFile intelligent verification requestanddynamicCardOnFile verification request.

This optional field in the verification request allows you to indicate the reason for merchant initiated transactions using stored credentials.

Swift package managersupport is now available for our iOS SDK version 2.4.0 onwards.

You can now takepartial refundsfor iDEAL payments.

You can now takepartial refundsfor PayPal payments.

We have updated the refund request URI for you to process thefull refundfor iDEAL payments.

You can now take payments usingiDEAL.

You can now take payments usingPayPal.

• 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.

• 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.

• In version 1, we now create a unverified token href in case of account verification failure as part of the"not verified" token response.

We have added anintegration example using a React.js applicationto our Web SDK documentation.

We have added a feature allowing you toremove the Web SDKfrom a page.

Version 3 is introduced to successfully process entity based billing. You must now supply the new mandatory field merchant.entity in yourcreate token request.

We have added anintegration example using a Vue.js applicationto our Web SDK documentation.

You can now use our card/networkToken paymentInstrument in our`payments:migrateCardOnFileSaleendpoint.

A network token uses a 16-digit token number, provided by the schemes, to replace an original card number.

You can now submit the scheme reference in yourmigrateCardOnFile tokenandmigrateCardOnFileSale tokenrequests.

This request parameter allows you to take a repeat payment with our APIs, linking to an agreement established with a different PSP.

You can now use PAN formatting for ourAndroid,iOSandWebSDK. The card number formats as the customer types when you implement this feature.

You can now make apayout to a wallet.

You can now take payments usingCanadian Electronic Funds Transfer (EFT).

You now receive an exemption result result and reason in yourauthorization responseif you have provided a riskProfile in your request.

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.

You now receive a verificationFailed result in yourauthorization responseif the issuer identifies a conflict.

You now have the option to supply a narrative in yourverified token request, allowing your customers to clearly see where the verified token request is coming from and helping to avoid confusion.

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 ourandroidandiOSSDK.

Sending the cardholder name is now optional for ourPayments,VerificationsandPayouts service. Whilst we still recommend that you send this information, you now have the option to omit it.

Control the cards you want to accept on your checkout form with ourcard brand configuration featurefor our Checkout Web SDK.

We’ve made the statement narrative element for ourVerification serviceoptional. This now defaults to ‘Active Card Check’ if you don’t supply a narrative.

Send funds to your customers' Apple Pay accounts using ourApple Pay decrypted payment instrument for Payouts.

We have released a new version of the iOS SDK - 2.1.0. This version allows for UITextFields in thevalidation feature.

Use the decrypted model forApple Pay Merchant Initiated Transactionsto submit a payment request using Network Token details – useful if you’re using tokens across multiple providers.

Use thedecrypted modelfor Apple Pay to verify accounts and submit a payment request using Network Token details – useful if you’re using tokens across multiple providers.

We’ve created a newAPM (Alternative Payment Methods) sectionin 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 forACH, also known as eCheck payments – a popular credit transfer and Direct Debit payment method for our US customers.

Use the decrypted model forApple Pay Customer Initiated Transactionsto submit a payment request using Network Token details – useful if you’re using tokens across multiple providers

Set youraccessibility configurationto set the language of an element for screen readers and help ensure your checkout meets an AA rating againstWCAG standards.

Use clear form on ourCheckout Web SDKto input multiple sets of card details without reloading the SDK.

The lifespan of the CVC session for ourCheckout SDKhas increased to 15 minutes, giving you longer to take a payment.

You now submit your customer's billing address details in yourrequests for Mobile Wallet payments.

You now get AVS results returned in ourresponses for Mobile Wallet payments. This helps your business understand risk factors where your customer’s AVS is unchecked, unmatched, or unsupplied.

We’ve included instructions on how to query card network tokens in ourTokens documentation– 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.

We’ve released Version 3 of ourVerified Tokens service, helping you analyse transactions with card data returned in our Verified Token responses.

You can nowcreate a CVC sessionfor 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.

You must now submit narrative in yourintelligentanddynamicverification requests.

Our newTokens version 2API gives you improved analytics – returning the BIN and card brand extra data alongside the token content.

You can now submit the scheme reference in yourrepeat payment requests. This allows you to take a repeat payment with our APIs, linking to an agreement established with a different PSP.

We have introduced a new error for invalid card numbers and have changed the formatting of all our error messages within the3DS service. 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.

We'll now send you acancel linkfor a partially settled payment to let you release funds.

Version 3 introduces updates to the merchant response. The curies array block now only lives inside the _links JSON block.

The curies array block has been updated to live inside the _links JSON block as well as outside.

You can now accept + as a character in the transactionReference field. Clickhereto see more information on our formatting rules.