Visa Accept Service B2B APIs

To enable seller acceptance capabilities, you must follow this specific sequence of API calls that support the seller lifecycle.

The primary business workflows include:

• Seller Enrollment and Setup: Register new sellers and configure their acceptance capabilities
• Activation of Acceptance Capabilities: Enable payment processing for enrolled sellers
• Transaction Processing: Handle sales and refunds for active sellers
• Lifecycle Management: Update seller profiles and manage account status

The workflow sequence ensures that seller onboarding and activation are completed before transaction processing begins, with transaction processing workflows depending on an active seller profile and refund workflows depending on previously processed transactions.

To enable seller acceptance capabilities, you must follow this specific sequence of API calls.

1. Application Configuration: Retrieve application settings using GET /appdetails. This determines integration mode and account policies for all subsequent operations.
2. Card Eligibility Validation: Validate payment instruments before enrollment using POST /cardeligibility. This confirms the ability to process payments for the intended card types.
3. Seller Name Tag Check: Verify seller identifier availability using GET /nametags/{sellerNameTag}. This helps prevent conflicts during enrollment.
4. Seller Enrollment: Register new sellers using POST /sellers. This creates the seller profile and returns seller ID for subsequent operations.
5. Seller Activation Confirmation: Verify seller status is ACTIVE before proceeding to transaction processing. Use GET /sellers/{sellerId} to confirm status.
6. Transaction Processing: Process payments and refunds using POST /sellers/{sellerId}/transactions. Refund transactions require original transaction ID references.

• Device Registration: For Hybrid mode integrations, register additional devices using POST /sellers/{sellerId}/devices.
• Compliance Reporting: Submit KYB/TnC data using POST /notification/seller/status when required.
• Transaction History: Retrieve transaction details using GET /sellers/{sellerId}/transactions for reconciliation.

Common challenges when integrating with Visa Accept:

• Seller Onboarding and Activation: Transactions are attempted before onboarding or activation is complete. Always verify seller status is ACTIVE before processing payments.
• Incomplete or Inconsistent Configuration: Required setup steps are not completed across all systems prior to use. Complete application configuration, card eligibility validation, and seller enrollment in sequence.
• Sandbox to Production Readiness: Prerequisites or validations are not fully completed before production go-live. Ensure all required agreements, approvals, and regional validations are in place.

During integrations, avoid these common errors:

• Transaction Timing: Do not attempt payment or refund calls before sellers are fully onboarded and activated. Always check seller status first.
• Reference Management: Retain original transaction identifiers required for refunds or reconciliation. Missing transaction references prevent refund processing.
• Flow Assumptions: Do not treat the APIs as single-step payment actions. Follow the complete sequence: onboarding, activation, transaction, and post-transaction steps.
• Configuration Dependencies: Verify application settings using /appdetails before beginning integration workflows. Integration mode affects available endpoints and required parameters.