NewOffensive AI & LLM penetration testing is now available —Learn more →
xtreme.infosec
PAYMENTSGateways, PAs & PSPs

VAPT for Payment Gateways & Aggregators — built for RBI and PCI DSS

RBI’s Payment Aggregator Directions (2025) ask for regular VAPT, PCI DSS compliance and an annual cyber security audit by a CERT-In empanelled auditor. We pentest your checkout, payment APIs, merchant dashboards and card data environment to PCI DSS 11.4, help your team fix every finding, and arrange the CERT-In empanelled audit report through our partner.

Checkout, APIs & dashboardsPCI DSS 11.4 pentestsCERT-In audit via partner
Free quoteWe reply within 1 hour

Get a payments VAPT quote

Share a few details and get clear next steps, a timeline and a fixed quote.

ConfidentialISO 27001 certifiedNo spam, ever
100+Projects delivered
30 minAverage response time
NDASigned before any code is shared
100%Client satisfaction

    Overview

    Testing for money movement and card data.

    In payments, the costly bugs are in the logic: a webhook that marks an order paid without checking the signature, a refund that runs twice, or a merchant who can see another merchant’s settlements. We test these flows by hand alongside segmentation, cloud and infrastructure checks, and map every finding to RBI and PCI DSS requirements.

    SCANNER ONLYXTREME INFOSEC
    Known vulnerability scan✓✓
    Payment, refund & payout logic testing✕✓
    Webhook & callback tampering tests✕✓
    CDE segmentation testing✕✓
    Findings mapped to RBI & PCI DSSLimited✓

    Built for:

    • ●Payment aggregators (online, cross-border, physical)
    • ●Payment gateways
    • ●Prepaid instrument issuers and PSPs
    • ●UPI and payment tech providers
    • ●Merchants with their own checkout
    Book a payments VAPT

    or call +91 98183 63944

    What we test

    What we test for payment companies

    Pick an area to see what we check — and a typical finding.

    Checkout & SDKs

    Hosted checkout, payment pages and JS / mobile SDKs.

    WHAT WE CHECK

    • Amount & currency tampering
    • Payment-page script control
    • Card data in logs & storage
    • 3-D Secure & OTP flow bypass

    EXAMPLE FINDING

    Order marked paid with a
    tampered amount
    CRITICAL

    Payment APIs

    Payment, refund, payout and settlement APIs.

    WHAT WE CHECK

    • Cross-merchant access (IDOR)
    • Refund & payout race conditions
    • API key & signature checks
    • Rate limits & enumeration

    EXAMPLE FINDING

    Refund processed twice
    with parallel requests
    HIGH

    Webhooks & callbacks

    Bank, network and merchant callbacks.

    WHAT WE CHECK

    • Signature & replay checks
    • Status-change trust
    • Callback URL validation (SSRF)
    • Idempotency

    EXAMPLE FINDING

    Unsigned webhook marks
    failed payments as success
    CRITICAL

    Merchant dashboards

    Merchant onboarding, KYC and dashboards.

    WHAT WE CHECK

    • Merchant-to-merchant data access
    • KYC document exposure
    • Role & sub-user bypass
    • Settlement report access

    EXAMPLE FINDING

    Merchant can download
    another merchant’s settlements
    HIGH

    CDE & cloud

    Card data environment, network segmentation and cloud.

    WHAT WE CHECK

    • Segmentation testing
    • Cloud IAM & Kubernetes
    • HSM & token vault access paths
    • Internal & external network pentest

    EXAMPLE FINDING

    Corporate network can reach
    the card data environment
    HIGH

    RBI & PCI reporting

    Reports for RBI audits and your PCI assessor.

    WHAT WE CHECK

    • Findings mapped to PCI DSS 11.4
    • RBI PA Directions coverage
    • Retest evidence for every fix
    • CERT-In audit report via partner

    EXAMPLE FINDING

    Retested report ready for
    your PCI & RBI audits
    READY
    Process

    How payments VAPT with us works

    01

    Scoping call

    Share your products, PCI scope and RBI audit dates. We sign an NDA first.

    02

    Scope & method

    We agree a written PCI DSS 11.4 method: CDE perimeter, application and network layers, and segmentation.

    03

    Testing

    Manual testing on sandbox or production in agreed windows, using test merchants and small amounts.

    04

    Report & fixes

    Every finding with its risk and exact fix, in a format your PCI assessor and auditors can use.

    05

    Retest & audit

    We retest every fix; where a CERT-In empanelled report is needed, our partner verifies and issues it.

    Engagements

    Pick the engagement that fits

    Tell us your licence type and PCI scope, and we’ll send a fixed quote.

    ESSENTIAL

    Checkout + API

    Your checkout and payment APIs.

    • Manual app & API pentest
    • Payment-logic testing
    • Report with fixes
    • 2 free retests
    Get a quote
    MOST POPULAR

    PCI DSS pentest

    The full PCI DSS 11.4 scope.

    • Everything in Checkout + API
    • Internal & external network
    • Segmentation testing
    • Report for your PCI assessor
    Get a quote
    CONTINUOUS

    Year-round programme

    Testing for every release and audit cycle.

    • Twice-yearly VAPT
    • Pre-launch tests for new products
    • 6-monthly segmentation tests
    • CERT-In audit via partner
    Talk to us
    “Their penetration testing methodology was thorough and aligned with OWASP standards. The final report was detailed, actionable, and easy for our developers to understand.”
    Shaik Ajur★★★★★
    “Xtreme InfoSec identified critical vulnerabilities that other vendors missed, with excellent remediation support.”
    William John★★★★★
    FAQ

    Questions before you start

    Does a payment aggregator need a CERT-In empanelled auditor?−

    Yes, for the annual system and cyber security audit under RBI’s Payment Aggregator Directions, 2025. Xtreme InfoSec is not CERT-In empanelled: we run the testing and help you fix the findings, and our CERT-In empanelled partner verifies them and issues the report. How CERT-In audits work →

    Does our PCI DSS pentester need to be a QSA?+

    No. PCI DSS 11.4 allows penetration tests by a qualified internal resource or a qualified external third party with organisational independence, and the tester does not need to be a QSA or ASV. Your QSA reviews the report during the assessment.

    Is an ASV scan the same as a penetration test?+

    No. PCI DSS asks for quarterly external scans by an approved scanning vendor (ASV) and, separately, penetration tests at least once a year and after significant changes. We run the penetration tests; the quarterly ASV scans stay with your ASV.

    How often must payment companies test?+

    RBI’s cyber directions for payment system operators ask for VA and PT at least once a year and before any critical service goes live, and the PA Directions ask for bi-annual VAPT reports. PCI DSS adds yearly pentests, segmentation tests every six months for service providers, and tests after significant changes.

    Will testing affect live payments?+

    We prefer sandbox or UAT, agree windows for any production testing, use test merchants and small amounts, and avoid destructive tests.

    Get started

    Get audit-ready for RBI and PCI DSS.

    Book a free scoping call. Share your products and PCI scope, and get a clear plan and a fixed quote.

    +91 98183 63944

      Message Us

      Tell us what you need — we’ll reply with clear next steps and a fixed quote.

      Your details stay confidential and are used only to respond to your enquiry.

      Privacy Overview

      This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

      Chat on WhatsApp