For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inBook a demo
  • Home
    • Introduction
    • How it Works
    • Integrating your BillPay / AP
      • Overview
      • Validation Workflow
  • Validate
    • GETFind Validation Jobs
    • POSTCreate Validation Job
    • GETGet Validation Job
  • Process
    • GETFind Process Jobs
    • POSTCreate Process Job
    • GETGet Process Job
  • Webhooks
    • POSTPayment Gateway Validation Job Completed
    • POSTPayment Gateway Process Job Completed
Logo
Sign inBook a demo
On this page
  • Validation Workflow
  • Overview
  • Validation Process
  • Step-by-Step Breakdown
  • 1. Extract Data from Invoice
  • 2. Payment Link Detection
  • 3. Vendor Database Lookup
  • 4. Online Vendor Search
  • 5. Payment Modality Determination
  • Benefits
  • Next Steps
HomeValidate Card Acceptance

Validation Workflow

Was this page helpful?
Previous

Overview

Next
Built with

Validation Workflow

The vendor card agent uses a sophisticated validation workflow to process invoices and determine the best payment approach for each vendor. This process ensures accurate payment processing while minimizing manual intervention.

Overview

The validation workflow follows a systematic approach to extract invoice data, identify payment methods, and determine vendor payment capabilities. This process is crucial for successful card payment processing.

Validation Process

Step-by-Step Breakdown

1. Extract Data from Invoice

The agent begins by parsing the invoice document to extract key information including:

  • Vendor name and contact details
  • Invoice amounts and line items
  • Payment terms and due dates
  • Any embedded payment links or instructions

2. Payment Link Detection

If a payment link is present on the invoice:

  • The agent navigates to the provided URL
  • Extracts payment amounts and any associated fees
  • Processes the payment directly through the vendor’s payment system

3. Vendor Database Lookup

When no payment link is available, the agent checks if the vendor already exists in the Mercoa database:

  • Searches for vendor by name, website, or other identifiers
  • Retrieves existing payment modality information
  • Uses stored vendor preferences and capabilities

4. Online Vendor Search

For vendors not in the database, the agent performs an online search:

  • Searches business directories and websites
  • Analyzes vendor websites for payment information
  • Identifies available payment methods and modalities
  • If a phone number is available, the agent can call the vendor directly to inquire about payment acceptance

5. Payment Modality Determination

Based on the search results, the agent categorizes vendors into payment modalities:

  • Phone Payment: Vendor accepts payments over the phone
  • Payment Gateway: Vendor has an online payment system
  • Account-based: Vendor requires account setup or ACH
  • Does Not Accept: Vendor doesn’t accept card payments

Benefits

This validation workflow provides several advantages:

  • Automated Processing: Reduces manual vendor research and setup
  • Payment Optimization: Identifies the most efficient payment method for each vendor
  • Error Reduction: Minimizes payment failures through proper validation
  • Scalability: Handles large volumes of invoices efficiently
  • Compliance: Ensures proper payment processing according to vendor requirements

Next Steps

After validation, the agent proceeds to process the payment using the determined modality. For vendors that don’t accept cards, the system can fall back to ACH payments or other alternative methods.