Visa Accept Service B2B APIs

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
000001 Message validation failed Required fields are missing, request data is in an invalid format, or request parameters fail business validation rules Review field-level validation errors in the response details and correct the request data accordingly
003001 Technical support contact required A system-level error occurred that cannot be resolved by the client Contact technical support and provide the correlation ID and error details
010008 Seller name tag conflict The requested seller name tag already exists for another seller within the application Select an alternative seller name tag or use a suggested value returned in the response
010010 Seller enrollment failed An unexpected system error occurred during the seller enrollment database persistence operation Retry the enrollment request. If the error persists, contact technical support with the correlation ID
010011 Seller not found No seller profile exists for the provided seller identifier Verify the seller ID is correct and that the seller has been successfully enrolled before making this request
010014 Accept token provision failed The VTS token provisioning process failed during seller enrollment or card addition Retry the request. If the error persists, verify card eligibility and contact technical support
010019 Seller payment instrument not found No active payment instrument (PAN) record exists for the specified seller Verify the seller has an enrolled and active payment instrument before performing this operation
010020 Accept tier not found The accept tier configuration required for the seller's country or card type does not exist in the system Verify the application has a valid accept tier configured for the seller's country and card type
010021 Accept token not found No accept token exists for the specified payment instrument SID Ensure the payment instrument was fully provisioned during enrollment before referencing its token
010023 Device conflict The device is already registered with an active KIC device binding and rebind was not requested Use a different device identifier or set the rebind flag to true to re-register the existing device
010024 Invalid application ID No application configuration exists for the provided external application identifier Verify the application ID is correct and that the application has been properly onboarded
010034 Application configuration not found The requested application has no configuration values stored in the system Ensure the application has been fully onboarded and configured before querying its details
010036 Seller ID conflict A unique seller ID could not be generated due to repeated collisions with existing identifiers Retry the enrollment request. If the error persists, contact technical support
010037 Duplicate seller payment instrument The provided card number (PAN) is already enrolled under a different seller profile Use a different card for enrollment or locate the existing seller associated with this card
010045 Reopen invalid account The seller account cannot be reopened because it is not in a valid closed or suspended status Verify the seller's current status supports reopening. Only closed or suspended accounts can be reopened
010052 Failed to update combined profile The combined profile update in vabs-services failed during a seller name tag change in HYBRID integration mode Retry the request. If the error persists, contact technical support with the correlation ID
010053 Seller name tag invalid The seller name tag does not meet format requirements: must be 1-25 characters containing only letters, numbers, spaces, and allowed special characters (~ ! # $ % ^ ' & ( ) /) Provide a name tag that conforms to the character and length requirements
010055 Selected payment instrument invalid The specified primary PAN ID does not exist or its associated token is not in ACTIVE status Verify the payment instrument ID is correct and that the instrument has an active token before switching
010071 Customer already enrolled A seller with the same customer ID is already enrolled and active for this application Use the existing seller profile or use REOPEN enrollment type if the previous enrollment was closed
010077 Card not eligible The provided card number's BIN prefix is not configured as eligible for this application or issuer Verify the card is issued by a supported issuer and its BIN range is included in the application's eligible card configuration
010079 Seller application mismatch The specified seller does not belong to the application identified in the request path Verify the seller ID and application ID combination is correct. The seller must have been enrolled under the specified application
010082 VTS RTTV error The VTS Real-Time Token Verification service returned a null or incomplete response during token resolution Retry the request. If the error persists, verify the card's token status and contact technical support
010085 MCM check failed The seller name tag failed the Merchant Content Monitoring profanity or compliance check Choose a different seller name tag that does not contain restricted or inappropriate content
010087 Fintech disabled by issuer The fintech application has been disabled by the issuer for the resolved accept tier Contact the issuer to enable fintech access for the relevant tier, or use a different card associated with an enabled tier
010088 Payment instrument already enrolled The payment instrument (card) is already enrolled with an active token for this seller Use the existing enrollment or close the current card enrollment before re-enrolling
010090 Terms and conditions not accepted The fintech application configuration requires terms and conditions acceptance but the request did not include acceptance confirmation Include the terms and conditions acceptance flag in the enrollment or update request

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.

Common Integration Issues

Issue: Transaction timing errors

Issue: Reference management errors

Error Handling Best Practices

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