| File section | Question to resolve | Technical evidence |
|---|---|---|
| Parties | Who sells, who buys, who benefits, and who is authorised to act? | Approved account ownership and screening record before integration |
| Service | Is the item custom work, support, access, an automated digital service, or something else? | Offer, acceptance event, entitlement, and cancellation behavior match the approved model |
| Provider | Can the client-owned account support the parties, EUR route, bank, service, and required identity checks? | Verified configuration in the actual account; no assumed provider access |
| Record | What invoice, fiscal, tax, receipt, or evidence does the client’s adviser require? | Identifiers and status connect to the order and approved accounting handoff |
| Exceptions | Who handles pending, failed, duplicated, disputed, reversed, or refunded activity? | Visible queue, safe retry, user message, audit trail, and reconciliation owner |
Payment eligibility is not inferred from a country page.
Banks, cards, currencies, settlement, customer identity, service categories, and provider policies can alter what is available. Faith Forge Labs does not supply a substitute merchant account or imply that a provider will approve the route. The client owns its accounts and commercial decisions.
Tax and fiscal treatment must arrive before code hardens it.
The Tax Administration of Kosovo provides official starting material, including information concerning digital services from foreign companies. A qualified adviser confirms what applies to the actual seller, buyer, service, and date. Engineering then implements the approved display, evidence, invoice or record, and reporting behavior.
Mandatory checkpoint: a paid engagement can be declined or paused if the client, beneficial owners, end users, end use, banks, vendors, technology, destinations, sanctions or export conditions, or reliable payment route cannot be adequately established.