- iFrame
- Portal
- Payment Services v2
iFrame
17183 - BUG - nToken Scheme Validation Fix
- Updated the iFrame to validate each token scheme according to their own specification, which will make nToken have a minimum length of 4, and maximum length of 38 characters.
Portal
17093 - Add toggle to Portal to enable IP only authentication for Proxy Requests
- Customer can by pass (Proxy) API key validation by enabling the APIKeyBypass toggle on the proxy tokenization page in customer portal.
Payment Services v2
17093 - Standardize Orbital Stored Credentials
- Brought
StoredCredentials
usage into a standard. AnymitMessageType
can be sent through theStoredCredentials.TransactionType
fieldStoredCredentials.Initiator
now accepts "merchant" or "cardholder" instead of themitMessageType. StoredCredentials.Initiator
,StoredCredentials.CredentialStored
, andStoredCredentials.TransactionType
are now used to deduce the appropriatemitMessageType
(with some exceptions) as detailed in the TokenEx Orbital documentation.
17013 - SafeCharge/Nuvei Soft Descriptor Field Implementation
- Clients can now utilize the standard
SoftDescriptors
object to populate Safecharge/Nuvei's DynamicDescriptor fields. This change is backwards compatible with the oldDynamicDescriptors
object, however theSoftDescriptors
will take precedent if both are populated in the request.
17014 - Stripe Soft Descriptor Field Implementation
- We have added a new object to for users to provide
SoftDescriptors
. There are two existing fieldsstatementDescriptor
andstatementDescriptorSuffix
. Users can provide these values viaSoftDescriptors
object withsoftDescriptors.Descriptor
andsoftDescriptors.DescriptorSuffix
. Users can provide these values via existing and new parameters but If there is a value in newSoftDescriptors
object, however will take precedent if both are populated in the request.
17084 - Object reference error when ServiceUnavailable
response received from Payeezy
- Fixed an issue with Payeezy where an error was thrown instead of returning gracefully upon receiving a 503 error from the gateway.