Loading...
Supporting developers, startups, and full-fledged companies building on Stellar and Soroban
© 2026 Stellar Development Foundation
Subscribe to the Newsletter
By Catlog
Catlog will integrate Stellar as the core settlement and payout layer of our payment infrastructure, with Stellar USDC as our primary settlement asset.
At checkout, buyers pay in stablecoins from wallets and chains they already use. Using NEAR Intents and Circle's CCTP, we will route payments from supported chains into Stellar, where all merchant balances settle in USDC, with no wallets, keys, or chain complexity for merchants.
For fiat payouts, we will integrate the Stellar Anchor Platform (SEP-24/SEP-31) for compliant conversion into local currencies via regional anchors, plus MoneyGram Access ramps (Currently under KYB review) for cash withdrawals, vital for Africa's cash-preferring and underbanked sellers.
Technical integration: Stellar RPC/Horizon APIs, Anchor Platform APIs, MoneyGram APIs, NEAR Intents, and CCTP.
$97.0K
$2.5M+ in payment volume processed across 50,000+ orders and transactions to date (Crypto payments processed $260k+: https://dune.com/catlogshop0514/inflow-catlog)
2,000+ active merchants running their businesses on Catlog daily
Live in 4 markets: Nigeria, Ghana, Kenya, and South Africa, with multi-currency support already built
Full commerce workflow ownership; merchants use Catlog for orders, inventory, bookkeeping, and payments, making crypto settlement a native option inside software they already rely on, not a standalone tool they must adopt
Revenue-generating with an established subscription business model
Validated demand from crypto-holding consumers; Nigeria and Kenya rank among the world's highest crypto-adoption markets, yet holders must off-ramp to fiat before spending with local merchants. Catlog merchants accepting stablecoins directly removes that friction for everyday local purchases, with cross-border and diaspora payments as a further unlock
Merchant Testimonials (https://www.youtube.com/watch?v=sC4wUkkJYxA, https://www.youtube.com/watch?v=mBYUcq3Tx-Y&pp=0gcJCfkLAYcqIYzv, https://www.youtube.com/watch?v=VJIv9vZckK4&t=22s)
Merchant Stores (https://sadeoni.com, https://fitfuse.org/, https://steady-gadgets.catlog.shop/, https://teesandco.co, https://queenchicfancy.catlog.shop/, https://stephs-little-things.catlog.shop/, https://lacedit.catlog.shop/, https://misslauretacosmetics.catlog.shop/, https://wywrd.catlog.shop/, https://shopalltheeves.catlog.shop/, https://strandshairofficial.catlog.shop/, https://skinvestmentwith-quinn.catlog.shop/, https://4am.catlog.shop/, https://sharonsmity.catlog.shop/?preview_mode=true, https://ebancollections.catlog.shop/, https://jheduhub.catlog.shop/, https://atsalii.catlog.shop/, https://jred-technologies.catlog.shop/, https://radelshair.catlog.shop/, https://sassybyetty.com/, https://taste-of-london-gh.catlog.shop/, https://damsel-in-defense.catlog.shop/, https://dd-store.catlog.shop/, https://camseys-hair.catlog.shop/, https://deelora-jewelry.catlog.shop/, https://maudlamoda.catlog.shop/, https://purelonel.catlog.shop/, https://beautybygrace.catlog.shop/, https://girlies-wigs.catlog.shop/, https://menaskente.catlog.shop/, https://dichewearlagos.catlog.shop/, https://hmwears.catlog.shop/, https://loocheeskinluxury.catlog.shop/, https://skinmust.catlog.shop/)
Timeline: Weeks 1–4
Budget: $26,000
Deliverable 1.1 — Shared Stellar transaction layer
Implement transaction records, the provider-adapter interface, idempotency keys, status transitions, Catlog merchant-ledger references, and Stellar testnet connectivity. Add feature-gated Catlog entry points for cross-chain deposits.
How success will be measured:
A reviewer-accessible test environment is deployed.
Catlog transaction records are linked to Stellar transaction identifiers.
Automated tests verify idempotency and status transitions.
Budget: $4,000
Deliverable 1.3 — NEAR Intents MVP
Integrate the NEAR Intents 1Click API for quotes, route disclosure, deposit handling, and one supported source asset settling into Stellar USDC.
How success will be measured:
A quote is obtained and displayed inside the Catlog test build.
One cross-chain transfer settles successfully into Stellar USDC.
The provider execution ID, source-chain transaction, Stellar transaction, and recorded demo are supplied.
Budget: $10,000
Deliverable 1.4 — CCTP MVP
Implement one inbound USDC transfer to Stellar using CctpForwarder, with correct Stellar addressing and six- versus seven-decimal precision handling.
How success will be measured:
The source-chain burn, Circle message and attestation, and Stellar mint-and-forward transaction are verifiable.
Automated tests cover recipient encoding and USDC precision conversion.
The transferred balance is reconciled to the corresponding Catlog record.
Budget: $9,000
Deliverable 1.5 — QA and reviewer build
Complete the feature-gated UI, smoke tests, error capture, source references, and a reviewer-accessible integrated MVP deployment for NEAR Intents and CCTP.
How success will be measured:
A recorded demo covers the NEAR Intents and CCTP prototypes.
Automated test results and source-code references are supplied.
Reviewers can access and test the deployed build.
Budget: $3,000
Total Tranche 1 budget: $26,000
Timeline: Weeks 5–10
Budget: $27,000
Deliverable 2.2 — NEAR Intents multi-route integration
Implement quote requests, route and fee disclosure, expiry handling, approval and signing, deposit-address management, execution tracking, refund states, and failure recovery across at least three routes.
How success will be measured:
Three supported source-chain or asset routes settle into Stellar USDC.
The routes include at least one EVM and one non-EVM source.
Explorer links, provider execution IDs, and failure-path test results are supplied.
Budget: $10,000
Deliverable 2.3 — CCTP bidirectional integration
Implement inbound and outbound USDC between Stellar and at least one supported CCTP domain, including CctpForwarder, domain and address validation, decimal normalization, attestation recovery, and duplicate protection.
How success will be measured:
Test transfers complete successfully in both directions.
Source- and destination-chain transaction links are provided.
Automated tests cover replay protection, precision, invalid recipients, and interrupted-session recovery.
Budget: $11,000
Deliverable 2.4 — Shared reconciliation and operations layer
Implement merchant-ledger reconciliation, external-event deduplication, transaction retry queues, provider and network identifiers, and an internal transaction-support view for the remaining integrations.
How success will be measured:
A reconciliation report covers every required test route.
A replayed event produces no duplicate balance or transaction change.
The operations view shows pending, completed, failed, and recoverable transactions with their external identifiers.
Budget: $4,000
Deliverable 2.5 — Test automation and observability
Complete unit, integration, and end-to-end test suites together with structured logs, metrics, alerts, and a reviewer-accessible testnet release for the remaining integrations.
How success will be measured:
Automated test results cover successful, failed, retried, expired, and duplicate-event paths.
Monitoring dashboards and a tested alert are demonstrated.
Reviewers receive the testnet deployment, demo video, and supporting transaction evidence.
Budget: $2,000
Total Tranche 2 budget: $27,000
Tranche 3 — Mainnet launch and production verification
=========================================================
Timeline: Weeks 11–25 (mainnet launch and setup in Weeks 11–12; 90-day production verification beginning at the start of Week 13 and ending during Week 25)
Budget: $44,000
Final-tranche on-chain metric commitment
Panel-ratifiable acceptance gate: During a single 90-consecutive-day production verification window beginning at the start of Week 13 and ending during Week 25, at least 10 distinct verified merchants will transact through Catlog, with at least 100 distinct, successfully settled merchant payments on Stellar mainnet processed in aggregate across those merchants. Existing and newly verified merchants are eligible; onboarding and verification do not have to occur within the measurement window, but merchants must be verified before their payments are counted. Each of the 10 merchants must receive at least one qualifying payment during the window. This gate is an explicit Tranche 3 acceptance condition, alongside the integration deliverables below.
Measurement window: Before measurement begins, Catlog will record the exact start and end timestamps in UTC in the SCF submission evidence. Only payments with Stellar ledger close times within that window qualify. The same window applies to D3.5 production route verification.
On-chain footprint registration commitment: Merchant-associated Stellar mainnet addresses are pending and will be supplied to SCF reviewers once generated. Catlog will maintain a reviewer-accessible footprint register with the submission evidence, identifying the accounts used to receive and settle merchant payments, the USDC asset identifier, any Catlog-controlled contract IDs used by these flows, and the mapping between each verified merchant's internal ID and the applicable account and memo or other on-chain payment reference. The initial addresses will be supplied before the measurement window begins; addresses generated subsequently will be added before payments associated with them are counted. Merchant verification records will be available privately to reviewers without publishing sensitive business or personal information.
Counting and verification: A qualifying payment must correspond to a real merchant order or invoice, settle successfully in Stellar USDC through the registered footprint, and reconcile to the Catlog merchant ledger. Each payment is counted once using its unique Catlog payment ID and Stellar transaction hash plus operation or event identifier. Failed, reversed, refunded, duplicate, internal, and designated test-account transactions are excluded. Bridge funding, cash-out, and multiple on-chain legs of the same payment do not create additional merchant-payment counts.
Evidence for panel ratification: The final verification report will include the UTC window, footprint-register link, verified merchant count, qualifying payment count, and a reconciliation export with merchant ID, payment ID, amount, asset, settlement timestamp, ledger status, and Stellar explorer link and operation or event reference for every counted payment. Reviewers must be able to reproduce both counts from the evidence. Route-verification transactions below establish integration functionality and count toward the 100-payment gate only if they independently meet all qualifying-payment criteria.
Deliverable 3.1 — MoneyGram complete integration and launch
Implement the selected wallet onboarding path, SEP-10 authentication, SEP-24 cash-out initiation, KYC handoff, memo and reference-number handling, transaction polling or webhooks, failure recovery, ledger reconciliation, Production Preview, and mainnet rollout.
Budget breakdown:
MoneyGram wallet configuration, SEP-10, and SEP-24 implementation: $7,000
Cash-out UI, KYC handoff, memo handling, status polling, and reference-number flow: $8,000
Idempotency, reconciliation, failure recovery, operations tooling, and automated testing: $7,000
Production Preview configuration, mainnet rollout, verification, and release documentation: $6,000
How success will be measured:
A complete sandbox cash-out covers KYC handoff, USDC transfer, reference-number retrieval, and terminal reconciliation.
Cancellation, expiry, rejected KYC, insufficient balance, delayed settlement, duplicate-event, and retry paths are tested.
Production Preview is completed and a real low-value mainnet cash-out is demonstrated following MoneyGram approval.
Catlog, MoneyGram, and Stellar identifiers are reconciled in the merchant ledger and operations view.
Budget: $28,000
Deliverable 3.3 — NEAR Intents mainnet launch
Deploy the production NEAR Intents integration with at least three live source routes settling into Stellar USDC.
How success will be measured:
Three mainnet route executions complete successfully, one for each supported route.
Provider execution IDs and explorer evidence are supplied.
An interrupted client session resumes without duplicate execution or loss of status.
Budget: $4,000
Deliverable 3.4 — CCTP mainnet launch
Deploy inbound and outbound USDC transfers between Stellar and at least one supported CCTP domain.
How success will be measured:
A mainnet transfer completes in both directions.
Burn, message, attestation, mint, and forwarding evidence is supplied as applicable.
Recovery from an interrupted attestation or client session is demonstrated without double execution.
Budget: $4,000
Deliverable 3.5 — Shared production deployment
Deploy production transaction workers, configuration, secrets, feature flags, ledger integration, health checks, and rollback support for NEAR Intents, CCTP, and MoneyGram.
How success will be measured:
Within the 90-day production verification window defined above, at least one successful mainnet transaction from each required integration route reconciles to the Catlog merchant ledger: each of the three NEAR Intents source routes, CCTP inbound, CCTP outbound, and MoneyGram cash-out. This requires at least six route-verification executions, with all required routes covered.
For each execution, reviewers receive the route, Catlog transaction and merchant-ledger references, provider identifiers where applicable, on-chain explorer links, timestamps, and a reconciliation record confirming the expected asset, amount after disclosed fees, recipient, and final status, with no duplicate ledger entry or unexplained balance difference. MoneyGram cash-out evidence also includes the provider's terminal status, linked to the Stellar transfer.
All required executions reach terminal status and reconcile before the verification window closes. Reviewers can trace each execution from its on-chain evidence to the corresponding ledger entry using a reviewer-accessible reconciliation export or operations view.
The rollback and incident-response procedures are documented and tested.
Budget: $1,000
Deliverable 3.6 — QA, production verification, monitoring, and documentation
Complete production regression testing, dashboards and alerts, support runbooks, user documentation, a composed-flow demo, and low-value production route verification using designated Catlog test accounts. Coordinate participation by verified merchants and evidence collection for the Tranche 3 on-chain metric commitment.
How success will be measured:
The demo covers cross-chain receipt through NEAR Intents and CCTP, Stellar USDC settlement and merchant-ledger reconciliation, CCTP outbound transfer, and MoneyGram cash-out.
Monitoring shows transaction status, completion rates, settlement times, and failure categories.
User documentation, technical documentation, release notes, and operational runbooks are published.
A production verification report provides the relevant provider identifiers and on-chain transaction links for every required integration route, including the D3.5 reconciliation evidence.
The report demonstrates at least 10 verified merchants and 100 qualifying mainnet merchant payments within the defined 90-day window, using the registered footprint and reproducible counts specified in the Tranche 3 acceptance gate. Designated test-account transactions are reported separately and excluded from those counts.
Budget: $7,000
Total Tranche 3 budget: $44,000
10 verified merchants and 100 successfully settled Stellar mainnet merchant payments within a 90-day. Metric will be reported via merchant wallets on stellar.expert , invoice and receipt tying the transaction to a merchant
Silas Adedoyin (Founder/CEO)
Leads vision, product direction, partnerships, fundraising, and market expansion. Technical founder with ~9 years of fullstack experience; previously at Mono (YC W21). Has led Catlog through Techstars NYC and expansion into 4 markets.
github.com/faarda | linkedin.com/in/silasadedoyin
Kayode Ejisun (CTO)
Leads technology strategy and engineering execution: architecture, infrastructure, security, and scalability. Brings hands-on blockchain experience across smart contracts, wallets, dApps, and crypto payment infrastructure, directly relevant to this build.
github.com/polymath-jones | linkedin.com/in/ejisun-kayode
Victor Shigaba (Product Engineer)
Builds the systems powering Catlog's merchant and customer experiences: features, APIs, integrations, and reliability.
github.com/iamvikthur | linkedin.com/in/shigaba-victor-shigaba-530306185
John Ameh (Product Engineer)
Builds merchant-facing products across frontend and backend, including third-party integrations.
github.com/Johnamehgreg | linkedin.com/in/johnamehgreg
Irene Sertonam Blagogee (Growth Marketing)
Leads growth and merchant acquisition through data-driven campaigns focused on adoption, retention, and revenue.
linkedin.com/in/setornam-irene-blagogee-307875152
Jemima Benson-Aruna (Operations)
Runs day-to-day operations, turning priorities into repeatable processes across teams and partners.
linkedin.com/in/jemimaba
EJISUN OLUBUNMI
Shigaba Victor
Silas Adedoyin
No other submissions.