The marketplace can remain a technology supplier if its actual service supplies evidence or technical support without initiating the customer’s payment or receiving the funds. If it submits an online release instruction for the buyer, payment initiation becomes the central permission question. Receiving the purchase money into its own pooled account requires a separate assessment of execution, money remittance or payment-account services. These conclusions follow from the functions in Schedule 1 to the Payment Services Regulations 2017 (PSRs) and the definitions in regulation 2.
The marketplace purchase tested in the UK
On 2026-09-24, UK Finance reported a consumer purchase from a private seller within the Great British Tokenised Deposit (GBTD) initiative. The buyer’s money was locked in the buyer’s account and released when the goods were exchanged. That is the relevant transaction for this analysis. UK Finance’s announcement attributes it to the GBTD pilot.
As at 2026-11-18, the GBTD programme page describes completed retail pilots and further planned testing. Treasury’s update published on 2026-07-14 forecast a full platform in 2027, on page 15 of its strategy report. A marketplace should obtain a bank-specific service offer and operative terms before treating the facility as available for ordinary customer purchases.
The three designs below allocate authority for a proposed UK sterling purchase between a consumer buyer, a private seller, a marketplace and UK banks. The actual pilot’s legal allocation requires its signed mandate and participant agreements.
Establish when the payment instruction exists
A pure reservation restricts the available balance while leaving the deposit credited to the buyer’s account. On those facts, the reservation need not request a payment transaction. The later instruction to pay the seller can be the first payment order. A movement into another account, or an initial instruction already requesting execution, needs a different analysis. The label “lock” cannot decide which event has occurred: regulation 2 defines a payment order by the instruction requesting execution.
An earlier consent or mandate can authorise a later transaction under regulation 67. The bank must distinguish that consent from receipt of the order. Under regulation 81, receipt is generally actual receipt, with specified rules for business days, cut-offs and agreed execution dates. Its deferred-receipt provision identifies a specific day, the last day of a period, or the day funds are placed at the provider’s disposal. A delivery condition needs a supported legal treatment within those rules.
Once an electronic sterling payment order has been received, regulation 86(1) generally requires the amount to reach the seller’s payment service provider by the end of the following business day. The bank cannot assume that calling the order conditional permits an indefinite wait for delivery adjudication. A separate buyer instruction after the reservation gives a clearer event for receipt and execution.
Authentication is a further question. The bank must apply the strong customer authentication requirements relevant to the action, including online access, electronic initiation and remote actions carrying fraud risk. For a payer-initiated electronic remote payment, that authentication must link dynamically to the amount and payee, subject to applicable exemptions. A hold can therefore require authentication even if it creates no payment order. Allocate this to the bank’s service and security process under regulation 100.
Three-design permission comparison
The comparison assumes the marketplace performs these functions as part of its business. PIS means payment initiation service; its provider is a PISP. PI means payment institution, and EMI means electronic money institution. A seller’s delivery evidence and the marketplace’s review do not themselves establish authority to debit the buyer. The governing permissions and exclusions appear in Schedule 1; the FCA applies them to e-commerce and technical support in PERG 15.3, Q25B, and PERG 15.5, Q33A and Q39.
Design A: Bank checks delivery evidence against its buyer mandate. Design B: Marketplace can order release or change the payee. Design C: Marketplace receives money into its own pooled account.
- Funds and account access. Design A: Buyer retains the deposit claim against the bank. Marketplace receives only the transaction information needed for its evidence service. Design B: Buyer’s deposit remains at the bank, but marketplace has instruction rights over payment from that account. PIS can apply while the bank holds the funds. Design C: Buyer first pays the pool. The account holder is the marketplace; customers’ contractual and any beneficial rights require separate terms.
- Reservation and customer instruction. Design A: Buyer instructs bank to reserve. Bank specifies whether this is reservation alone, a mandate, or receipt of a payment order. Design B: Buyer’s delegation and bank interface determine whether the marketplace initiates at reservation, release, or both. Design C: The inbound transfer is already a payment. Later payout or repayment is another transaction. A displayed “hold” represents the provider’s accounting and contract.
- Delivery and dispute information. Design A: Seller supplies evidence; marketplace transmits it. Bank checks the agreed condition. Buyer sends objections through the bank-recognised route. Design B: Marketplace investigates if appointed and may issue an operative release or stop instruction within its authority. That function needs the appropriate provider or agency arrangement. Design C: Marketplace or licensed principal decides under the agreed holding and dispute terms. Its receipt and payout services remain within the perimeter assessment.
- Submit, veto, amend or revoke. Design A: Bank acts on buyer instructions and agreed conditions. Marketplace has no independent payment veto or amendment power. Statutory revocation rules still apply. Design B: Platform release instructions can be PIS. A PISP must preserve the amount, payee and other transaction features notified by the payer; changing them requires a new authorised instruction. Design C: Provider controls the payout mechanism under the customer mandate. Buyer and seller rights must specify when they may request cancellation, release or repayment.
- Authentication and execution. Design A: Bank authenticates the relevant buyer action and executes. Delivery-message authentication establishes the message’s origin. Design B: Bank and PISP perform their respective authentication and secure-communication duties. Bank authentication can coexist with regulated platform initiation. Design C: Buyer’s bank authenticates the inbound payment. The pool provider and its bank apply the controls for the subsequent payout and refund.
- Expiry and post-settlement remedy. Design A: Bank restores the unused reserved balance under the hold terms. Any separate outstanding order must also be addressed. A completed payment needs a repayment or legal remedy. Design B: Bank and principal must reconcile expiry with existing instructions. Platform cannot promise revocation beyond the applicable cut-off. Design C: Provider pays out or repays according to the agreed entitlement and safeguarding arrangements. The buyer’s original bank debit does not disappear on expiry.
- Launch route. Design A: Bank provides the reservation/payment product; marketplace supplies evidence or genuine technical support. Prefer a separate bank-channel payment instruction at launch. Design B: Use an appropriately authorised provider, a genuine bank agency, or registered PI/EMI agency as applicable. Remove independent release and payee control to pursue a technology-only role. Design C: Use a properly scoped receipt/payout provider and safeguarding arrangement, or obtain the marketplace’s own required status. For a PI, establish an onward order and permitted holding period. An ordinary account at a licensed bank is insufficient.
Apply the exclusions to the actual service
The technical-service exclusion in Schedule 1, Part 2, paragraph 2(j) requires supporting payment services without ever possessing the transferred funds. It expressly excludes payment initiation and account information services. For design A, the contract, interface permissions and operating practice must all confine the marketplace to evidence or support. If its delivery message functions as the customer’s online request to initiate payment, the bank’s subsequent checks do not remove that initiation activity.
The FCA recognises genuine outsourced technical support, with responsibility remaining with the payment service provider. A consumer-facing marketplace contract for listing or dispute assistance can coexist with that arrangement. The payment service itself must be provided by the identified bank or licensed principal. PERG 15.5 Q39 and the FCA’s May 2026 Approach Document, paragraphs 5.8–5.10, explain that allocation.
For design B, the definition of PIS covers an online service initiating a payment order at the user’s request from an account at another provider. Neither taking possession of money nor holding the buyer’s login credentials is a necessary element of that definition. The distinction is developed in Licentium’s article on who initiates a UK checkout payment. A release product adds the need to establish the instruction, consent and revocation events at each stage.
PIS permission also has limits. Regulation 69(3)(a) and (h) prohibits a PISP from holding the payer’s funds or changing the amount, payee or another notified transaction feature. A marketplace wanting to substitute a seller or redirect a payment must obtain a fresh authorised instruction and use a service model that permits the proposed function. An unrestricted payee-edit button cannot be justified by a PIS permission.
The commercial-agent exclusion requires an agreement authorising the platform to negotiate or conclude the underlying sale or purchase for either the buyer or the seller, while representing only that side. A payment-collection appointment or a label in the terms is insufficient. The marketplace must show what sales authority the platform exercises and whom it represents. PERG 15.5 Q33A specifically addresses marketplaces and escrow businesses. A neutral dispute intermediary with no authority to negotiate or conclude the sale has no established basis for this exclusion. A true seller-agent model should also explain how its separate buyer-protection promise avoids an inconsistent buyer-agency role.
Partnership terms must identify the regulated principal and its service. Under PERG 15.4 Q28–Q29, a genuine agent of a credit institution permitted to provide payment services in the UK does not require registration under the PSRs. A PI must register its payment-services agent under regulation 34; an EMI must use its applicable agency process. For its own PIS business, the marketplace needs the relevant authorisation. The small-payment-institution route excludes PIS under regulation 14(4).
Resolve a delivery dispute before allowing release
For design A, the buyer should have a bank-recognised way to object while release remains preventable. The marketplace can collect the buyer’s complaint and the seller’s evidence. The bank needs a reliable record of whether an objection reached the agreed channel before the applicable cut-off. A marketplace acknowledgement alone should never be displayed as confirmation that the bank has stopped payment.
The mandate must specify what the bank is testing. If the buyer authorises payment only on actual delivery and absence of a timely objection, an unmet condition can affect whether payment was authorised. If the buyer instead authorises payment on receipt of a named authenticated delivery message, the bank’s correct response to that message can satisfy the payment instruction even where the delivery report is false. The seller’s or marketplace’s liability then requires examination under the sale or protection contract. Regulation 67 and regulation 75 require attention to consent and proof; recorded use of a payment instrument alone need not establish authorisation.
Use this sequence when the buyer disputes delivery:
- The bank confirms whether there is only a reservation, a revocable order, an irrevocable order or an executed payment. The marketplace displays that confirmed state and preserves the complaint timestamp.
- While consent can still be withdrawn, the bank processes a valid withdrawal under the agreed procedure. For a bank-received order, revocation generally ends at receipt. For PISP initiation, the cut-off is the buyer’s consent to that PISP to initiate the transaction. For initiation by or through the payee, it is consent to the payee to execute it. An agreed day under regulation 81(5) permits revocation until the end of the preceding business day. After those limits, regulation 83(5) requires agreement between the payment service user and the relevant provider or providers and, for payee-initiated transactions, the payee’s agreement.
- The marketplace investigates delivery only to the extent its service terms appoint it to do so. The seller supplies evidence and can contest the complaint. The bank investigates payment authority, authentication and execution. A bank undertaking to adjudicate delivery needs express terms covering that additional role.
- At the agreed expiry, the bank removes an unused reservation unless a valid extension or other lawful restriction applies. The documents must also cancel or otherwise resolve any pending payment order. A restored available balance is not a repayment of money already transferred.
- The sale terms determine the remaining buyer and seller obligations. A buyer who wrongfully withholds payment may still face a claim for the price or damages; the buyer retains applicable non-delivery remedies. Sale of Goods Act 1979, sections 49–51, addresses those claims. The expiry of the funding mechanism should be distinguished expressly from termination of the sale.
A delivery dispute alone supplies no general statutory extension of payment execution time. The fraud-delay power introduced on 2024-10-30 requires the grounds in regulation 86(2A)–(2D). The delay must be necessary for the specified enquiries and end no later than the fourth business day after receipt. An ordinary disagreement about performance must use the agreed pre-order or revocation arrangements.
Receipt of funds changes protection and repayment duties
In A and B, a genuine restriction on the buyer’s deposit gives the marketplace no received customer funds to safeguard. Payment-initiation duties can nevertheless apply to B. Before describing the arrangement as custody, escrow or a trust, obtain the bank’s account terms and any instrument creating the claimed proprietary or security rights. Identify the depositor, any beneficiary, release conditions and treatment on insolvency.
In C, the marketplace receives customer money for onward payment. The FCA identifies receipt into an account in the marketplace’s name as a possible money-remittance or payment-account service in its guidance for marketplace business models. An authorised PI must safeguard relevant funds under regulation 23. The FCA’s supplementary safeguarding rules took effect on 2026-05-07; the safeguarding requirements as at 2026-11-18 include CASS 10A and CASS 15. The principal’s obligations must cover the actual receipt and holding chain. Small PIs can opt into the safeguarding requirements.
Regulation 33 also limits a PI’s payment accounts to payment transactions. Under the FCA’s interpretation in PERG 15.2 Q5, customer funds need an accompanying onward payment order, for immediate or future execution, and holding must remain limited to operational and technical need. The FCA rejects indefinite holding. For C, agree the onward order, lawful execution timing and permitted holding period. If the delivery or dispute wait exceeds those limits, keep the money reserved at the buyer’s bank until payment can proceed.
Safeguarding addresses the provider’s insolvency. A right to recover the price of undelivered goods must arise under the sale or protection terms or applicable law. For a pooled-funds launch, use the UK payment safeguarding compliance review to address the implementation once the receiving entity and relevant funds are identified.
A bank may promise the reservation and payment service it actually provides. A marketplace may make a separate buyer-protection promise, with its own eligibility rules, decision-maker and funding source. An escrow promise needs an identified holder, enforceable holding and release obligations, beneficiary rights, dispute procedure and insolvency analysis. The party making each promise must accept that obligation in the customer’s contract. The marketplace’s service terms also require the consumer-service and fairness analysis in Consumer Rights Act 2015, sections 48–50, 62 and 68. The genuine private sale should be kept distinct from those business-to-consumer services.
After settlement, use the applicable remedy. An unauthorised payment engages the bank’s refund and restoration duties under regulation 76, subject to the statutory conditions. Recovery after an authorised payment requires an established seller repayment obligation, an applicable marketplace protection promise or another available remedy. The provider handling a new refund needs the necessary authority for that payment. Licentium’s article on refund responsibilities after settlement provides comparative reading on allocating that later payment; its separate jurisdictional rules must be read in their own setting.
Agree the operating documents before a purchase
- Bank account terms and reservation mandate. Responsible parties and required decision: Bank and buyer agree the amount, named seller, reservation expiry, balance treatment, cancellation/extension rights and whether any payment order exists at reservation.
- Conditional-payment specification. Responsible parties and required decision: Bank identifies receipt, execution and irrevocability events, acceptable delivery evidence, objection priority, failures and late or duplicate messages. Any automatic-release design must satisfy the payment-order rules.
- Marketplace and principal agreement. Responsible parties and required decision: Bank or licensed principal and marketplace define the actual service provider, technical or agency role, instruction permissions, registration where required, responsibility for errors and audit access.
- Sale and buyer-protection terms. Responsible parties and required decision: Buyer, seller and marketplace identify delivery obligations, dispute reviewer, evidence process, seller challenge, expiry consequences, repayment obligor and funding. Private-seller status must be accurately disclosed.
- Customer information and payment records. Responsible parties and required decision: Bank or licensed principal supplies applicable payment-service information, consent records, status acknowledgements and complaint routes. Marketplace uses the same events and terminology.
- Receipt and insolvency documents for C. Responsible parties and required decision: Receiving provider establishes relevant-funds treatment, safeguarding or other applicable arrangements, account ownership, any trust basis and responsibility for release and repayment.
The statutory disclosure basis includes regulation 48, regulation 49 and Schedule 4. The bank and marketplace should approve the screens against those documents before enabling purchases.
Buyer wording for the recommended launch design
The following wording assumes a bank reservation followed by a separate buyer instruction. The transaction summary must display the bank, amount, seller and expiry. The product must implement the described events.
Reservation
Your bank will reserve the purchase amount shown above until the displayed expiry. The amount remains credited to your bank account and is unavailable for other payments while reserved. After the exchange, you can instruct your bank to pay the named seller. The seller receives payment only after that separate instruction is accepted and executed. If the reservation expires unused, your bank will make the amount available again. Your obligations under the sale terms continue unless the sale is cancelled or otherwise ends.
Dispute reported and bank confirmation pending
We have recorded your delivery dispute and sent it to your bank through the agreed channel. Bank confirmation is pending. Check the bank status shown here before relying on a change to the reservation or payment.
Bank confirms reservation with no payment order
Your bank has confirmed that the purchase amount remains reserved and no payment order has been received. We will review the delivery evidence and the seller’s response under the dispute terms. Payment requires your separate instruction to your bank. The reservation will expire at the time shown unless an extension is agreed through the bank’s process.
Launch decision and changes requiring a new route
Launch A only when the bank provides the reservation product and the marketplace’s evidence message has no independent payment-instruction effect. Use the separate buyer instruction described above unless the bank’s conditional-payment documents establish a compliant alternative. Move B into a genuine bank or licensed-provider service arrangement before giving the marketplace release authority. A PIS-only route requires preservation of the payer’s notified transaction. Launch C only after the receiving service and its required authorisation or agency status are established; regulation 138 prohibits unauthorised provision of payment services.
Reopen that decision whenever the marketplace starts generating payment orders, acquires a unilateral release or payee-edit permission, receives funds, or adds account-information services. The contract and production permissions must change together.
The framework-contract termination amendments effective on 2026-04-28 under SI 2025/688 concern termination of the payment-service relationship. An individual purchase reservation ends under its agreed expiry rules, subject to applicable law. Treasury’s Modernising Payment Services Regulation consultation, published on 2026-07-14, is closed as at 2026-11-18. Proposed reform supplies no present exemption for the marketplace’s release function.