Changelog – Release 85

API Enhancements:

• Unified error summary details messages

Implemented a unified structure for error summary as documented in API Documentation. Potential impact on those customers processing the response for the endpoints below where the structure will change.

AS-IS:

Code Block
"error_summary": { "message": "Invalid Transaction Details", "code": "invalid_transaction_details", "details": { "messages": [ { "gateway_specific_code": "9", "gateway_specific_description": "Invalid PIN", "description": "Invalid Transaction Details", "status_code": null, "status_code_description": null } ] } }

TO-BE:

Code Block
"error_summary": { "message": "Invalid Transaction Details", "code": "invalid_transaction_details", "details": { "gateway_specific_code": "9", "gateway_specific_description": "Invalid PIN", "messages": [ "Invalid Transaction Details" ] } }

• Create charge
  • POST /v1/charges
    • Using vault-token with fraud object in request body
    • Using customer from gateway (ref_token)
    • Process charge with pre-auth 3DS (for TillPayments gateway)
    • Using OTT (for TillPayments gateway)
• Get balance
  • POST /v1/charges/balance
• Standalone refund
  • POST /v1/charges/refunds
• Verification
  • POST /v1/charges/verification
• Dynamic pricing
  • POST /v1/charges/dynamic-pricing
• Standalone 3DS
  • POST /v1/charges/standalone-3ds
• Pre-auth 3DS (using vault token)
  • POST /v1/charges/3ds
• Finalize and decline fraud charge in status inreview
  • POST /v1/charges/:id/process
  • POST /v1/charges/:id/decline
• Create OTT (VisaSRC)
  • POST /v1/payment_sources/tokens
• Gateway account
  • POST /v1/gateways/:gateway_id/accounts
  • POST /v1/gateways/:gateway_id/accounts/:id
• Customers
  • POST /v1/customers – only for creating a customer with payment destination (body.payment_destination)
  • POST /v1/customers/:id – only for updating a customer with payment destination (body.payment_destination or body.default_payment_destination)
• Customer payment source
  • POST /v1/customers/:_id/payment_sources/:_payment_source_id/verify – verify customer payment source
• Services
  • POST /v1/services/:id/verify – update service credentials (only for service.group = 3ds)
  • POST /v1/services/:id/generate-access
• Transfers
  • POST /v1/transfers/:id/capture

Impacted Functionality: Error messages

• Increased key maximum expiration from 90 days to 1 year for “global” scope

Changed maximum expiration date for all keys from 90 days to 1 year for “global” scope.

Impacted Functionality: Keys

• Blocked the exchange of Click to Pay OTT into permanent vault tokens, customers, and subscriptions

Blocked the exchange of Click to Pay OTT into permanent Vault tokens, customers, and subscriptions flows. This is to ensure customers do not use the Click to Pay OTT (FPAN/Card scheme token), intended for one-off payments, for recurring payments.

Impacted Functionality: Click to Pay, Customer & Subscription

Widget Enhancements:

• Enhanced the Click to Pay Android OTP screen experience

Introduced a fix for the Click to Pay OTP screen to ensure proper alignment of information when a user switches the OTP receipt channel from Email to Mobile.

Impacted Functionality: Click to Pay

UI Enhancements:

• Enhanced “Signup” page flow with clarifying details

Improved the “Signup” page by adding a text reminder to indicate that users are in the signup flow, not the sign-in flow. We have also introduced the ability to return to the previous step for better user experience.

Impacted Functionality: Sign-up flow, Frontend

• Updated the text for File Settings → Quotes information icon in the Request Report functionality

Changed text for File Settings → Quotes information icon in the Request Report functionality from “When enabled, the quotes will be added to the field values in the report” to “When enabled, quotes (“) will be added to the start and end of each value in the report. Please enable this option if you expect delimiters to be populated in the report values to prevent interference with file formatting” to make it more descriptive and clear for merchants.

Impacted Functionality: Reporting