Release notes - RapydGateway

Release Version	Release Date	Summary
2.68	2026-11-09	The WalletPayment endpoint accepts a new authorizationCode field. It is required on merchant-initiated incremental and reauthorization subsequent transactions The PushFunds error for an invalid sponsoredMerchantData.countrySubdivisionCode now says 1 to 3 alphanumeric characters, matching the rule Documentation: the Content-Type: application/json header is listed as required, the sponsoredMerchantData field formats are published, an incremental amount is added to the existing authorization, CreateVirtualCard's transactionLinkId is 22 characters, and the obsolete outOfScaScope is no longer shown (responses still carry it) Documentation: CardPayment and WalletPayment no longer say that subsequent transactions must use the Sale operation, and sponsoredMerchantData.merchantId is described as the payment facilitator's own identifier
2.67	2026-11-06	The CardInformation endpoint returns cardBinDetails.isDccEligible as true or false, never null. It is false when DCC eligibility isn't known
2.66	2026-11-03	The CardInformation endpoint now returns two new fields in cardBinDetails: cardholderBillingCurrency and isDccEligible. For Visa cards, billingCurrency keeps returning the issuer country The CardPayment, VirtualCardPayment, PushFunds, PullFunds and WalletPayment endpoints accept two new optional fields: transDate (MMDD) and transTime (hhmmss) Address fields that exceed the scheme limit are now truncated instead of rejected: senderData.streetAddress on PushFunds and PullFunds, addressVerificationData.streetAddress and postalCode on CardPayment, and sponsoredMerchantData streetAddress, cityName, cityOrPhoneNumber and postCode When the issuer rejects a 3D Secure authentication, responseDescription now starts with the issuer's reason. The correlation ID is still included A CreateVirtualCard retry with the same 3D Secure transaction after a timeout is no longer rejected as a duplicate
2.65	2026-10-29	The cardPresentData.cardSequenceNumber field is now optional for contactless and chip card payments. When sent, it must be up to 3 digits The PullFunds specialConditionIndicator field now also accepts CBDC, Stablecoin and Blockchain An OTI void for a payment that has already been voided, or that already has a void in progress, is now refused Documentation of the PushFunds data required for cross-border transactions to New Zealand, Australia and Saudi Arabia
2.64	2026-09-17	Updated refund fallback mechanism for internal use only
2.62	2026-05-20	The Visa CVV2 result code definitions for the CardVR parameter have been updated in line with Visa's Field 44.10 redefinition The ValitorPay endpoint GetVirtualCardData now provides the fields cardNumber, trid, initiator, initiatorReason, tavv, and transactionLinkId in the response A new walletPaymentData object has been added to the Card Payment endpoint. This object contains the fields walletPaymentType, paymentCryptogram, and eci The PullFunds endpoint now truncates the SenderData.City field instead of rejecting requests that exceed the maximum length The CAVR value is now returned in the response for the CardPayment and WalletPayment endpoints A new binInformation object is now returned in the response for the CardPayment and WalletPayment endpoints The lastFourInPan field is now returned in the response for the CardPayment and WalletPayment endpoints for token transactions A new DecryptWalletToken endpoint is now available that decrypts Apple Pay and Google Pay payment tokens and returns the decrypted card data The CreateVirtualCard endpoint has been extended to accept two new optional input fields: transactionLifecycleId and transactionLinkId
2.61	2026-03-26	Support messageId on Card Payments. Added a new optional messageId field to the Card Payment endpoint. Include submerchantId when querying Push Funds. Create dedicated consumer for reversals. Implemented a new MassTransit consumer to handle IPerformReversal messages directly within ValitorPay. New field for Tax ID for sponsored merchants from France, Belgium and Luxemburg. Masked personal data and virtual card numbers in PushFunds / PullFunds logs Documentation improvements regarding cardholder billing currency support Improved mdStatus field documentation. Relaxed ICC data requirement for card-present refunds
2.60	2026-02-18	The PushFunds endpoint now provides the acquirerReferenceNumber in the response in ValitorPay The cardPresentData object now validates the pinBlock fields for incoming transactions ValitorPay now blocks all BGN currency requests sent after February 28th, 2026 The messageId is provided in direct refund emergency reversals The CardVerification callback now provides the callbackSource property The CardCheck payment operation no longer requires the cvc field when transactionType is MailOrder
2.59	2026-01-22	The DirectRefund and DirectReversal endpoints now provide additional logging of incoming requests in ValitorPay The WalletPayment and PullFunds endpoints now support the scaExemption parameter The cardPresentData object now provides the parameters terminalCapability, terminalPinEntryCapability and terminalType under the terminalData object The RefundWithCorrelationId endpoint now provides the parameters agreementNumber and terminalId. These parameters are used to retrieve partnerId It is now possible to provide eci through the walletPaymentData object in the PullFunds endpoint The PullFunds endpoint now provides the parameters streetAddress, city, postCode and countrySubdivisionCode in the recipientData object for VISA cross‑border transactions into and out of Canada and the USA The validation of the cardPresentData object has been updated so that required, optional and not‑required fields are validated according to the transaction type for Sale and Auth operations
2.58	2025-12-17	In CardPayment single tap fields added in the cardpresentData object A new parameter 3DSMessageVersion added under the cardVerificationData object in CardPayment, VirtualCardPayment and PullFunds 3DSMessageVersion added in the CardVerificationResponse AFT (PullFunds), new required fields added to support tokendata Validation added for TripLedDepartureDate
2.57	2025-11-20	In case of duplicate correlationId, the response code is returned in the validation error response It is now possible to send only cardholderName through the cardholderData object in the CardVerification endpoint Reduced browserData->language restrictions in the CardVerification endpoint The parameter merchantReferenceData is now supported for RefundWithCorrelationId It is now possible to provide softPosInformation through the cardPresentData object in the CardPayment endpoint The marketplaceId and foreignIndicator have been moved to the schemeData object. Marketplace object has been deprecated
2.56	2025-10-13	The CardPayment, VirtualCardPayment, WalletPayment, PullFunds and PushFunds endpoints now provide the parameters rampProviderID under the SchemeData object The recipientData->firstName and recipientData->lastName parameters in the PullFunds and PushFunds endpoints are required for all VISA transactions The CardVerification endpoint now returns cardholderInfo in the response The CardPayment and WalletPayment endpoints now provide the parameter amexSellerId in the SponsoredMerchantDataEnhanced object The airlineData->passengerName parameter has been updated to include more information regarding format and length for Amex transactions
2.55	2025-09-18	DirectPurchaseOfLiquidAssetsOrQuasiCash is now supported as a transactionType in the PullFunds endpoint HighRiskSecurities is now supported as a transactionPurpose in the PullFunds endpoint The CardVerification endpoint now provides the parameter merchantAmexSEID under the ThreeDs2XGeneralExtraFields object The sponsoredMerchantData->emailAddress parameter in the CardPayment, VirtualCardPayment and WalletPayment endpoints is required for American Express transactions In case when a PP-P response is received in the VirtualCardPayment and WalletPayment endpoints response, the transaction is reversed
2.54	2025-08-28	The CardVerification endpoint now provides the parameter merchantReferenceData in the CardVerificationAdditionalData object The GetDccOffer endpoint now returns responseCode and responseDescription in the response The CardPayment, VirtualCardPayment and WalletPayment endpoints now provide the parameter merchantAmexSEID under the PaymentSchemeData object Added documentation for the authType returned in the CardVerification callback In case when a PP-P response is received in the CardPayment endpoint response, the transaction is reversed
2.53	2025-06-23	Users may now provide emailAddress within sponsoredMerchantData in requests TaxRefunds is now supported as a transactionType in the PushFunds endpoint The PushFunds and PullFunds endpoints now provide the parameters streetAddress, cityName, countrySubdivisionCode, countryCode, postCode under the paymentFacilitatorData object The fields merchantData->merchantState and merchantData->merchantCounty in the PushFunds endpoint have been deprecated along with the whole PushFundsMerchantData object It is now possible to calculate the dcc offer through the GetDccOffer endpoint The CardPayment, VirtualCardPayment and WalletPayment endpoints now provide the parameters originalTransactionAmount, originalTransactionCurrency, scaleFactorExchangeRate, scaleFactorMarkupRate under the AdditionalData->DccInfo object
2.52	2025-05-27	It is now possible to correctly pass a currency value with a leading zero (if needed) through the applePayWalletPayment/decryptedPaymentTokenData object in the WalletPayment endpoint To ensure consistency with PushFunds, the sender Date of Birth format in PullFunds has now been changed from YYYYMMDD to YYYY-MM-DD
2.51	2025-04-07	Various documentation updates
2.50	2025-03-26	The PushFunds and PullFunds endpoints now provide the parameters dateOfBirth, occupation, birthCountry, nationality, emailAddress under the SenderData object and personalEmail under the RecipientData object The parameter amount is now supported for RefundWithCorrelationId. This allows the user to do a partial refund if an amount is provided The parameters amount and currency are now supported in the WalletPayment endpoint The CardVerification endpoint now returns authorizationType in the response Various documentation updates
2.49	2025-02-19	A list of country subdivisions may be found in the relevant endpoints under sponsoredMerchantData->countrySubdivisionCode The CreateVirtualCard endpoint now returns the cardholderRelatedDataResult Various documentation updates
2.48	2025-01-08	The CardVerification endpoint now returns transStatus in the response The sponsoredMerchantData->addressLine parameter in the PushFunds endpoint has been deprecated. Please use the sponsoredMerchantData->streetAddress parameter instead The CardPayment endpoint now returns cardPresentData->iccData in the response when appropriate Various documentation updates
2.47	2024-12-05	VirtualCardPayment and PushFunds endpoints now contain authorizationIdentifier in the response The CardInformation endpoint now provides the parameters fasterFunds, fundsDisbursementEnabled and moneyTransfer in the cardBinDetails object of the response It is now possible to provide card present data through the cardPresentData object in the CardPayment endpoint. Card present transaction types have also been added Various documentation updates
2.46	2024-10-30	Payment Facilitators are now able to provide all acceptor location data under the sponsoredMerchantData object The parameter sourceOfFunds is now supported for PushFunds Added support for Transaction Link Data - currently only available for Mastercard The parameter cardHolderData->email in the CardVerification endpoint is now validated for a proper email address Various documentation updates
2.45	2024-09-26	Independent Sales Organizations (ISO) are now able to provide their isoId as an input parameter under the schemeData object Payroll is now supported as a transactionType in the PushFunds endpoint The accepted currencies for Amex are: ISK, EUR, USD and GBP Various documentation updates
2.44	2024-08-19	Payment Facilitators are now able to provide their Payment Facilitator Id to the schemes in the field schemeData->PaymentFacilitatorId It is now possible to make multiple captures when using authType->PreAuthorization Multiple documentation and example updates
2.43	2024-07-16	Unsupported card types will now return an error message to the user The timeout value of the CardPayment endpoint has been reduced from 100 seconds to 30 seconds Various technical improvements
2.42	2024-06-20	The parameter eci is now available in the CardVerification response message as part of the frictionlessData object The parameter transStatusReason is now available in the CardVerification response message Links to the Implementation Guide from the API have been updated
2.41	2024-05-13	Refund with correlationID examples have been added to the Implementation Guide CardVerification example card numbers have been updated in the API Multiple documentation and example updates
2.40	2024-04-11	Merchants are now able to provide their own MessageID through the field acquirerReferenceNumber in CardPayment and WalletPayment endpoints when the operation is either Sale or Auth
2.39	2024-04-05	Merchant Advice Codes are now available in the GetBatchReport response CardholderRelatedData can now be supplied in cases where the merchant wants to use Account Name Inquiry Various documentation improvements
2.38	2024-03-21	Payment Account Reference (PAR) is now available in the transactionReports of GetBatchReport The WhenToClear parameter has been updated to include more information regarding when this value will be used The authorization expiry date is now available in the response for CardPayment, VirtualCardPayment and WalletPayment Partial authorizations are now supported for PullFunds AuthorizationIdentifier is now available in PullFunds response Updated examples for Google Pay payments Various documentation updates
2.37	2024-03-11	Changes to the mandatory fields in 3DSecure (only one phone number OR email address is required and cardholder billing address information is no longer required but highly recommended) Full merchant reference data may now be provided in Create virtual card payment batch Card VR (CVC validity) is now available in the response for Card payment, Pull Funds, and Create virtual card MerchantCountryOfOrigin no longer accepts numerical values
2.36	2024-03-01	Regular software updates
2.35	2024-02-20	Users may now provide merchantCountryOfOrigin within sponsoredMerchantData in requests PAR is now being provided in all responses when it is provided from the issuer
2.34	2024-01-31	Merchants may now indicate if a PullFunds transaction is related to cryptocurrency using the SpecialConditionIndicator. Merchants may now provide the Electronic Commerce Indicator (ECI) received when decrypting the payment token in WalletPayments. The ECI is now provided in WalletPayment, CardPayment and VirtualCardPayment responses.
2.33	2024-01-19	Any updated masked card numbers are now available in the batch report as updatedMaskedCardNumber. The transaction ID of the original transaction is now available in the Refund response as OriginalTransactionID.
2.32	2023-12-13	Masked token data is now available in the GetBatchReport response (when available) Cardholder data, billing data and browser data became mandatory in the CardVerification endpoint Zero amount transactions are now possible in the WalletPayment endpoint Added support for sending URLs within the MerchantReferenceData Updated examples for Apple Pay/Google Pay payments, PullFunds and Refund with Correlation ID are now available The BinRange endpoint has become deprecated and is no longer supported
2.31	2023-11-09	Marketplace support added Masked schema token displayed in responses Making refund with correlationId possible CardCheck feature in card payment
2.30	2023-10-18	Marketplace support added Masked schema token displayed in responses Making refund with correlationId possible CardCheck feature in card payment
2.29	2023-09-28	Pull funds added SCA exemptions changed
2.28	2023-09-13	Remove version 1.0 Some small bugfixes
2.27	2023-08-29	Improve Push funds Google Pay - new parameter to return decrypted token without payment Improve first/subsequent transaction in Walletpayment Return MerchantAdviceCode and MerchantAdviseDescription in payment endpoints Specifications improvements
2.26	2023-07-20	Address verification data added to CardPayment Allow 1-8 digits in TriplegInformation/Array/FareBasisCode Remove Xid from CardVerificationdata Display response code information
2.25	2023-07-04	Remove restrictions for MailOrder and TelephoneOrder trans types Add sponsored Merchant data to Push Funds Support First transaction in MTP WalletPayment Add the field tripLegDepartureDate to Airlinedata Let Merchant know if refund operation was performed as refund or reversal Add required information to Mastercard Pushfunds endpoint