On This Page
Features Introduced This Week
Estimated and Incremental Authorization Support for Eligible Processing
Connections | RM-47041
Estimated and Incremental Authorization Support for Eligible Processing
Connections
| RM-47041- Description
- Cybersource now supports estimated authorizations and incremental authorizations for the FDI Global processor, enabling merchants to obtain an initial authorization for an estimated amount and increase the authorized amount when additional charges are incurred. This enhancement supports lodging, vehicle rental, cruise, healthcare, and other variable-spend industries where the final transaction amount is not known at the time of authorization. Merchants can also maintain a single authorization lifecycle that aligns with card-brand requirements for estimated and incremental authorization processing.
- Mandate
- Does not apply.
- Audience
- Merchants in North America that process transactions through FDI Global.
- Technical Details
- Merchants can identify an authorization as an estimate using processingInformation.authorizationOptions.authIndicator=0 and can increase a previously approved authorization by submitting an incremental authorization request through/pts/v2/payments/{id}orccIncrementalAuthService_run=true.Merchants can submit multiple incremental authorizations against the same original authorization while maintaining transaction linkage throughout the authorization lifecycle. This enhancement supports estimated authorization use cases such as lodging, vehicle rental, cruise, and healthcare transactions and is available for Visa, Mastercard, and Discover transactions.
- Important Dates
- Released on September 30, 2026
Additional Search Fields Added to the Transaction Search API |
RM-49264
Additional Search Fields Added to the Transaction Search API
|
RM-49264- Description
- The Transaction Search API now supports searching for transactions using additional identifiers that enable more precise transaction identification and reconciliation. Merchants can now search using a client transaction ID, airline ticket number, or passenger name.
- Mandate
- Does not apply.
- Audience
- Merchants that use the Transaction Search API and need to identify transactions using a client transaction ID, airline ticket number, or passenger name.
- Technical Details
- The Transaction Search API now supports searching for transactions using themerchant_transaction_identifier, airline ticket number, and passenger name fields. These additional search criteria help merchants identify and reconcile individual transactions more accurately when multiple transactions share similar attributes.
- Important Dates
- Released on October 1, 2026