Zip (formerly QuadPay) logo
    Buy Now Pay Later

    Metro 2 Integration for Zip (formerly QuadPay)

    Integrate Zip (formerly QuadPay) merchant data with Metro2 for BNPL credit reporting. Zip does not have documented native Metro 2 reporting to US credit bureaus. This Metro2 integration enables merchants to report Zip installment payments under their own furnisher ID. Metro2 connects via Zip's REST API with OAuth 2.0 Client Credentials authentication. The API supports both asynchronous webhooks (posted to your callbackUrl) and synchronous mode (?sync=true). Key endpoints include /orders/authorize, /refund, /void, /confirm, and /capture. Zip charges merchants approximately 4% + $0.15 per transaction.

    How It Works

    Zip merchant data is accessed via REST API (OAuth 2.0 Client Credentials) with endpoints for order authorization, capture, refund, and void. Async webhooks deliver events to your callbackUrl. Metro2 maps BNPL payment data to Metro 2 Base Segment format and submits to Equifax, Experian, and TransUnion under your merchant furnisher ID.

    Zip (formerly QuadPay) logoZip (formerly QuadPay)
    Metro2Metro2
    Credit Bureaus

    Benefits

    Enable Credit Reporting

    Zip does not have documented native credit bureau reporting. This integration enables reporting for your Zip customers.

    OAuth 2.0 REST API

    Connect via Zip's REST API with OAuth 2.0 Client Credentials grant for secure, standards-based authentication.

    Async + Sync Modes

    Receive payment events via asynchronous webhooks to your callbackUrl, or use sync mode with ?sync=true for immediate responses.

    Merchant-Controlled

    Report under your own furnisher ID for direct control over tradeline data and customer credit relationship.

    CFPB Compliance

    Meet evolving CFPB BNPL reporting requirements with Metro 2 compliant submissions to all three bureaus.

    Data Fields That Sync

    Metro2 maps these fields from Zip (formerly QuadPay) to Metro 2 format automatically.

    • Customer demographics and identification
    • Installment terms and payment schedule
    • Payment records, amounts, and dates
    • Account status and delinquency
    • Order authorization and capture data
    • Zip order identifiers and merchant reference

    Get Set Up in 4 Steps

    1

    Obtain OAuth Credentials

    Set up OAuth 2.0 Client Credentials from the Zip merchant portal. Production base URL: gateway.us.zip.co; sandbox: gateway.sand.us.zip.co.

    2

    Connect Zip API

    Set up REST API connection with OAuth authentication and configure webhook callbackUrl for async event delivery.

    3

    Map Installment Plans

    Configure how Zip installment plans map to Metro 2 account types, payment schedules, and reporting fields.

    4

    Launch Reporting

    Validate test data using the sandbox environment and begin production credit bureau submissions.

    Frequently Asked Questions

    Is this for Zip or QuadPay?

    QuadPay has rebranded to Zip. This integration works with the current Zip platform and API.

    Does Zip report to credit bureaus natively?

    Zip does not have documented native Metro 2 reporting to US credit bureaus. This Metro2 integration enables merchants to report Zip transactions under their own furnisher ID.

    How do webhooks work with Zip?

    Zip sends asynchronous webhooks to your configured callbackUrl for payment events. You can also use synchronous mode by appending ?sync=true to API calls for immediate responses.

    What environments are available?

    Zip provides both production (gateway.us.zip.co) and sandbox (gateway.sand.us.zip.co) environments for testing before going live.

    Ready to Connect Zip (formerly QuadPay)?

    Start reporting to credit bureaus from Zip (formerly QuadPay) today. Our team will help you get set up quickly.