Pablo

I build payment infrastructure for crypto — and carry the P&L that comes with it.
Strategy, partnerships and regulatory perimeter on one side of the desk;
schema, services and deploys on the other.

Domain

Payments	On/off-ramp, cross-border settlement, card issuing, BIN sponsorship, payment orchestration
Custody	Custodial and MPC wallet architecture, key management, treasury and reconciliation
Regulation	Licensing perimeter, AML/KYC design, sanctions screening, provider due diligence
Markets	CIS and cross-border corridors, stablecoin settlement, B2B gateway economics

How I work

I sit on both sides of the table. On one, I negotiate with providers and banks, build the commercial model and decide what a given licence does and does not permit. On the other, I design the schema, review the PRs and carry the pager when it breaks.

That combination is the point: most payment products fail not on code and not on regulation, but on the gap between the two.

Stack

_{LANGUAGES & RUNTIME}

_{PAYMENTS ENGINEERING}

Payment rails, licensing perimeter, custody architecture.