Skip to login Skip to content
Developer Cybersource Logo

Getting started

Find tailored resources to kickstart your integration

API Reference

Use our live console to test and start building with our APIs

 

Accept payments

Online or In-person payment acceptance made easy

Technology partners

Register to get onboard our sandbox environment as a Tech partner or explore our pre-built integrations

Resources

Create seamless scalable payment experiences with interactive tools and detailed documentation

Documentation hub

Explore developer guides and best practices for integration with our platform

SDKs

Get pre-built samples to build or customize your integrations to fit your business needs

Demo hub

Access to variety of our product demos 

Testing

Signup for sandbox and use testing resources before going live

Sandbox signup

Create a sandbox to test our APIs

 

Testing guide

Guide with sandbox testing instructions and processor specific testing trigger data

Response codes

Understand all different error codes that REST API responds with

Support

Find resources and guidance to build, test, and deploy on our platform

Frequently asked questions

Find answers to commonly-asked questions about our APIs and platform

Contact us

Connect with our team of experts to troubleshoot or go-live to Production

Developer community

Connect and share with community of developers 

 

AI Assistant

Menu
  • Release Notes
  • Announcements
    • Important: SCMP Now Requires HTTPS
    • Important: SOAP Toolkit Update for Java Users
    • Important: SOAP Toolkit Update for C++ Users
    • Important: SOAP Toolkit Update for C# Users
    • Important: SOAP Toolkit Update for PHP Users
  • Features Introduced This Week
  • Fixed Issues
  • Known Issues

Known Issues

  • Release Notes
  • Announcements
    • Important: SCMP Now Requires HTTPS
      • HTTPS with Java Clients
        • Update JDK Properties
      • HTTPS with Non-Java Clients
        • Enable SCMP to Simple Order Conversions for Non-Java Clients
    • Important: SOAP Toolkit Update for Java Users
      • Java
    • Important: SOAP Toolkit Update for C++ Users
      • C++
    • Important: SOAP Toolkit Update for C# Users
      • C#
    • Important: SOAP Toolkit Update for PHP Users
      • PHP
  • Features Introduced This Week
  • Fixed Issues
  • Known Issues
On This Page
  • Payments | EPS-30813Transaction Search | EPS-31026Reporting | EPS-31014Payments | EPS-30773Payments | EPS-30820REST API | EPS-30637Invoicing | EPS-30538Payment | EPS-30491API Testing | EPS-30041Business Center | EPS-30657Reporting | EPS-30677Merchant Boarding | EPS-30718Payments | EPS-30784Transaction Search and Details | EPS-30810

Payments
| EPS-30813

Description
If a debt recovery transaction's
networkTransactionId
field has any spaces, it fails with the error
Invalid field: subsequent_auth_transaction_id
.
Audience
Merchants who offer the Discover card.
Technical Details
None.
Workaround
None.

Transaction Search
| EPS-31026

Description
Portfolio accounts that use Transaction Search in the Business Center are experiencing intermittent slowdown and occasional timeouts.
Audience
Portfolio account users.
Technical Details
No.
Workaround
No.

Reporting
| EPS-31014

Description
When a reseller account and its subordinate merchant account generate the Billable Transaction Detail Report, there is sometimes a mismatch between the two reports.
Audience
Resellers and subordinate merchants who use the Billable Transaction Detail Report.
Technical Details
None.
Workaround
None.

Payments
| EPS-30773

Description
Voided transactions performed soon after the batching time might still be batched, despite receiving confirmation that the void occurred in the API Response.
Audience
Merchants using Visa Platform Connect and GPX processors for payment transactions.
Technical Details
Merchants should see the error DNOTVOIDABLE rather than SOK when the void call was performed close to the daily set batching time.
Workaround
Perform void calls before the set batching time setup for your merchant ID during the boarding of your account to prevent any overlap.

Payments
| EPS-30820

Description
An intermittent DINVALIDATA error is sometimes returned in the
ics_bill
(settlement) call rather than during the
ics_auth
(authorization) call.
Audience
Merchants who use Visa Platform Connect for payment transactions.
Technical Details
None.
Workaround
If this scenario occurs, perform an authorization reversal to remove the ring fencing of the funds induced by the generation of the authorization code by the issuer. Prompt your customer to enter a valid value based on our documented validations. The addition of restrictions in your checkout page will also assist in preventing this scenario.

REST API
| EPS-30637

Description
A defect is causing the
consumerAuthenticationInformation.token
field to be returned in the
processorInformation
object instead of the
consumerAuthentication
object.
Audience
Merchants using the REST API.
Technical Details
None.
Workaround
None.

Invoicing
| EPS-30538

Description
When an invoice has been partially paid at least once, the remaining balance provided within the webhook response might not return a correct value.
Audience
Merchants using invoicing.
Technical Details
None.
Workaround
Real-time data is available in the Business Center's Invoicing and Reporting pages to help you track the payment status of orders processed using invoicing.

Payment
| EPS-30491

Description
Merchants using digital payments such as Apple Pay and Google Pay, in conjunction with Discover or Diners Club cards will see the following error:
DINVALIDDATA "Unsupported ECI type. e_commerce_indicator=DIPB"
.
Audience
Merchants processing Discover or Diners Club card transactions using Vantiv on Visa Platform Connect.
Technical Details
Our implementation with Vantiv is preventing the usage of the
e_commerce_indicator
value
dipb
, indicating the passing of a cryptogram from an authenticated transaction.
Workaround
You can replace the value
dipb
with the value
internet
to bypass the current validation. However, you risk losing the liability shift and incurring increased rejections downstream.

API Testing
| EPS-30041

Description
The API testing trigger 5001.00, which tests AVS response codes, is not producing the correct responses for Discover cards.
Audience
Global.
Technical Details
The test amount of 5001.00 should trigger a processor response of
processorInformation.avs.code=Y
. Instead, it is returning
processorInformation.avs.code=A
.
Workaround
None.

Business Center
| EPS-30657

Description
Some users logging into the Business Center's testing environment are not receiving the One-Time Password if it is sent using SMS.
Audience
Users of the Business Center's testing environment.
Technical Details
None.
Workaround
You can use email instead of SMS.

Reporting
|
EPS-30677

Description
When you use the REST API
GET reporting/v3/reports
request to query the
reportName
parameter, and the length of the report name is too long, the affected report is not returned in the response.
If the query parameter
reportName
is not specified, then it does successfully return the report details.
Audience
Users of the Reporting REST API.
Technical Details
None.
Workaround
Merchants can omit the
reportName
query parameter in the API call or recreate the report with a shorter name.

Merchant Boarding
| EPS-30718

Description
Resellers are currently unable to enable Secure Acceptance for new merchant accounts.
Audience
Resellers.
Technical Details
None.
Workaround
None.

Payments
|
EPS-30784

Description
An intermittent error sometimes prevents transactions from being recorded in the Business Center even though a response was received by the merchants. In some cases, this can result in the cardholder being charged twice.
Audience
Merchants using the Cielo and Rede processors in Latin America.
Technical Details
None.
Workaround
None.

Transaction Search and Details
|
EPS-30810

Description
Some resellers are experiencing slow loading or timeouts in the Business Center's testing environment when using the Transaction Search and Transaction Details pages.
Audience
Resellers.
Technical Details
None.
Workaround
None.
Back to top

Visa

Cybersource.com

Terms + conditions

Cookie policy

Privacy notice

Your privacy rights

© 2024 Cybersource. All rights reserved. All brand names and logos are the property of their respective owners, are used for identification purposes only, and do not imply product endorsement or affiliation with Cybersource.