Skip to main content

List Application Processors

Overview​

List all Processors enabled for a specific Application. The Processor resource represents the acquiring platform where Merchant accounts are provisioned and transactions are processed.

Resource Access​

  • User Permissions: Admin users only
  • Endpoint: GET /applications/\{application_id}/processors

Arguments​

ParameterTypeRequiredDescription
application_idstringYesThe unique ID of the Application

Example Request​

curl -X GET \
  'https://api.ahrvo.network/payments/na/applications/APapplicationExample123/processors' \
  -u username:password \
  -H 'Content-Type: application/json'

Example Response​

{
  "_embedded": {
    "processors": [
      {
        "id": "PRprocessorExample456",
        "created_at": "2023-01-15T10:30:00Z",
        "updated_at": "2023-01-15T10:30:00Z",
        "application": "APapplicationExample123",
        "processor": "DUMMY_V1",
        "enabled": true,
        "default_merchant_profile": "MPprofileExample789",
        "application_config": {
          "can_debit_bank_account": true,
          "enable_pin_debit": false,
          "ach_settlement_delay_days": 3,
          "allow_split_payouts": true,
          "default_currencies": ["USD"],
          "default_level_two_level_three_data_enabled": false
        },
        "config": {
          "processor_specific_field": "value"
        },
        "system_config": null,
        "_links": {
          "self": {
            "href": "https://api.ahrvo.network/payments/na/processors/PRprocessorExample456"
          },
          "application": {
            "href": "https://api.ahrvo.network/payments/na/applications/APapplicationExample123"
          }
        }
      },
      {
        "id": "PRprocessorLitle123",
        "created_at": "2023-03-20T14:15:00Z",
        "updated_at": "2023-03-20T14:15:00Z",
        "application": "APapplicationExample123",
        "processor": "LITLE_V1",
        "enabled": true,
        "default_merchant_profile": "MPprofileLitle456",
        "application_config": {
          "can_debit_bank_account": true,
          "enable_pin_debit": true,
          "ach_settlement_delay_days": 2,
          "allow_split_payouts": false,
          "default_currencies": ["USD", "CAD"],
          "default_level_two_level_three_data_enabled": true
        },
        "config": {},
        "system_config": null,
        "_links": {
          "self": {
            "href": "https://api.ahrvo.network/payments/na/processors/PRprocessorLitle123"
          }
        }
      }
    ]
  },
  "page": {
    "offset": 0,
    "limit": 20,
    "count": 2
  }
}

Additional Information​

  • Processor Types: Common processor types include:
    • DUMMY_V1: Sandbox/testing processor
    • LITLE_V1: Vantiv/Worldpay processor
    • VANTIV_V1: Vantiv processor
    • MASTERCARD_V1: Mastercard processor
    • Additional processors available based on your platform configuration
  • Enabled Status: The enabled field indicates whether the processor is currently active for the Application
  • Default Merchant Profile: The processor can reference a default Merchant Profile that defines fee structures and settlement settings
  • Application Configuration: The application_config object contains settings specific to the Application-Processor relationship:
    • can_debit_bank_account: Whether bank account debits are allowed
    • enable_pin_debit: Whether PIN debit transactions are enabled
    • ach_settlement_delay_days: Number of days to delay ACH settlements
    • allow_split_payouts: Whether split transfers/payouts are allowed
    • default_currencies: Supported currencies for this processor
    • default_level_two_level_three_data_enabled: Whether Level 2/3 data processing is enabled by default
  • Config Objects:
    • config: Top-level processor-wide settings
    • application_config: Settings specific to this Application
    • system_config: System-level configuration (typically managed internally)
  • Multiple Processors: An Application can have multiple processors enabled simultaneously, allowing you to:
    • Route different merchants to different processors
    • Provide redundancy and failover options
    • Support different payment types or regions
    • A/B test different processor configurations
  • Use Cases:
    • Check which processors are available for merchant onboarding
    • Verify processor configuration settings
    • Audit enabled payment processing platforms
    • Determine supported features and capabilities