Navigate to...

Error Codes

Custom Error Handling

Visa Accept Service B2B APIs use custom error codes and error responses in addition to standard Visa Developer Platform error codes. These APIs include product-specific error codes for business logic validation, seller name tag conflicts, and detailed field-level validation errors that identify the location of invalid data.

Standard Visa Developer Platform Error Codes

For common HTTP status codes and standard Visa Developer Platform error codes, see:

Visa Developer Error Codes

Product-Specific Error Codes

The following error codes are specific to Visa Accept Service B2B APIs and relate to business logic and validation rules enforced by the service.

Business Logic Error Codes

Error Code	Description	Cause	Resolution
`VABSVC_00001`	Message validation failed	Required fields are missing or request data is in an invalid format	Review field-level validation errors and correct the request data
`VABSVC_00002`	Technical support contact required	System-level error that requires technical assistance	Contact technical support and provide the correlation ID and error details
`VABSOBS_00008`	Seller name tag conflict	The requested seller name tag already exists	Select an alternative seller name tag or use a suggested value returned in the response

HTTP Status Code Errors

The Visa Accept Service B2B APIs may also return specific HTTP status codes to indicate request conflicts or processing errors.

HTTP Status Code Examples

HTTP Status	Description	Cause	Resolution
`HTTP 409`	Duplicate seller enrollment	An attempt was made to enroll a seller with an existing identifier	Use `REOPEN` as the enrollment type or verify seller uniqueness before retrying

Error Response Format

Error responses returned by Visa Accept Service B2B APIs include detailed information that helps identify the cause of the failure and any invalid fields.

{
        "errorMessage": "error-description",
        "correlationId": "unique-tracking-id",
        "requestId": "specific-request-identifier",
        "fieldErrors": [
        {
        "field": "field-location-path",
        "error": "specific-validation-error"
        }
        ]
        }

Common Integration Issues

Issue: Transaction timing errors

Typical error: HTTP 400 returned due to seller status validation failure
Cause: Payment or refund requests are sent before the seller is fully onboarded and activated
Solution: Verify that the seller status is ACTIVE using GET /sellers/{sellerId} before processing transactions

Issue: Reference management errors

Typical error: VABSVC_00001 returned due to a missing transaction reference
Cause: Original transaction identifiers are not retained for refund operations
Solution: Store transaction IDs returned in successful payment responses and reuse them for refunds

Error Handling Best Practices

Follow these best practices when handling errors returned by Visa Accept Service B2B APIs:

Use correlation IDs: Include correlation IDs when reporting errors for troubleshooting and monitoring
Implement retry logic: For 5xx system errors, apply retries with exponential backoff
Validate before processing: Confirm seller status and validate request data before transaction processing
Handle field-level errors: Use field validation details to guide corrective actions