RM-31868

Description
The Worldline (SIX) processing connection is updated to support multiple partial captures for a single authorization.
Audience
Merchants processing on the Worldline (SIX) gateway in the EU.
Benefit
Merchants can support split shipments and capture for individual items as they are shipped.
Technical Details
Merchants who wish to support multiple partial captures should follow the guidance for multiple partial capture processing in the SIX developer guide. Merchants must update their capture processing to include the following additional fields:
Sequence
REST API Field:
processingInformation.captureOptions.captureSequenceNumber
SCMP API Field:
capture_sequence
Simple Order API Field:
ccCaptureService_sequence
Total Count
REST API Field:
processingInformation.captureOptions.totalCaptureCount
SCMP API Field:
capture_total_count
Simple Order API Field:
ccCaptureService_totalCount
Important Dates
Released to production October 28, 2024.

RM-32624

Description
The Elavon Americas gateway connection is updated to support:
  • 3-D Secure 2.x.
  • Payment Account Reference (PAR)
  • Surcharge
Audience
Merchants that use the Elavon Americas gateway in the US and Canada.
Benefit
The addition of new features gives merchants more choices.
Technical Details
3-D Secure
Elavon Americas supports 3D-Secure up to version 2.2, which enables the use of dynamic authentication through biometrics and token-based authentication methods. This feature enables authentications that do not require manual input from the cardholder, sometimes called frictionless flow. Version 2.2 also recognizers soft declines, which reduces the chance that a payment is declined, as well as the risk of customer abandonment.
Delegated authentication and decoupled authentication are also available. Delegated authorization allows merchants to use third-party authenticators as well as the issuing bank for payment authorizations. Decoupled authorizations allow customers to obtain an authorization on one device and complete the transaction on a second device.
Payment Account Reference (PAR)
The PAR enables merchants to find the source of funds used for payments across all payment instruments. This gives merchants more visibility into customer behavior, especially with digital wallet payments in which the customer's primary account number (PAN) is hidden behind a device primary account number (DPAN), which is tokenized version of a PAN used in mobile device payments.
The PAR value can be beneficial in the following scenarios:
Transaction source identification: this can be helpful when multiple transactions occur in a short time frame or when customers engage in recurring payments.
Fraud prevention: using the PAR value, merchants can detect and flag potentially suspicious activities more effectively.
Customer support: enables customer support to more easily retrieve and track transactions when customers call to inquire or dispute a charge, thereby facilitating a quicker customer resolution.
Personalized services: merchants can better understand their customer spending patterns and preferences. This could assist merchants to offer personalized promotions, rewards, and experiences, enhancing customer satisfaction and loyalty.
Regulatory Compliance: PANs can assist merchants in meeting regulatory requirements, such as anti-money laundering (AML) and know your customer (KYC) requirements. To include the PAR value, use the following fields:
REST API:
processorInformation.paymentAccountReferenceNumber
Simple Order API:
paymentAccountReference
Surcharge
Surcharge enables merchants to list surcharge as a separate line item for payment transactions. This feature must be enabled with the merchant's acquiring bank before it can be used. The surcharge amount will be included in the following fields:
REST API:
orderInformation.amountDetails.surcharge.amount
SOAP API:
surchargeAmount
This field value should include a decimal point between dollars and cents. For example: 5.25.
Important Dates
Released to production November 1, 2024.

RM-30007

Description
A new field,
ProviderTransactionID
, is added to the Reporting and Transaction Search features. The new field is currently available for Pix through Iugu and will later be used for future provider-specific transaction reference numbers.
Pix is an alternative payment method in the LAC region. It has been implemented and is currently in production with Iugu as the provider. This provider includes a unique identifier, the Codego ID, which is essential for merchants to reconcile and retrieve transactions. To avoid using provider-specific field names, this and future provider-specific transaction reference numbers will be contained the
ProviderTransactionID
field.
Audience
This feature is currently available to merchants using the provider Iugu in LAC.
Benefit
Enables merchants to run post-transaction services with their provider and also share the transaction information with VAP transaction data.
Technical Details
Users can add the
ProviderTransactionID
field to existing or new report subscriptions or one-time requests using the
Add Fields
button.
Important Dates
Released to production October 30, 2024.