June 2025 [provider-action-mappings]

Recent Fixes to Provider Integrations

Worldpay (Vantiv) Token Handling
Issue:
Leading zeros in tokens returned from Worldpay (e.g., 032542025294343) were being dropped during storage, resulting in mismatches.
Fix:
Tokens are now treated as strings instead of numbers, preserving leading zeros during tokenization.
https://developer.authvia.com/v3.3/reference/payments-token-vantiv-creditcard

Infobip RCS Integration
Issue:
Infobip required a custom mapping to be compatible with Authvia’s RCS messaging infrastructure.
Fix:
Custom RCS mappings implemented to fully support Infobip as an RCS provider.
https://developer.authvia.com/v3.3/reference/messaging-rcs-infobip-rcs

Maverick Gateway – Void & Refund Support
Issue:
Void and refund operations were not supported in the Maverick credit card gateway, limiting post-transaction capabilities.
Fix:
Void and refund functionality added, supporting the full transaction lifecycle.
https://developer.authvia.com/v3.3/reference/payments-creditcard-maverick

Fluidpay – Missing countryCode in Credit Card Mapping
Issue:
The countryCode was not being properly sent during credit card mapping, risking data mismatches.
Fix:
Mapping now correctly uses the countryCode from the PaymentMethod object.
https://developer.authvia.com/v3.3/reference/payments-token-fluidpay

PNC – Missing State Field in Tokenization
Issue:
The state field was sometimes missing in tokenization payloads.
Fix:
Defaulted to CA (California) if no state is provided by the PNC gateway.
https://developer.authvia.com/v3.3/reference/payouts-token-pnc

PNC – Lowercase state Value Causing Mapping Issues
Issue:
PNC returns the state in lowercase, but the system expected uppercase.
Fix:
Tokenization mapping was updated to handle lowercase state values appropriately.
https://developer.authvia.com/v3.3/reference/payouts-token-pnc