Open-Source Go Library for FreedomPay Commerce Connect

What it is

go-fcc-connector is a Go library that covers FreedomPay’s Freeway Commerce Connect API. We extracted it out of our production payment platform work and released it as open source under the github.com/nimbus-payments organization — both because it solves a real industry problem and because we believe integration patterns should outlive any one engagement.

Why it exists

FreedomPay is a major payment processor for retail, hospitality, and B2B commerce in North America. Their Commerce Connect API is solid, but at the time we needed it, no idiomatic Go client existed. Teams building Go-based payment infrastructure on top of FCC were either rolling their own, reaching for less-suitable wrappers, or staying on languages they didn’t want to be on.

What it does

The library covers the FCC transaction surface end-to-end: sale, auth, capture, refund, void, and cancel operations against card-present and card-not-present flows. Token management — create, update, and refresh — is supported with the same Go-idiomatic ergonomics. Level II and Level III commercial card data is first-class, which matters for B2B engagements and corporate-card processing where rates depend on line-item data.

The design follows Go conventions: functional options for client configuration, strongly-typed request/response structs rather than generic maps, context support throughout for timeout and cancellation, and bearer-token authentication as the simple base case. There are zero external dependencies — the library uses only the Go standard library.

client, err := fcc.NewClient(
    fcc.WithBaseURL("https://fcc.freedompay.com:1013/api"),
    fcc.WithBearerToken(token),
)

Every public type and function carries godoc comments. The README includes runnable examples for each operation type.

What it represents

This is one of two open-source Go libraries we maintain — the other is go-netsuite-connector for talking to NetSuite RESTlets. They are companion pieces of the same engineering philosophy: when integration patterns are well-understood, they should be available to the broader community, not locked inside one client engagement.

The library is a working artifact of how we approach payments engineering: type-safe, idiomatic, well-documented, and built to be operated in production.

What this looks like as a service

If you are building Go services that need to integrate with FreedomPay, the library is yours to use. If you need help integrating it — or you need a similar library written for a different processor — that is the kind of engineering work we sell.