Secure Bancard runs a full ISO merchant lifecycle on Pioneer, built with embedded partner engineers

Accuracy and fixed windows could not bend. Product change still had to move. Point integrations would not hold.

Penny-level ledgers and ACH paths were non-negotiable. Morning settlement, authorization, and dispute files had to clear fee calculation, matching, dynamic risk, and Daily Ledger work within 15 minutes, including human risk review.

Fees, risk rules, and underwriting flows had to stay configurable so new merchant programs did not force core rewrites.

The bet was one production surface from underwriting through funding on Pioneer: rule-driven fees, risk, and underwriting; a daily Camel cycle with analyst hold/release inside the same SLA window; ACH from approved ledger through returns and collections; and multi-level ISO processing with Secure Bancard live as ISO-on-platform.

Capability coverage spans UTool underwriting, daily Camel processing, risk operations, ACH funding and returns, ISO-on-platform, monthly reconciliation, and Merchant Portal self-service. Fees, risk rules, underwriting flows, and reporting stay configurable, not hard-coded per program.

Intronsoft embedded a five-person partner engineering team alongside Secure Bancard's in-house staff for more than four years. This was not a discovery sprint. It was continuous delivery into production systems Secure Bancard already depended on.

Intronsoft owned platform engineering across underwriting tools, daily pipelines, risk workflows, funding, and merchant portals. Secure Bancard retained payment domain, merchant operations, and compliance policy.

Delivery protected accuracy first, kept risk review inside the morning window, landed capabilities domain by domain, and proved multi-level ISO processing with Secure Bancard as a live ISO.

Merchant onboarding flows through UTool, Secure Bancard's underwriting application. Teams configure merchant profiles and fees, including flat and percentage fees for interchange, association, and dynamic fee schedules.

Credit verification and history review feed an approval decision based on the verification report. Approved merchants onboard to the processing application and gain access to the Merchant Portal for reports, statements, and self-service account details.

Each morning, settlement, authorization, and dispute files arrive over SFTP. An Apache Camel pipeline ingests the files, calculates interchange and association fees, matches authorizations to transactions, and applies dynamic risk rules.

The pipeline must complete within a 15-minute SLA. It generates Daily Ledger, risk analysis, loan repay calculations, hold/release, and merchant reports.

Risk analysts review flagged merchants and transactions, apply hold or release decisions, and trigger Daily Ledger regeneration when needed. Human-in-the-loop review sits inside the automated cycle, not after it.

After the Daily Ledger is approved, the platform generates ACH to move funds from Secure Bancard to merchant accounts, and from merchant accounts to Secure Bancard when required.

ACH returns are received and reprocessed. After more than two reprocess attempts, items move to writeoffs and handoff to the collections team.

Monthly reconciliation recalculates the full month per merchant, generates corrective Monthly ACH, and produces monthly statements. Merchants access statements and reports through the Merchant Portal.

Merchants gained a coherent lifecycle: onboarding, funding, statements, and self-service on one platform instead of stitched tools.

Operations kept risk review inside the morning cycle. Product teams changed fees, risk, and underwriting without rewriting the core for each program. Growth gained a live ISO model: Secure Bancard processes as an ISO on the same technology it sells to affiliates.

The platform runs the full merchant lifecycle in production: underwriting, daily processing, risk, ACH, ISO, reconciliation, and Merchant Portal.

Morning settlement, auth, and dispute files clear the daily cycle inside the 15-minute SLA. Secure Bancard runs roughly 15 million transactions a year on this surface, with penny-level ledger and ACH paths treated as a hard constraint.

The platform held. Years of merchant growth ran on a coherent lifecycle surface, and the partnership already had shared operating context when the next leap was required.

When volume and cost pressure demanded another step, the same teams executed a focused scale rebuild. Part 2 covers that work: 10× headroom on ECS Fargate, Redis, and OpenSearch.