Funds
Validate payment authorization, the basis for crediting funds, and consistency between balances and actual transactions.
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 needs no source code and includes one in-scope retest.

A weakness matters because of what it can reach. Connect technical findings to the business operations at risk.
Validate payment authorization, the basis for crediting funds, and consistency between balances and actual transactions.
Check who can read, change or export customer, merchant, order and transaction information.
Examine resource limits, fault isolation and agreed recovery scenarios using controlled validation.
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.
These scenarios illustrate our testing method. Where transaction states need further validation, we can agree separately on using a test environment and synthetic data.
Web, mobile and desktop applications, merchant portals and payment APIs. Test input handling, authentication, sessions and object-level permissions.
Exposed services, cloud and storage configurations, credentials and environment separation. Assess third-party connections only within the authorized scope.
Crediting, balances, payouts, refunds and reconciliation, alongside data exports and resource limits. Follow the access actually obtained to its business impact.
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.
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.
Tell us the domains and applications you want tested, including mobile or desktop clients.
Confirm assets, authorization, price, testing window and communication contacts.
Validate reachable paths and keep your team informed, including high-risk findings.
Receive findings and recommended fixes, followed by one free retest within scope after remediation.
Each finding connects the entry point to the impact, so engineering and security teams can prioritize the fix.
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| Service | What’s included | Estimated price |
|---|---|---|
| Expert support | Remediation guidance from penetration testing experts. Minimum 20 hours. | USD 350 / hour |
| Annual testing plan | One full penetration test plus 3 quarterly tests over 12 months. | 150% of the one-time test price |
| Security intelligence updates | Timely 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.
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 SecurityBlockSec’s security products and services are grounded in the team’s research and hands-on experience in security auditing, attack prevention, and fund tracing.
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.
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.
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.
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.
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.
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.
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.
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.
Discuss the payment operations, systems and testing boundaries that matter to your team.