Security spans the complete payment path
Security scope for gh-link covers the same path as any card transaction, from the approved payment device through to the settlement record. Approved hardware and PIN security apply whether the card is domestic or international.
Separate the baseline from the scheme rules. The baseline moved recently, because 51 future-dated requirements in PCI DSS v4.x became mandatory on 31 March 2025 and include stronger authentication and automated log review.
Those controls are assessed against your whole cardholder data environment, which now includes the new gh-link routing path and any test environment holding real keys. Adding a scheme after a passing assessment quietly extends that scope, so the assessment you cite in 2027 needs to have covered the environment as it looks after enablement.
How should acquirers test acceptance?
Test to GhIPSS requirements. The sequence runs through formal certification of each terminal and software combination, and only then a controlled pilot in live merchant conditions.
Certification exists precisely because specification compliance doesn't predict real behavior. The U.S. Payments Forum describes acquirer terminal end-to-end certification as verifying that deployed terminals send and receive authorization messages correctly between terminal and acquirer host system, with host certification completed first as a prerequisite.
Note the ordering. Host certification precedes terminal certification in every scheme program that publishes one, which means a project plan that runs terminal configuration and host message mapping as parallel tracks will stall at the handover point. Sequence the host work first and the terminal cohorts behind it.
What must functional testing prove?
Functional testing has to prove that every approved terminal and software combination behaves correctly for every supported transaction type. Cover purchases and application selection.
Application selection deserves disproportionate attention. EazyPay Tech identifies duplicate candidate list entries as a frequent EMV Level 3 certification failure because multiple terminal configuration entries share the same registered application provider identifier.
Since adding a domestic AID to terminals that already carry international ones creates exactly that condition, treat candidate list construction as a dedicated test case per card type rather than as something the purchase test covers incidentally.
What belongs in regression testing?
Regression testing protects the acceptance you already have, which is the larger revenue stream and the one nobody thanks you for preserving. Retest international card purchases on both contact and contactless paths.
Firmware versions complicate the retest scope. Under the PCI PTS program guide, POI v6 firmware expires every third year on 31 December, independently of the device approval date.
So a terminal cohort can pass gh-link certification on a firmware build that reaches its own expiry mid-pilot. Pin the exact firmware version into every regression result you record, because a result that names only the model tells you nothing once the vendor ships an update.
What should the pilot measure?
A pilot measures whether the change holds up in conditions you didn't simulate, so pick merchants whose transaction mix and connectivity reflect the wider estate rather than your easiest sites. Define the cohort and the success thresholds.
Scale matters when you choose sites. Bank of Ghana reported 80 POS devices per 100,000 adults in 2025, up from 71 in 2024, with coverage described as low.
Thin coverage means an individual merchant carries more local traffic than density figures suggest, and a failed terminal has no neighbor to absorb the volume. Build your rollback criteria around merchant-level acceptance rate rather than estate-wide averages, because the average will stay healthy while a single site fails completely.
EGS can scope the acceptance journey
The next step is a structured assessment of what your estate and processing environment actually support, mapped against what GhIPSS requires. EGS works at that level, as a fintech and technology partner founded in 2007 with around 500 staff and delivery centers across Europe and Africa. The company builds payment infrastructure and POS software for banks and payment providers.
An engagement covers the terminal inventory and the configuration changes gh-link acceptance requires. EGS does not supply a pre-certified gh-link connector, and no vendor honestly can, because certification attaches to your specific terminal and host combination.
Bring your terminal inventory and your current host specification to a scoping conversation with EGS, and you'll leave with the change list and the dependency order.