đŸ“ƒ
Developer Docs
  • Overview
  • Integration Options
  • Webhooks
    • Build a webhook endpoint
    • Check signature
  • Getting Started
    • 1. Creating User Accounts
    • 2. User Account Types & Permissions
    • 3. Generate Access Tokens
    • 4. Choose Integration Options
    • 5. Securing Embedded UIs
      • 5a. Securing Embedded UIs Using HMAC (deprecated)
    • 6. Loading the frontend library
      • 6a. Preloading PayEngine Web-Component in SPA
    • 7. Custom styling the Web-Components
    • 8. Handling Callbacks from Web-Components
    • 9. Available Web-Components
    • 10. Available Webhooks
  • Merchant Onboarding
    • Overview
    • Integration Options
    • Onboarding/Payments Application Workflow
    • Embedded Onboarding UI
    • Merchant onboarding APIs
    • Partner's Onboarding UI
    • Merchant Lifecycle
    • Onboarding to Partner Relationships
  • Processing Payments
    • Introduction
      • Transaction Flow and Status
    • SecureFields JS
      • SecureFields Bank Account
      • Using tokens
    • Credit Card Form
    • Connect with Plaid
    • Connect Mailgun
    • 3D Secure
    • Payments API
    • Searching Transactions
    • Registering a cloud connected device
    • Apple Pay
      • Apple Pay in your native app
    • Google Payâ„¢
    • Level 2 and Level 3 Data
    • Fraud Prevention
    • Reporting
    • PCI Compliance
    • Address Verification Service (AVS) Check
    • Hosted Payments
    • Tap to Pay
  • Card Account Updater
  • ORCHESTRATION SYSTEM
    • Orchestration Overview
    • Onboarding Orchestration
    • Transactions Orchestration
    • Omnicommerce Orchestration
    • Merchant Servicing
    • Universal Reporting
  • TOKENIZATION
    • Automatic Network Tokenization
    • Token Migration Process
  • DISPUTE MANAGEMENT
    • Retrieval Requests & Chargebacks
  • Certification
    • Partner Certification
  • Data Sharing
    • Secure Data Sharing with PayEngine
  • eCommerce Integration
    • PayEngine Payment Gateway for WooCommerce
Powered by GitBook
On this page
  • Level 2 Data Requirements
  • Tax Amount
  • Order Number
  1. Processing Payments

Level 2 and Level 3 Data

The more data you pass with a commercial transaction, the lower the interchange fees that apply to that transaction.

PreviousGoogle Payâ„¢NextFraud Prevention

Last updated 10 months ago

Commercial cards are eligible for level 2 (Business, Corporate and Purchasing cards) and level 3 (Corporate and Purchasing cards only) rates, but may be charged at level 1 rates if you don’t provide all the required data. Consumer cards are only eligible for data level 1.

For Level 3 support please contact your solution engineering point of contact.

Important: Along with Level 2 and Level 3 Data, cardholder ZIP code should always be submitted along with card data for full AVS and interchange qualification. See the section on how to include cardholder ZIP code data.

Level 2 Data Requirements

Tax Amount

Tax Amount is required for both Visa and MasterCard transactions. For Visa, the tax amount must be between 0.1% - 22% of the payment total, and between 0.1% - 30% for MasterCard transactions. This value is sent via the sales_tax field as documented in the and .

Order Number

Order Number is required for MasterCard payments only. This field cannot be blank for a Sale or capture request to meet MasterCard’s Level 2 qualifications and should be sent via the order_number field as documented in the and .

Visa generally requires capture to happen within 24 hours of Auth. Some eligible large ticket payments can be captured up to 7 business days after authorization when using a corporate/purchasing cards.

MasterCard generally requires capture to happen within 48 hours of Auth.

Visa also requires AVS for CNP transactions (except Corporate Card and Purchasing Card, which are always exempt from AVS)

Secure Fields
auth
sale API
auth
sale API