Curbstone

If you are not an IBM i shop

• The vendor’s primary differentiation is IBM i-native integration; cloud-native or non-IBM i organizations may be better served by more stack-agnostic payment providers.

If you require extensive public proof from independent reviews

• Major review platforms showed limited or no Curbstone review coverage in accessible listings during this run, which may be a procurement consideration for enterprises requiring broad third-party validation.

If you require published, self-serve pricing in dollar terms

• The vendor publishes tier thresholds but not the associated fees; organizations needing quick price comparisons without a sales process may prefer vendors with published rates.

If you need an all-in-one acquiring plus gateway bundle

• Curbstone does not provide the merchant account; you must engage a separate acquirer or merchant services provider.

If your roadmap includes moving away from IBM i

• A payments layer optimized for IBM i may create migration work later; consider a stack-agnostic payments abstraction layer if re-platforming is planned.

Known limitations acknowledged by the vendor

• Support excludes custom coding and programming.
• PCI and compliance materials provided by the vendor are informational and are not legal advice.

Roadmap / upcoming features

• No public product roadmap or dated feature commitments were found in this run.

Scale limitations

• The vendor states it supports very large customers and processes large volumes, but independent benchmark data, published SLAs, or incident histories were not identified.

Security/compliance documentation gaps (public documentation gaps)

• No clearly documented SOC 2 or ISO 27001 posture was identified on primary site pages reviewed.
• No public, detailed data residency or hosting region documentation was located in the sources reviewed.

Review / market visibility limitation

• Limited presence of Curbstone-specific, third-party end-user reviews on major platforms was observed in this run (G2 category listing: 0 reviews; Capterra: 0 reviews).

• The vendor targets IBM Power Systems running IBM i and documents RPG-friendly APIs.

• The vendor publishes PCI scope diagrams and describes remote tokenization and related architecture patterns intended to reduce elements of merchant PCI scope.

• The vendor states that annual service agreements include support coverage, while explicitly excluding custom coding/programming from support scope.

• These points reflect vendor-provided positioning. Independent user-review corroboration was limited in the accessible sources for this run.

Review-platform availability check (Gartner, G2, TrustRadius)

• Gartner Peer Insights: No Curbstone-specific Gartner Peer Insights product page or reviews were found in the accessible search results during this run; the platform can be gated and may require login for full discovery.
• G2: Curbstone appears in G2’s "Payment Processing Software" category listing but showed no visible reviews or rating in the accessible results. Attempts to access a direct product reviews page were unsuccessful within this research method.
• TrustRadius: No Curbstone-specific TrustRadius product review page surfaced in accessible results during this run.
• Capterra: Capterra lists "Curbstone CorrectConnect" but the accessible listing showed no visible rating or reviews.

Vendor-attributed testimonials (attributed quotes retained as vendor material)

• Curbstone’s homepage and marketing materials include attributed customer quotes, for example:
  • Delta Apparel: "Using Curbstone Card, we have integrated real-time credit card processing into the order entry system…" (testimonial claims faster order processing and fewer errors).
  • Corvette America: quoted as stating the software "runs flawlessly" and is "simple and easy to implement."
  • Shimano/Pearl Izumi: quoted as stating "The install went exactly as predicted…"
  • Shenandoah Telephone: quoted as stating, "After several months, I think Curbstone has paid for itself… [vendor claim about other providers being more costly]."
  • Filter Specialists, Inc.: quoted as receiving funds "several days earlier" and experiencing less "busy work."
  • Mesa Group: quoted as having a "smooth go-live."
• These are vendor-attributed testimonials and were not independently validated in this research.

Case-study quotes (vendor-published)

• The Senior Life case study includes a vendor-published quote describing a moderate daily transaction volume shifting to self-service payments and reduced phone volume.

Independent community quotes (negative/neutral)

• Direct end-user discussions referencing Curbstone on public community platforms such as Reddit or Hacker News were not identified in this run (searches for Curbstone on those platforms returned unrelated results). This creates an evidence gap: most publicly available voice-of-customer content located in this run is vendor-authored.

Common reasons customers choose Curbstone (inferred from vendor materials and IBM i ecosystem coverage)

• IBM i-native integration and RPG-friendly APIs.
• Goals to reduce PCI scope within IBM i environments.
• Desire to retain an existing merchant account/acquirer (the vendor indicates merchant-of-record services are not provided by Curbstone itself).

Reasons customers might leave or churn (inferred from category dynamics; not verified by Curbstone-specific reviews)

• Migration away from IBM i could reduce the value of an IBM i-specific payment integration.
• Need for an all-in-one acquiring, gateway, and fraud stack with global coverage could motivate migration to larger providers.
• Cost competitiveness relative to interchange optimization or volume discounts elsewhere.

Case studies located (vendor-published PDFs)

• Bartlett Bearing (case study PDF)
• Mystic Stamp (case study PDF)
• Senior Life (case study PDF)

Outcomes reported (examples)

• Senior Life: describes a modest number of daily transactions shifting to self-service payments, reducing manual calls and customer service load.
• Vendor testimonials and case studies report outcomes such as reduced manual work, faster order processing, and improved settlement timing.

Critical evaluation / methodology gaps

• These outcomes are vendor-published and may be directionally useful, but: sample sizes, baselines, and measurement methodology are not disclosed; results may not generalize across industries or card mix.
• Suggested buyer due diligence: request customer references willing to discuss implementation complexity; request measurable KPIs (e.g., downgrade and interchange qualification improvements, chargeback trends); and request confirmation of whether results were audited or measured independently.

• Mid-market to enterprise organizations running IBM i for ERP, order-entry, and financial systems.
• Practical range (inferred): organizations where IBM i is mission-critical and payment volumes justify a dedicated integration and compliance-scope reduction investment (from smaller mid-market up through large enterprise).

• Manufacturing, distribution, retail, e-commerce, insurance, rentals, publishing, higher education, healthcare and dental, pharmaceuticals, telecommunications, government, utilities.

• Decision makers: CFO / Controller, CIO / VP IT, Security / Compliance leaders.
• End users: Accounts receivable teams, call center/customer service teams (MOTO/IVR), e-commerce operations teams.

• IBM i payment acceptance integration without full re-platforming.
• Reduction of PCI scope within legacy systems through tokenization.
• Settlement visibility and operational support for payment workflows integrated with IBM i systems.

• IBM i is the system of record for orders and invoices.
• Requirement to keep sensitive card data out of merchant infrastructure.
• Need to support multiple channels: in-person EMV, online, and MOTO/IVR.

• No IBM i footprint.
• Requirement for fully self-serve, published pricing without engaging vendor sales.
• Requirement for the vendor to act as merchant-of-record or to provide bundled acquiring (vendor does not supply merchant accounts directly).