Reusable EMV Level 3 framework

Write the L3 core once. Cast it per processor.

Foundry is the engine behind Paying.co's certifications — a native EMV Level 3 lifecycle written once, with each processor added as a thin, swappable adapter. Native C99 core. Android/Kotlin SDK rides on top as a wrapper.

Start a certification →Read the docs →

132 certifications shipped · <50% of prior pricing · 75 / 25 shared core / adapter

FOUNDRY · ONE CORE → MANY CASTINGS

SHARED L3 CORE · ~75%

Canonical model

BER-TLV

Money

Crypto

only authorize() crosses the processor boundary

CASTINGGlobal Payments

CASTINGTSYS TransIT

CASTINGElavon EPG

CASTINGCybersource

01 · The Foundry model

A mold you reuse, a casting per client.

Every EMV L3 engagement repeats the same lifecycle. Foundry writes that lifecycle once and treats the processor as the only part that changes.

01 · CORE

The engine is written once

Canonical model, BER-TLV parser, hardware abstraction, transaction engine and crypto — roughly 75% of every certification — already built and battle-tested.

Shared across every engagement

02 · CAST

Each processor is an adapter

A new engagement means implementing one seam. Only authorize() differs per processor; credentials stay in the injected transport, never in the adapter.

Thin, swappable processor layer

03 · SHIP

Certify faster, for less

Because the core arrives already proven, the work, timeline and cost collapse to the adapter implementation and the certification test scripts.

More reuse. Less reinvention.

02 · Inside the core

Everything the lifecycle needs, in one place.

The pieces that should never be rebuilt for every processor are centralized, tested and reused.

CANONICAL MODEL

Canonical transaction model & BER-TLV

One normalized transaction shape and a complete TLV parser and view engine feed every processor adapter.

MONEY

ISO 4217 handling

Exponent-aware minor units live in one module — JPY at 0 decimals, USD/MXN/EUR at 2, BHD/KWD at 3 — so adapters never guess.

CRYPTO

Crypto & key management

Key provisioning and the crypto seam are built into the native core and carried intact across targets.

API FACADE

Transport-agnostic lifecycle

Sale, pre-auth, completion, void, refund and get — with idempotency storage and clean in-band error codes.

/* The only seam a new processor implements */
fdy_status_t authorize(
  const fdy_txn_t   *txn,
  const fdy_creds_t *creds, // held by transport
  fdy_auth_result_t *out
) {
  // map canonical → processor request
  // send via injected HTTP transport
  // map response → canonical result
  return FDY_OK;
}
/* everything else — lifecycle, TLV,
  money, crypto — is already done. */

03 · Processor castings

Eight processors. One core.

Every casting on the current roster is live and shipping today — one shared lifecycle with a growing set of processor-specific adapters.

SHIPPED

Global Payments

UCP REST · multi-currency

SHIPPED

TSYS TransIT

Transit-focused adapter · USD

SHIPPED

NAB

NAB Velocity casting

SHIPPED

Santander

ISO 8583 · MXN · via Prosa

SHIPPED

EPX

Via NAB · Custom Pay XML

SHIPPED

Elavon EPG

EPG casting · multi-currency

SHIPPED

Cybersource

Visa Platform Connect

SHIPPED

TSYS Gateway

Second TSYS path alongside TransIT

04 · Native core, any target

A pure C99 engine that runs where you need it.

Foundry's core is native C99 — no Android, JVM or coroutine dependencies. Embed it on unattended terminals, kiosks, native applications, or behind any language's FFI. Android/Kotlin rides on top as a wrapper rather than defining the architecture.

COREC99no runtime deps

ANDROIDKotlin SDK wrappernative underneath

UNATTENDEDKiosks & terminalsembedded target

BUILDCMake · Makefileportable

FFILanguage bindingsclean boundary

VERIFICATIONASan · UBSan · LSanclean

05 · Certified hardware

Built for the terminal families customers actually deploy.

The same native core can sit beneath multiple device ecosystems without changing the transaction model.

ID TECH

Native device integrations

Deploy the same Foundry lifecycle on ID TECH hardware while keeping processor behavior isolated in the casting.

PAX

Android & unattended

Use Foundry below PAX applications and preserve one lifecycle as hardware and processor combinations change.

AXIUM BY INGENICO

Portable native core

Carry the C99 core into AXIUM environments without rewriting the L3 engine around a new runtime.

PUT THE CORE TO WORK

Certify with groundwork that's already proven.

Reconnect on an EMV L3 engagement and put 132 certifications' worth of tested lifecycle, TLV, money and crypto infrastructure to work on your next processor or device combination.

Talk to us →Explore the docs →