A new-country launch can go wrong before the first payment if different teams work from different assumptions. The hardware order may describe one reader, the tariff file another currency, and the installation note an obsolete payment Location. A Bulgarian project should start with one versioned configuration pack that everyone approves.
The pack freezes the inputs for a particular deployment. Later changes remain possible, but they become visible decisions with a reviewer and a repeat test, rather than informal substitutions during shipping or installation.
Record today’s Bulgarian payment conditions
The current Stripe Bulgaria regional guide marks Terminal integration Private preview and states that transactions use EUR with the appropriate Bulgarian account and reader Location. WisePad 3 is listed. Confirm preview access for the actual operator, local reader procurement and the intended venue use with Stripe before ordering or promising a launch date.
Use EUR in this Terminal planning pack. If an older template contains BGN, flag it for review instead of copying it into payment configuration. This follows the current Terminal documentation; it is not advice about separate accounting or legal conversion obligations.
CoreCharge’s existing matched integration uses WisePad 3 as the reader, with the native Android rental application and Terminal SDK inside the cabinet. The agreed wiring provides a USB data link and reader power from the cabinet, so the normal reader flow needs no additional merchant phone. The operator purchases and registers the reader through its own eligible local Stripe account. Stripe handles rental payments there; CoreCharge links them to orders and physical rental events.
Create a cover sheet that identifies one setup
| Pack section | Approved input | Owner of confirmation |
|---|---|---|
| Market and account | BG deployment, eligible operator account and preview access | Operator with Stripe |
| Venue | Actual address, support contact and staffing scenario | Operator and venue |
| Payment | EUR, correct environment and Location reference | Authorised integration lead |
| Hardware | Cabinet model, serials, reader, bracket and data cable | Agreed hardware supplier |
| Rental rules | Tariff version, authorisation policy and return network | Operator |
| Acceptance | Test cases, evidence and reopening authority after changes | Operator and CoreCharge |
Include a version, preparation date and approval status on the cover sheet. Store sensitive integration access in the controlled configuration system, not in this document. Identifiers useful for coordination do not justify distributing private keys.
Use change requests for substitutions
If a reader or cabinet model changes, review the mount, data path, software and test scope together. A photograph of a similar enclosure does not establish interchangeability. Stripe’s WisePad 3 documentation describes its SDK connection; the exact CoreCharge cabinet configuration still needs to match the order.
A venue change requires a fresh address and Location review. Stripe’s Location guidance explains the physical-site mapping. Keep the obsolete version for traceability, mark it superseded and give the installer the approved current version.
The European deployment matrix is useful when the same brand prepares several markets. Each country needs its own approved inputs even when the cabinets look identical.
Accept the pack against the physical station
Before dispatch, compare the supplied unit and components with the approved list. At the venue, verify power, network, reader accessibility, Bulgarian customer instructions and displayed EUR tariff. Confirm the real staffing arrangement; technical self-service operation does not by itself approve a fully unattended placement.
Complete a controlled payment, release, return and final-amount check using the intended account and environment. Record discrepancies against the pack version. Resolve them before public opening rather than treating an attractive cover sheet as acceptance evidence.
The test-to-live checklist provides the transition steps. Finish with named support and a first operating review so the documentation remains useful after delivery.
Explore CoreCharge reader-equipped rental stations or request a Bulgaria configuration pack review with your venue, account status and proposed hardware quantity.
References and project scope
Technical references checked on 17 October 2026. The operating procedures above are planning guidance; hardware, account access and payment settings are confirmed for each deployment.