Payment Security Assessment

For fiat and crypto payment providers, BlockSec tests payment APIs, merchant permissions, crediting, refunds and settlement. Testing starts from the agreed external scope and connects findings to risks for funds, data and service continuity, with remediation guidance and a retest.

  • External black-box testing
  • No source code required
  • One retest within scope

External black-box testing needs no source code and includes one in-scope retest.

  • Fiat payment providers
  • Crypto payment providers
  • Crypto exchanges
  • Banks & brokerages

Funds. Data. Continuity.

A weakness matters because of what it can reach. Connect technical findings to the business operations at risk.

Funds

Validate payment authorization, the basis for crediting funds, and consistency between balances and actual transactions.

Data

Check who can read, change or export customer, merchant, order and transaction information.

Continuity

Examine resource limits, fault isolation and agreed recovery scenarios using controlled validation.

Payment business logic: from crediting to settlement

We check what business transaction supports a payment instruction, whether its details match the approval, whether the person or system issuing it has permission and whether the conditions for execution are met.

  1. Confirm & credit

    What we test
    False callbacks, repeated notifications, and mismatched amounts or currencies.
    Potential impact
    An unsupported or duplicate increase in the available balance.
  2. Reserve & spend

    What we test
    Concurrent spending and the handling of reserved, frozen or released funds.
    Potential impact
    The same balance spent more than once, or spending beyond available funds.
  3. Pay & refund

    What we test
    Merchant and order permissions, repeated refunds, and recipient changes.
    Potential impact
    Unauthorized payouts, excess refunds or payments to the wrong recipient.
  4. Settle & reconcile

    What we test
    Reversals, repeated adjustments and exception handling against actual transactions.
    Potential impact
    An incorrectly retained balance or a mismatch in the accounts.

These scenarios illustrate our testing method. Where transaction states need further validation, we can agree separately on using a test environment and synthetic data.

What a payment security assessment covers

Payment API and application security

Web, mobile and desktop applications, merchant portals and payment APIs. Test input handling, authentication, sessions and object-level permissions.

  • Merchant isolation
  • API authorization
  • Session controls

Infrastructure & dependencies

Exposed services, cloud and storage configurations, credentials and environment separation. Assess third-party connections only within the authorized scope.

  • Exposed services
  • Credential access
  • Test / production boundaries

Payment workflows

Crediting, balances, payouts, refunds and reconciliation, alongside data exports and resource limits. Follow the access actually obtained to its business impact.

  • Transaction states
  • Data access
  • Resource limits

Clear boundaries before testing starts

The external black-box test requires no source code or internal accounts. Production checks are read-only and exclude operations that could damage production data.

  • Only assets authorized in writing. Third-party services with unverified ownership are excluded.
  • We stop once we establish that funds could be transferred, before any money moves.
  • No DoS or high-volume stress testing.
  • We collect only the evidence needed and store and delete it as agreed.

From agreed scope to verified fixes

Testing takes at least two weeks, with initial findings by the end of week one. Scope, schedule, validation methods and stop conditions are agreed before work begins.

  1. 01

    Share your scope

    Tell us the domains and applications you want tested, including mobile or desktop clients.

  2. 02

    Agree the plan

    Confirm assets, authorization, price, testing window and communication contacts.

  3. 03

    Test & communicate

    Validate reachable paths and keep your team informed, including high-risk findings.

  4. 04

    Report & retest

    Receive findings and recommended fixes, followed by one free retest within scope after remediation.

Evidence your team can act on

Each finding connects the entry point to the impact, so engineering and security teams can prioritize the fix.

  • Entry points and reproduction conditions
  • Evidence and business impact
  • Root causes and remediation guidance
  • Retest results and remaining issues within scope

Start with one assessment. Extend as your systems change.

One-time payment penetration test

From

USD 20,000

From 2 weeks

One comprehensive black-box test of the agreed scope, a report, remediation recommendations and one free retest.

Discuss Your Payment Security Scope

Optional services

ServiceWhat’s includedEstimated price
Expert supportRemediation guidance from penetration testing experts. Minimum 20 hours.USD 350 / hour
Annual testing planOne full penetration test plus 3 quarterly tests over 12 months.150% of the one-time test price
Security intelligence updatesTimely updates on external security incidents over 12 months.USD 2,000 / year

Final pricing and timing depend on the agreed testing scope and system complexity.

Build on what the assessment reveals

Architecture assessment, source-code audit, attack and incident-response exercises, and ongoing monitoring and response can be scoped separately. For on-chain monitoring, explore Phalcon Security.

Explore Phalcon Security

Security research, applied to your business.

BlockSec’s security products and services are grounded in the team’s research and hands-on experience in security auditing, attack prevention, and fund tracing.

Clients served across BlockSec
1,000+
Countries across our client base
60+

Related reading

Payment security FAQ

What is a payment security assessment?

BlockSec uses authorized external black-box penetration testing to assess payment APIs, merchant permissions and workflows such as crediting, payouts, refunds and reconciliation. Findings explain risks to funds, data and business continuity, with evidence and recommended fixes. An assessment cannot guarantee that every vulnerability will be found.

How does this differ from blockchain penetration testing?

This assessment focuses on payment APIs, merchant permissions, crediting, payouts, refunds and reconciliation for fiat and crypto payment providers. Blockchain penetration testing emphasizes signing, approval and withdrawal controls, and on-chain execution for crypto institutions. APIs and fund logic can overlap; the scope is agreed around your systems and payment flows.

Is this suitable for traditional fiat payment providers?

Yes. The service is designed for fiat and crypto payment providers, as well as exchanges, banks and brokerages that handle funds. The systems and payment workflows included are agreed before testing begins.

Do we need to provide source code or internal accounts?

No source code, internal accounts or special system access is required for the initial external black-box test. Additional authenticated testing, test data or source-code review can be agreed separately where needed.

Will testing move real funds or change production data?

No. We use read-only checks in production. If we confirm that funds could be transferred, we stop before initiating a transfer. We agree on test intensity and stop conditions with your team before testing begins.

How long does testing take, and what do we receive?

Testing takes at least two weeks, with initial findings by the end of week one. You receive evidence, reproduction conditions, business impact and remediation recommendations, followed by one free retest within scope after fixes. The final schedule is confirmed for your scope.

Does this replace PCI DSS validation or AML screening?

No. This engagement tests system and business-workflow security. PCI DSS compliance validation and AML screening have separate scopes and requirements. A penetration testing report is not a PCI DSS certification.

How can we test again as our systems change?

The optional annual plan includes one full penetration test plus three quarterly tests over 12 months. Expert remediation support and security intelligence updates are separate options. Scope and scheduling are agreed in the service plan.

Find the path. Understand the impact. Verify the fix.

Discuss the payment operations, systems and testing boundaries that matter to your team.