Executive Summary
- Launch a defined version of A: the employer makes genuine part-payments of wages from its own funds, pays the fintech’s service charges and owes the remaining wages. Employees incur no fintech debt or fee. This supports a payroll analysis because payment discharges the employer’s wage obligation, rather than creating a separate employee financing obligation. The contractual and operational facts must sustain that distinction. (Financial Services and Markets Act 2000, sections 19 and 22; Regulated Activities Order 2001, articles 60B and 60L.)
- Use a UK-authorised payment institution to hold the employer’s payment funds and execute transfers into employees’ existing bank accounts. Confine the Philippine company to payroll data, calculations, requests and status reporting, without custody or independent payment initiation. A partner’s authorisation does not excuse a separate payment service supplied by the fintech. (Payment Services Regulations 2017, regulations 25, 34, 36 and 138; Schedule 1, paragraphs 1 and 2(j).)
- Split B according to the debtor. A provider-funded £200 employee loan with a £2 compulsory fee presents a consumer-credit case. A corporate facility owed only by the incorporated employer, followed by an employer wage payment, has different borrower and wage-discharge mechanics. Any employee service fee and its deferral still require separate analysis. Provider funding alone does not decide which structure exists. (Regulated Activities Order 2001, articles 60B, 60F and 60L.)
- Treat C’s cash advances, compulsory subscription and employee recourse after employment ends as a planned regulated-credit product. Cancellation of access does not itself cancel existing principal. A reusable facility and separate fixed-sum loans require different documentation and cost calculations. Use an appropriately authorised lender as the real lender if this variant is later developed. (Regulated Activities Order 2001, articles 60B and 60L; Consumer Credit Act 1974, sections 9, 10 and 66A; FCA CONC 4, 5.2A and 6.)
- Apply statutory exemptions cumulatively. A short term, a small fee, a payroll deduction or the label earned wages creates no general exemption. Employer-loan and supplier-credit exemptions each have conditions which an independent fintech’s charged cash advance does not satisfy merely by involving an employer. (Regulated Activities Order 2001, articles 60F and 60G.)
- Keep wage entitlement, completed wage payments, loan principal and service fees in separate records. Variable shifts, disputed hours, leavers and failed transfers can change the available amount and the party bearing the loss. Employment-law review must address deductions, genuine overpayments, minimum-wage treatment and payslips; qualifying employer salary advances follow the mandatory PAYE reporting rule. (Employment Rights Act 1996, sections 8, 13, 14 and 27; National Minimum Wage Regulations 2015, regulations 12 and 13; Income Tax (PAYE) Regulations 2003, regulation 67BD.)
- Consumer communications, complaints and overseas processing remain relevant even where no regulated credit exists. State the fee recipient, cash received, payday effect and recourse plainly. Assign controller and processor roles by actual decisions, and put a lawful UK-to-Philippines transfer mechanism and security controls in place. A one-employer pilot reduces operational uncertainty; it supplies no licensing exemption. (Consumer Rights Act 2015, sections 49, 62 and 68; Digital Markets, Competition and Consumers Act 2024, Part 4, Chapter 1; UK GDPR, articles 3, 5, 6, 28, 32, 44A and 46.)
Wage payments and employee financing obligations
Earned wage access regulation starts with the obligation created by the transaction. An employee’s contractual entitlement to remuneration is a claim against the employer. An app’s estimate of accrued net pay is information about that claim. It does not establish that money has already been transferred, that a separately protected account exists, or that the employee owes a finance provider repayment.
Under article 60B of the Regulated Activities Order, entering into a regulated credit agreement as lender is a specified activity. Exercising, or having the right to exercise, the lender’s rights and duties is another. Article 60L defines credit to include a cash loan and other financial accommodation. The assessment asks whether an agreement supplies credit to an individual or another relevant recipient and whether an exemption applies. The Financial Services and Markets Act 2000 (FSMA) adds the business and UK territorial tests. The agreement’s substance controls; neither interest-free pricing nor deduction through payroll answers those questions. (Financial Services and Markets Act 2000, sections 19, 22 and 418; Financial Services and Markets Act 2000 (Regulated Activities) Order 2001, SI 2001/544, articles 60B and 60L.)
The FCA’s employer salary advance statement describes arrangements that are commonly outside consumer-credit regulation and warns about fees, repeated use and reduced payday income. It also recognises that structures vary. The statement is regulatory guidance, rather than a statutory exemption for every product using salary data. An analysis of a UK salary advance app therefore requires the funding agreement, employee terms and payment mandate. A product name cannot replace them. (FCA, “FCA sets out views on Employer Salary Advance Schemes”, 30 July 2020; Regulated Activities Order 2001, articles 60B–60L.)
Three variants require four defined transaction structures. A is an employer’s own early wage payment with employer-paid service charges. B1 is a provider-funded loan owed by the employee with a fixed transaction fee. B2 is financing owed only by an incorporated employer, which uses the proceeds to pay wages, while an employee pays a separate transaction charge. C combines provider-funded employee advances, a recurring subscription and contractual employee recourse after departure. B1 and B2 are alternative contractual implementations of provider-funded Variant B.
For each structure, the payment partner executes transfers under its own payment-service contract. The fintech receives the service fee in the base variants. If a UK lender later replaces the fintech as the employee’s lender, the lender and fee recipient must be stated separately. None of the illustrations assumes an employee wallet, card or stored-value claim against the fintech. The employee receives sterling into an existing bank account; the app displays wage and transaction information.
Variant A as a genuine employer wage payment
A is the recommended launch design. The employer funds each early payment and instructs its payment institution to make it on the employer’s behalf. The payment discharges the same amount of the employer’s accrued wage obligation. The employer pays the fintech’s software and usage charges under a business contract. The employee pays nothing, promises no repayment to the fintech and gives no fallback debit authority to it. The employer remains liable for the unpaid wage balance.
The operational sequence should make that legal allocation visible.
1. The employer supplies approved time-worked records, rates of pay, payroll deductions, prior payments and payroll dates. The fintech calculates a conservative estimate of eligible accrued net wages and applies an employer-approved withdrawal limit.
2. The employer prefunds its own account with the UK payment institution. The account contract identifies the employer as the payment-service user and the funds as money received for payment transactions. The fintech receives its business fees through a separate invoice and account.
3. An employee submits a wage-payment request through the app. That request goes to the employer’s approval process. The employer authorises the payment in the payment institution’s controlled service; the fintech cannot independently debit the employer’s account or change the beneficiary.
4. The payment institution executes the employer’s transfer to the employee’s existing bank account. Its status messages distinguish pending, completed, rejected and returned transactions. The employer records a wage part-payment only when the transfer has completed under the agreed reconciliation rules.
5. At payroll, the employer calculates the period’s actual gross pay, statutory deductions and net entitlement. It subtracts completed wage part-payments once and pays the balance. The employee can see both the early payments and the amount remaining for payday.
Assume that approved work supports £1,000 of eligible accrued net wages. A proposed 40% limit permits £400 of early pay. Completed payments of £100 and a pending request of £50 leave £250 available. An employee requests a further £200. The old £50 request then fails, and the new £200 transfer completes. Completed early pay is now £300, with no pending transfer. Before any further work accrues, £100 remains available under the cap. If subsequent work brings the final net entitlement to the stipulated £2,000, and no further advances are made, the employer pays £1,700 on payday.
The calculation is 40% of eligible accrued net wages, less completed payments and pending reservations. Availability is floored at zero: a negative recalculation stops new requests without itself creating a fintech debt. The cap is a proposed product control, not a statutory safe harbour. A failed payment releases its reservation only after failure is confirmed. An uncertain payment remains reserved until traced; sending another transfer without resolving the first creates a duplicate-payment risk. The £2,000 illustration stipulates final net pay and does not substitute for a PAYE calculation.
This defined A supports a non-credit conclusion because the employer settles an existing remuneration obligation without substituting an employee debt to the fintech. The strongest competing analysis arises if the documents instead preserve the full wage liability and create a separately repayable employer or provider loan. A payment before the contractual payday can involve financial accommodation where the repayment obligations have that substance. The absence of an employee fee would not establish that no credit agreement exists: credit can be interest-free, and any costs paid on the employee’s behalf require their own assessment. A genuine employer-loan exemption must be tested if the parties choose that structure. (Regulated Activities Order 2001, articles 60B, 60G and 60L; FCA CONC App 1.2.3R; FCA Handbook Glossary, “total cost of credit to the borrower”.)
The recommendation deliberately allocates ordinary estimation and employment risks away from an employee-fintech debt. The employer approves eligible wages and bears its payroll calculation risk. Its terms may preserve lawful recovery of a genuine wage overpayment, without converting every completed wage payment into a repayable app loan. The fintech may indemnify the employer for errors caused by its own breach. That business indemnity must not become a concealed employee reimbursement obligation. Deductions and overpayment recovery still require the employment-law analysis below. (Employment Rights Act 1996, sections 13, 14 and 27.)
If employment ends, the employer reconciles completed part-payments against actual final wages. The fintech has no personal claim for those payments. If fewer wages were earned than the employer previously recorded, the employer must establish the overpayment and an appropriate recovery route. If the employee disputes the hours or rate, the employer must resolve that wage question; an app balance cannot establish the debt by itself.
If the fintech fails, the employer must retain the data and payment references needed to run payroll without it. Wages that remain unpaid remain the employer’s obligation. If the employer fails, further requests should stop when funding or verified wage information becomes unreliable. Already completed wage payments and unused prefunding require separate treatment. Money in the employer’s payment account is not automatically the employee’s property merely because payroll data identifies the employee as a prospective recipient. The account contract, payment status and applicable safeguarding and insolvency rules determine the relevant claims. (Payment Services Regulations 2017, regulations 2 and 23; FCA CASS 15.)
Variant B when the employee owes the provider
B1 should be designed and assessed as employee credit. Assume the fintech pays £200 from its own balance sheet into an employee’s bank account. The employee agrees to repay £200 plus a £2 compulsory transaction fee in 14 days. The fintech is both lender and fee recipient. The employer agrees to collect £202 through the next payroll, with the required employee authority, and remit it to the fintech. The payment partner executes transfers; it does not become the lender merely by moving the money.
The funding sequence differs from A. The fintech sends its own funds to its payment account or instructs a transfer from its bank account. The partner pays the employee on the fintech’s behalf. The employee incurs the agreed finance obligation. Payroll later collects that obligation through an authorised allocation of wages. If the agreement gives the fintech a continuing personal claim when payroll collection fails, that claim survives the failed collection unless a contractual waiver applies.
At a stipulated £2,000 final net wage entitlement, a lawful £202 payroll allocation leaves £1,798 for the employee’s bank account on payday. Together with the £200 loan proceeds, the employee has received £1,998 across the period and paid £2 for the credit. The £200 payment did not itself discharge the employer’s wage debt: the lender supplied it under the employee’s financing agreement. This illustration adds the fee to the repayment. A contract withholding a fee from the initial cash would require different disclosures and calculations.
Five separate £200 advances charged at £2 each produce £1,000 of principal and £10 of transaction fees. The lender must still determine whether the contract creates five fixed-sum agreements or repeated use of one running-account facility. Dates, available credit, repayment terms and compulsory charges affect the required cost and APR disclosures. A price of £2 cannot be assessed meaningfully without the amount received and the period of borrowing. No statutory APR follows from a fee label alone. (Regulated Activities Order 2001, article 60L; Consumer Credit Act 1974, sections 9 and 10; FCA CONC App 1.2.3R–1.2.6R.)
Cash supplied now against an employee’s repayment promise satisfies the central credit concept. Accrued-wage data can constrain the amount advanced and improve collection forecasts, but it does not extinguish the financing obligation. A fixed fee compulsory for obtaining the advance forms part of the credit-cost assessment even if the contract calls it a processing, technology or transfer fee. Charging the employer instead would change the price allocation; it would not necessarily remove an existing employee loan. (Regulated Activities Order 2001, articles 60B and 60L; FCA CONC App 1.2.3R; FCA Handbook Glossary, “total cost of credit to the borrower”.)
The result remains contract-sensitive if the fintech disclaims recourse. A claim limited to a wage receivable, an assignment, a guarantee or a right to collect from payroll must be examined for the actual financial accommodation provided. Removing a direct-debit mandate does not erase a repayment promise. A genuine purchase of a receivable requires analysis of ownership, price, collection rights and who bears non-payment; calling a recoverable advance a purchase cannot settle the statutory test. A narrow remedy for fraud or misrepresentation does not by itself establish that a genuine purchase is lending. The non-credit argument is strongest where the employee receives an employer wage payment and never becomes the financing debtor, which is the separate B2 structure. (Regulated Activities Order 2001, articles 60B and 60L.)
B1 exposes the employee to failures that A allocates differently. If the employer becomes insolvent before payday, the employee may have both an unpaid wage claim and an outstanding loan. The contract must state whether the lender waives collection in that event; the app must not imply a waiver which the terms withhold. A payroll shortfall, departure or disputed shift must trigger the lender’s appropriate arrears and dispute process. It must not produce repeated automatic deductions without checking authority, affordability and the alleged amount. (FCA CONC 7.3, 7.6 and 7.14.)
The fintech’s insolvency does not normally forgive the employee’s contractual debt. A lawful successor may acquire lender rights, with the relevant permission and servicing duties. The operational records must prevent the employer, original provider and successor from collecting the same amount twice. Employees need authenticated notices identifying the creditor and a reliable way to verify any changed payment instruction. Holding or exercising lender rights can itself be regulated under article 60B(2).
For UK entry, the preferred B1 partner route would place the employee agreement with a UK-authorised consumer lender whose permission covers this lending. That lender must actually make the credit decision and hold the lender’s obligations. The Philippine fintech could supply software and defined support; any broking or regulated servicing needs its own exemption, permission or valid appointed-representative arrangement. A payment institution appointed only to transfer £200 supplies no consumer-credit permission to either party. (Financial Services and Markets Act 2000, sections 19 and 39; Regulated Activities Order 2001, articles 36A, 39F and 60B.)
Variant B when only the employer owes the financing
B2 has a different borrower. Assume the fintech lends to an incorporated UK employer, without an employee guarantee or indemnity. The employer alone must repay the corporate facility. It receives the financing into its own payment account and instructs a £200 early wage payment. That transfer discharges £200 of the employer’s wage obligation. The fintech separately charges the employee £2 for the requested service, collected lawfully through payroll. These are distinct employer financing, wage payment and employee service relationships.
The employer repays the £200 corporate borrowing from its own funds under the funding agreement. It must not treat that corporate repayment as an additional employee debt. At £2,000 of stipulated final net wages, the employer owes a £1,800 wage balance after the early part-payment. A separately lawful £2 service-fee deduction leaves £1,798 on payday. The employee’s overall cash is again £1,998. The identical cash total does not make the legal structures identical: B1 preserves the wage debt until payroll allocation and creates employee principal; B2 reduces the wage debt at the early payment and leaves corporate principal with the employer.
An ordinary incorporated company is outside the individual and relevant-recipient borrower classes in article 60B. That supports exclusion of this corporate facility from regulated consumer credit. An employer that is a sole trader, small partnership or another relevant recipient requires a different analysis. An employee guarantee, reimbursement promise or secondary financing agreement also changes the facts. The conclusion depends on the legal borrower, rather than on the employer’s commercial description. (Regulated Activities Order 2001, articles 60B and 60L.)
The £2 employee charge deserves its own test. If it purchases an app service and is payable only at payday, the fintech may be allowing time to pay for its own service. A genuine charge-free deferral can engage the supplier-credit exemption if every applicable condition is met. A fee charged for that deferral, a disguised employee cash loan or different supplier and lender arrangements require further analysis. Treating the corporate principal as outside consumer credit does not clear every contract in the product. Consumer fairness, price disclosure and payroll deduction rules also apply to the employee charge. (Regulated Activities Order 2001, articles 60F and 60L; Consumer Rights Act 2015, sections 62 and 68; Employment Rights Act 1996, section 13.)
On employer insolvency, the fintech bears its corporate counterparty exposure under the funding contract. The employee does not acquire a personal duty to repay corporate principal simply because the financing paid wages. A wage overpayment remains a distinct employer recovery issue. Provider insolvency can interrupt further financing and payment instructions, so the employer needs funding and payroll continuity arrangements. B2 may support a non-consumer-credit principal analysis, but it is a more complex first product than A: it adds employer credit exposure and employee charges without improving the recommended allocation of employee risk.
Variant C with a subscription and employee recourse
C is a planned employee-credit product on the stated mechanics. The provider funds cash advances and the employee must repay them, including after employment ends. A recurring subscription is compulsory for access. In the base variant, the fintech is lender and subscription recipient; a payment partner moves funds without assuming those roles. The app offers no employee stored-value account. Money is paid into the employee’s existing bank account and the employer collects agreed amounts through payroll where lawfully authorised.
Assume a £200 advance and a compulsory £5 monthly subscription. At stipulated net wages of £2,000, collection of £200 principal and one £5 subscription leaves £1,795 on payday. The employee has received £1,995 across the period. Three £200 draws during the same charged month would create £600 principal and one £5 monthly charge on these illustrative terms. A month with no draw still costs £5 while that subscription remains active. These amounts describe hypothetical pricing, not a legal maximum or a market quotation.
The documents must explain what the subscription buys and when it accrues. Access, draw execution, repayment administration and unrelated services may have different legal roles. A mandatory subscription needed to obtain credit can enter the total charge for credit, including where an associated or separate service company receives it. A genuinely optional service requires separate evidence of choice and pricing. Allocating the charge to another group company does not establish that it is outside credit cost. The APR calculation must apply the prescribed assumptions to the actual facility and relevant charges. (FCA CONC App 1.2.3R(4) and (6), and 1.2.4R–1.2.6R; FCA Handbook Glossary, “total cost of credit to the borrower”.)
If the employee can draw, repay and draw again within an agreed credit limit, the arrangement may be running-account credit. Distinct fixed-sum agreements do not become one facility merely because the app displays them together; the contract and ability to reuse credit decide that question. The lender needs documentation, statements, creditworthiness assessments and arrears processes appropriate to the form actually offered. Repeated access cannot be treated as a sequence of unrelated payroll events when one continuing credit relationship governs it. (Regulated Activities Order 2001, article 60L; Consumer Credit Act 1974, sections 9 and 10; FCA CONC 5.2A and 6.)
Employment termination makes the financing risk explicit. If final wages cover only part of the balance, C gives the provider a personal claim for the remainder on the assumed terms. That obligation must be displayed before enrolment and before each draw. Ordinary cancellation should stop future access and charges according to lawful contract terms; it does not by itself extinguish principal already borrowed. Statutory withdrawal or cancellation rights have separate effects and must be distinguished from cancelling the app subscription. (Consumer Credit Act 1974, section 66A; Consumer Rights Act 2015, sections 62 and 68.)
Repeated borrowing can leave the employee with a smaller amount available at each payday. A lender must assess creditworthiness, including affordability risk, under the applicable CONC rules. A feed showing earned wages is not an assessment of essential expenditure, other commitments or the effect of repeated subscriptions and advances. The model should prevent stacking inconsistent with its credit decision, show the next payday amount after all expected collections, and trigger human review where repeated use or payroll instability indicates financial difficulty. (FCA CONC 5.2A, 6.7.2R–6.7.3G and 7.3.)
For departure, employer insolvency or unsuccessful payroll collection, the lender needs a suitable alternative collection process. It should verify the debt, assess the individual’s circumstances and consider appropriate forbearance. Subscription charges should not continue automatically merely because a former employee cannot repay principal or cannot access the employer-linked service; their contractual basis and fairness require review. Debt recovery must not be routed through workplace pressure or disclosure to colleagues. A wage dispute requires the employer to investigate entitlement and the lender to investigate any disputed debt derived from that entitlement. (FCA CONC 7.3, 7.9 and 7.14; Consumer Rights Act 2015, section 62; UK GDPR, articles 5 and 6.)
A UK-authorised lender should own the employee credit relationship if C is pursued. The Philippine company can remain a supplier only to the extent of its actual functions. A contract that calls the partner the lender while the fintech independently commits funds to employees, controls lending and retains lender rights can leave the fintech performing regulated activities. The partner agreement must allocate origination, funding, credit decisions, fees, servicing, complaints, arrears, losses and exit. Payment permissions and lending permissions must each match the activity performed. (Regulated Activities Order 2001, articles 36A, 39F and 60B; Payment Services Regulations 2017, regulation 32.)
Credit exemptions for supplier and employer arrangements
Article 60F(2)’s relevant unsecured fixed-sum exemption requires borrower-lender-supplier credit, no more than 12 payments within 12 months, no interest or other charges, and satisfaction of its exclusions. B1 supplies unrestricted cash and charges for it, so the combination fails. C cannot disregard a compulsory credit-access subscription when testing whether credit is free. Article 60F(3) has a separate running-account test: supplier credit, specified periods of no more than three months for unsecured credit, one payment clearing each period, no interest or other significant charges, and the stated exclusions. A small-fee argument addresses only part of that test. (Regulated Activities Order 2001, article 60F(2), (3), (7) and (8).)
The amendment effective on 15 July 2026 restricts the fixed-sum exemption for specified third-party supplier-credit arrangements. Article 60F(7B)(b) preserves the relevant position for certain agreements resulting from employer or group arrangements with employee borrowers. That saving leaves the remaining article 60F(2) conditions intact. It does not exempt a charged cash loan merely because an employer helped arrange it. An employer-connected saving also cannot support a direct-to-consumer product lacking the required employer arrangement. (Regulated Activities Order 2001, article 60F(2)(e), (7A)–(7C); Financial Services and Markets Act 2000 (Regulated Activities etc.) (Amendment) Order 2025, SI 2025/859, articles 1 and 3(3).)
Article 60G’s relevant preferential-credit routes require borrower-lender credit offered to a particular class, rather than the public generally. One route permits only interest, limited to one percentage point above the highest specified bank base rate measured 28 days before charging. The alternative restricts the total charge and prohibits increases in its rate or amount. The formula-linked repayment exclusion and paragraph 5 conditions must also be satisfied. For this unsecured employer-loan hypothesis, the relevant employment limb concerns employment with the lender or its group; an independent fintech’s contract with an unrelated employer does not satisfy it. Even where a lender’s agreement qualifies under article 60G, introducing the borrower to it can fall within credit broking. The lender’s exemption does not automatically exempt the distributor. (Regulated Activities Order 2001, articles 36A(1) and (4)(d), and 60G(3)–(7).)
Regulated credit agreements and collection
Regulated B1 and C require a consumer-credit operation, including the applicable rules in the FCA Consumer Credit sourcebook, CONC. Before agreement, the lender must supply the applicable prescribed credit information and adequate explanations of payments, adverse features, missed-payment consequences and withdrawal. The employee needs an opportunity to ask questions. A payroll-deduction consent is neither the prescribed credit information nor the executed credit agreement. The agreement must satisfy the applicable form and content requirements; defects can affect enforceability. (Consumer Credit Act 1974, sections 55, 60, 61 and 65; Consumer Credit (Disclosure of Information) Regulations 2010, regulation 3; Consumer Credit (Agreements) Regulations 2010, regulation 3; FCA CONC 4.2.5R and 4.2.12R–4.2.19G.)
The defined unsecured £200 consumer loan ordinarily carries the statutory 14-day withdrawal right under section 66A, subject to its timing and scope conditions. Withdrawal requires repayment of principal and any permitted interest within the statutory 30-day period; it does not allow the borrower to keep the cash. The section also controls additional compensation and qualifying ancillary services. The lender must support early repayment and any applicable rebate. These functions need an accessible app process and a record of the employee’s notice. (Consumer Credit Act 1974, sections 66A and 94–95; Consumer Credit (Early Settlement) Regulations 2004, regulations 2–4.)
Arrears notices depend on the facility and statutory triggers. Sections 86B and 86C distinguish fixed-sum and running-account credit; a missed single repayment does not automatically satisfy every arrears-notice condition. Sections 86D and 86E address relevant non-compliance and default sums. A default notice complying with section 88 must precede the breach-based enforcement steps specified in section 87 where that section applies. Ordinary maturity and every collection contact do not each require a section 87 notice. Court scrutiny of an unfair credit relationship remains relevant. (Consumer Credit Act 1974, sections 86B–86E, 87–88 and 140A.)
High-cost short-term credit requires a separate cumulative test. The relevant agreement must meet the definition’s borrower-lender or peer-to-peer limb, an APR of at least 100%, the prescribed short-term promotion or repayment condition, the unsecured condition and the absence of listed exclusions. A payday date alone is insufficient. If the definition is met, the detailed rules impose an initial 0.8% daily cost cap, an aggregate £15 default-charge cap and a 100% total-cost cap, including their connected-agreement and refinancing provisions. Those caps do not replace affordability or fair-treatment duties. (FCA Handbook Glossary, “high-cost short-term credit”; FCA CONC 5A.2.)
A valid or potentially valid dispute about a regulated debt requires suspension of recovery while the firm investigates. Difficulty paying requires appropriate forbearance and due consideration. Automated collection must comply with the rules on continuous payment authorities, financial difficulty and, where applicable, high-cost credit. A failed deduction must not initiate unlimited debit attempts, a new loan to repay the old one or pressure through the employee’s manager. The lender should agree a sustainable response to the actual cause of failure. (FCA CONC 7.3, 7.6, 7.9 and 7.14.)
A payroll deduction mandate does not itself give the lender a continuous payment authority over the employee’s payment account. Where a continuous payment authority is used, its operation, timing, cancellation and alternative payment options need the prescribed explanation, and the firm must stop using it once notified that it has been cancelled. The FCA definition excludes direct debits covered by the Direct Debit Guarantee and specified separate consent for a single payment. For high-cost short-term credit, two refused requests normally bar further requests under the same agreement, with separate instalment and forbearance provisions; partial-payment requests are also restricted. These are limits on that collection method, not cancellation of the underlying debt. (FCA Handbook Glossary, “continuous payment authority”; FCA CONC 4.6.2R–4.6.3R and 7.6.12R–7.6.17R.)
The contracts should expressly make authorised payroll collection by the agreed collection agent discharge the corresponding employee debt. This is a recommended allocation of intermediary risk. Without it, an employer’s deduction followed by failure to remit can leave a dispute over who received payment legally. The lender, employer and app must record the same discharge event and prevent a second demand for a sum the employee has already paid under the agreed mechanism.
Payment services and e-money definitions
The Payment Services Regulations cover listed services carried on as a regular occupation or business activity. Receiving employer money for onward transfer can constitute money remittance. Maintaining payment accounts and executing transfers can fall within the account-based services. An online service initiating a payment order from an account held at another provider can be payment initiation without holding money. Supplying consolidated information from payment accounts can be an account information service. The employer’s time sheets and payroll calculations are not themselves payment-account data. (Payment Services Regulations 2017, SI 2017/752, regulation 2 and Schedule 1, paragraph 1; FCA PERG 15.3, Q16, Q22 and Q25A–Q25B.)
The lender does not supply a separate payment service merely by lending its own money and receiving repayment. That FCA guidance matters for B1 and C: the credit analysis and the payment analysis answer different questions. Additional custody, account, remittance or initiation functions still require their own assessment. A lender that collects money for another creditor can have a different role from a lender receiving payment of its own debt. (FCA PERG 15.3, Q16; Payment Services Regulations 2017, regulation 2 and Schedule 1.)
The technical-service exclusion requires supporting services and no possession of the transferred funds. It expressly leaves payment initiation and account information outside the exclusion. The defined A workflow therefore separates the employee’s wage request from the employer’s payment authorisation. The fintech prepares information; the employer submits the payment in the partner’s service. A fintech API that instead accepts an employer instruction and initiates the bank payment as its own service requires a different analysis. Licentium’s UK payment orchestration analysis examines comparable limits on a technical supplier’s payment powers. (Payment Services Regulations 2017, Schedule 1, paragraph 2(j); FCA PERG 15.5, Q39.)
Other exclusions do not follow from employer distribution. The commercial-agent exclusion requires the relevant authority to negotiate or conclude an underlying sale or purchase for one side. Ordinary payroll administration does not establish it. One employer’s users do not form a statutory limited network merely because membership is restricted, where payouts are unrestricted sterling in ordinary bank accounts. Employees are not group companies for the intra-group exclusion. (Payment Services Regulations 2017, Schedule 1, paragraphs 2(b), 2(k) and 2(n).)
Electronic money requires electronically stored monetary value representing a claim on an issuer, issued on receipt of funds for payment transactions and accepted by someone other than the issuer, subject to the exclusions. A displayed £400 eligibility estimate does not satisfy those elements merely because the app calls it a balance. A loaded balance usable to pay third parties presents a different product. Employer funding can constitute receipt of funds; the employee need not top up personally. A payment account can also exist without separate e-money issuance. (Electronic Money Regulations 2011, SI 2011/99, regulations 2–3; Payment Services Regulations 2017, regulations 2 and 33.)
If a wallet is added, its issuer, claim, accepted uses and redemption rights must be explicit. An EMI can distribute or redeem its e-money through another entity, but cannot outsource the act of issuance to an agent or distributor. Distribution alone does not authorise separate payment services. A payment institution’s permission does not authorise issuance of the fintech’s own monetary value. Licentium’s payment institution and EMI guide explains that product distinction. The recommended launch uses direct bank payouts and creates no employee wallet. (Electronic Money Regulations 2011, regulations 33–34 and 39–40; FCA, Payment Services and Electronic Money: Our Approach, May 2026, paragraphs 5.2–5.11.)
Software partners and UK authorisation
A software supplier remains outside a regulated activity only while its actual functions support that conclusion. An authorised payment institution outsourcing operational functions must comply with regulation 25, including notification and controls over important functions. Outsourcing cannot transfer senior-management responsibility, undermine internal control or impair supervision. The principal’s responsibilities and audit, incident, subcontracting and exit rights should be reflected in the technology contract. The arrangement does not exempt an independent payment service sold by the fintech. (Payment Services Regulations 2017, regulations 25 and 36.)
If the fintech provides payment services for a payment institution, the agent route requires registration before those services start. The principal must cover the precise services, oversee the agent and accept the applicable responsibility. Employees and employers must know the principal’s identity. Payment-agent registration is different from authorisation as a payment institution and from appointed-representative status under FSMA. (Payment Services Regulations 2017, regulations 34 and 36.)
A credit appointed representative needs prescribed business, an appropriate principal agreement and written acceptance of responsibility. Eligible broking, debt collection and administration have their own prescribed limbs. The prescribed article 60B lending limb is limited to credit free of interest and all other charges. It therefore cannot allow the fintech itself to originate charged B1 or C loans under another firm’s permission. A lending partner should remain the real lender, while the fintech’s intermediary functions are separately assessed. (Financial Services and Markets Act 2000, section 39; Financial Services and Markets Act 2000 (Appointed Representatives) Regulations 2001, SI 2001/1217, regulation 2(1)(abc), (af), (ag) and (cd).)
B1 and C also require an assessment of the employer’s role. Introducing employees, helping them apply, collecting loan repayments or administering the lender’s rights can engage credit broking, debt collection or debt administration where the activity is carried on by way of business and no exclusion applies. An incidental unpaid payroll role and a paid distribution business can produce different business-test conclusions. The employer’s role needs its own documented basis; the lender’s permission does not automatically cover it. (Financial Services and Markets Act 2000, section 22; Regulated Activities Order 2001, articles 36A and 39F–39H; FCA PERG 2.3.3G.)
A payment institution’s ancillary-credit power is also limited. Regulation 32 requires credit connected with specified payment services, granted exclusively in connection with executing a payment transaction and ancillary to those services. It prohibits funding that credit from money received or held to execute customer payments, and imposes the relevant own-funds condition. An employee cash-lending business does not become permitted through that provision merely because a payment institution transfers the proceeds. Separate consumer-credit permission or an applicable exemption remains necessary. (Payment Services Regulations 2017, regulation 32; Electronic Money Regulations 2011, regulation 32(2).)
Own UK payment-institution authorisation is the route if the group intends to supply the UK payment service under its own responsibility. The statutory conditions include a UK-incorporated applicant with its head office and any registered office in the UK, and at least part of its payment-services business in the UK, alongside the other authorisation requirements. The EMI regime contains a separate overseas-body UK-branch route whose payment services must be related to e-money issuance. Adding a wallet to obtain that route would change the product. A small pilot itself creates no exemption; the recommended partner is a fully authorised institution, not a small PI whose safeguarding treatment may differ. (Payment Services Regulations 2017, regulations 6 and 23(16); Electronic Money Regulations 2011, regulations 6(4)–(4A) and 32(4).)
Territory must be assessed separately for credit, payments and e-money. FSMA sections 19, 22 and 418 govern the relevant regulated-credit analysis. PSR regulation 138 and EMR regulation 63 impose separate UK prohibitions. In PERG 15.6, Q46, the FCA says that it would not generally expect the PSRs to cover a provider incorporated and located abroad whose only activity is supplying internet and other services to UK customers from that overseas location. UK staff, agents, account servicing and decision-making can alter that assessment. That payments guidance cannot be transplanted into credit or e-money. Offshore incorporation and foreign governing law are not a general UK permission. (Financial Services and Markets Act 2000, sections 19, 22 and 418; Regulated Activities Order 2001, article 72; Payment Services Regulations 2017, regulation 138; Electronic Money Regulations 2011, regulation 63.)
Safeguarding and insolvency claims
The authorised PI must safeguard relevant payment funds. The supplementary CASS 15 rules effective from 7 May 2026 add detailed controls, including allocation and reconciliation requirements. Resolution packs, safeguarding returns and applicable audit requirements provide evidence to examine during partner selection. The partner must demonstrate which receipts belong to which payment-service user and how outstanding transfers are treated. Payroll funding cannot become lending capital or the fintech’s operating cash. (Payment Services Regulations 2017, regulations 23 and 32; FCA CASS 15.2 and 15.8; CASS 10A; SUP 16.14A and SUP 3A.)
Safeguarding protects the applicable customer claim against payment-provider failure. It does not insure the employer’s solvency or automatically give employees ownership of unused money in the employer’s account. Before money reaches the partner, its safeguarding obligations do not protect the employer’s ordinary bank balance. After a wage transfer completes, the employee’s receiving-bank relationship is a separate matter.
Failure of a non-bank PI or EMI does not carry FSCS deposit protection. Special administration can identify relevant claims, constitute the protected asset pool and distribute it under statutory rules. Costs, delays and shortfalls remain possible. A safeguarding bank’s failure raises separate depositor and eligibility questions. Employee communications should therefore explain the actual account and protection, without promising guaranteed or immediate recovery. (Payment and Electronic Money Institution Insolvency Regulations 2021, SI 2021/716, regulations 12–15, 17–19 and 42; FCA, “Using payment service providers”, section “How you’re protected if your provider fails”.)
The partner contract must also allocate refused, misdirected and defective payments. An incorrect account identifier can change the ordinary execution-liability position; fraud-reimbursement rules remain separately relevant. Permitted corporate-user opt-outs may affect the employer’s remedies. The company should not promise that the employer and employee have identical payment claims. Each incident needs the instruction, beneficiary-change history, partner trace and applicable contract. (Payment Services Regulations 2017, regulations 63, 82, 90–91 and 94.)
Variable work payroll corrections and lawful deductions
The app should calculate eligibility from completed work approved by the employer. A roster records anticipated shifts and does not prove that wages were earned. The calculation needs applicable pay rates, unpaid breaks, absences, tax, National Insurance, pension contributions and other lawful deductions. Conditional commission, disputed hours and unconfirmed corrections should not increase available early pay. Excluding a disputed amount from the app’s estimate does not decide the employee’s wage claim or authorise withholding undisputed wages.
Employment review must distinguish A’s and B2’s wage part-payments from B1’s and C’s collection of employee debt. In Great Britain, section 13 generally requires statutory authority, an applicable contractual term notified in writing, or prior written agreement for a wage deduction. Section 27 expressly preserves deduction protection for wages used to repay advances. Section 14(4) contains particular conditions for deductions paid to a third party. A general app acceptance cannot establish that each principal, fee and final-pay deduction meets these rules. The employer must hold and apply the actual authority. (Employment Rights Act 1996, sections 13, 14(4) and 27(2)(a).)
A genuine wage overpayment has a statutory deduction exception. A rejected transfer, contested shift or provider service fee is not automatically an overpayment. The employer must retain the source records, investigate the amount and distinguish a lawful correction from a disputed debt. Resignation does not itself permit collection of every balance from final wages. A’s documentation should leave any genuine employer overpayment claim with the employer and prevent an automatic conversion into fintech arrears. (Employment Rights Act 1996, sections 13(3)–(4) and 14(1).)
Minimum-wage treatment is a separate inquiry. The calculation must allocate remuneration to the correct pay reference period. A loan or wage advance does not count as additional minimum-wage remuneration, while deductions or payments on account of a genuine loan or wage advance have a specific exception. HMRC’s interpretation of a genuine documented employer advance includes related repayments, interest and charges. It separately directs attention to additional charges for providing the advance and the employer’s use and benefit. The actual money received, agreement and payroll entries must support the treatment. (National Minimum Wage Regulations 2015, SI 2015/621, regulations 9, 10(a) and 12(2)(b); HMRC National Minimum Wage Manual, NMWM09210 and NMWM11150.)
A payroll deduction for the employer’s own service can reduce minimum-wage pay even where the worker chose the service and consented in writing. A separate voluntary payment to the employer for that service can receive different treatment under regulation 12(2)(e). Conversely, a deduction remitting the worker’s own voluntary liability to a third-party fintech generally does not reduce minimum-wage pay provided that it is not expenditure in connection with employment under regulation 13, the employer does not require it and the employer charges no administration fee. B2’s £2 fee therefore requires its recipient, legal debtor and purpose to be established. Employer-required expenditure and employer administration charges need separate treatment. A avoids the employee-fee question but still requires the correct wage and hours calculation. (National Minimum Wage Regulations 2015, regulations 12–13; HMRC National Minimum Wage Manual, NMWM11130, NMWM11170 and NMWM11180.)
An itemised pay statement is required at or before a wage or salary payment, with the prescribed pay, deduction and applicable part-payment information. Where pay varies by time worked, relevant hours must appear. Payroll should approve the statement accompanying early wages and the account of completed payments at payday. The PAYE reporting rule does not remove this employment obligation. Keep hours, rates, deduction authority, adjustment history and settlement evidence. Minimum-wage records have the six-year retention period prescribed by regulation 59(8); relevant PAYE records have a separate minimum of three years after the tax year. Those requirements do not justify retaining every app field indefinitely. (Employment Rights Act 1996, section 8; National Minimum Wage Regulations 2015, regulation 59; Income Tax (PAYE) Regulations 2003, regulation 97; UK GDPR, article 5(1)(e).)
Northern Ireland uses the Employment Rights (Northern Ireland) Order 1996. Articles 45 and 46 contain counterpart rules for deduction authority, genuine employer overpayments and written third-party collection arrangements; article 59(2)(a) preserves deduction protection when advances are recovered. Article 40 requires employees to receive an itemised statement at or before wage payment, stating gross pay, deductions, net pay and applicable part-payment details. Its present statutory wording differs from Great Britain’s worker and variable-hours provisions. A Northern Ireland rollout should apply those local provisions and review subsequent amendments while retaining clear hours and payment information in the product. (Employment Rights (Northern Ireland) Order 1996, SI 1996/1919 (N.I. 16), articles 40, 45–46 and 59.)
Qualifying salary advances follow mandatory combined PAYE reporting. Regulation 67BD applies where regular pay intervals are at least one week and no more than one month, the early amount represents completed service not already paid for, the amount would otherwise enter the next regular payment, and the employer makes the corresponding reduced payment. The qualifying advances and reduced regular payment are treated as one relevant payment at the latter time for the specified reporting and record purposes. This is not an optional concession. (Income Tax (PAYE) Regulations 2003, SI 2003/2682, regulation 67BD(1)–(3).)
A third party can pay on the employer’s behalf while the employer retains that reporting obligation. This can support A and B2 where the payment genuinely discharges employer wages. B1’s and C’s separate employee loans cannot be treated identically merely because the next payroll collects them. In the B1 illustration, £1,798 is the employee’s bank payment after the £202 collection; it is not the whole wage entitlement or the taxable-pay calculation. Other loans and advances need their own tax treatment. (HMRC PAYE Manual, PAYE72053.)
On employer insolvency, statutory wage-related payments depend on the employee, qualifying debt, termination conditions and statutory limits. They do not guarantee every wage balance or repay a finance provider automatically. The employer, partner and insolvency officeholder need the completed-payment history to establish what remains unpaid. The pilot should stop further requests where valid funding or reliable wage approval is unavailable. These controls preserve the differences between A’s wage claim, B2’s corporate debt and B1’s or C’s employee credit. (Employment Rights Act 1996, sections 182 and 184.)
Employee communications repeat use and complaints
The request screen should identify the payer, lender where present, fee recipient, cash arriving, expected payroll effect and surviving repayment obligation. A should show an employee price of £0. B1 should display £200 received, a £2 fee and £202 due. B2 should distinguish the employer wage payment from its £2 service charge. C should state the recurring £5 illustration’s billing period, no-use charge, cancellation method and continuing principal. Projected payday pay must be identified as an estimate where hours or deductions remain unsettled.
Consumer law can apply outside regulated credit. The Digital Markets, Competition and Consumers Act prohibits unfair commercial practices, including misleading omissions and omitted mandatory price information. The Consumer Rights Act controls the fairness and transparency of a separate consumer app contract or notice within its scope; employment contracts and employer-employee notices have express exclusions. An employer-distributed fintech service does not acquire that employment exclusion automatically. Terms making the app’s balance conclusive, permitting arbitrary price changes or imposing disproportionate charges require review. A statement of zero interest must not conceal compulsory fees. (Digital Markets, Competition and Consumers Act 2024, sections 225, 227 and 230; Consumer Rights Act 2015, sections 48–49, 61–64 and 68, and Schedule 2.)
Repeat-use alerts should show cumulative withdrawals, fees and the resulting payday amount. A proposed pilot trigger is a private support prompt after early pay is used in two consecutive pay periods, with access to free independent money advice. That is a proposed operating choice, not a statutory frequency limit or evidence of poor work performance. Fee-bearing products should assess whether repeated small requests produce an unexpected total cost. The employer should not receive debt details to exert workplace pressure. (FCA, “FCA sets out views on Employer Salary Advance Schemes”, 30 July 2020; FCA CONC 7.9; UK GDPR, articles 5–6.)
Subscription cancellation requires classification of the service. The enacted DMCC subscription chapter excludes contracts of a banking, credit or payment nature to the relevant extent, and its substantive subscription duties are not yet operative. A distinct non-financial app service requires separate analysis. Current law already gives qualifying non-financial distance service contracts an ordinary 14-day cancellation period, subject to performance, information and other conditions. The Financial Services (Distance Marketing) Regulations contain a different regime, with exclusions for relevant authorised-person contracts and interaction with consumer-credit withdrawal. Where their cancellation right applies, the ordinary period is 14 calendar days; repayment and permitted service charges are separately regulated. No single cancellation rule applies to every A, B or C contract. (Digital Markets, Competition and Consumers Act 2024, sections 254–255 and Schedule 22, paragraph 2; Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013, regulations 6, 30 and 36; Financial Services (Distance Marketing) Regulations 2004, regulations 2–5 and 9–13; Consumer Credit Act 1974, section 66A.)
An intermediary marketing a financial service may also owe its own information duties under regulation 6 even where the supplier benefits from an authorised-person exclusion. Regulation 6A contains a narrow exception for specified supplier-credit intermediaries. Its conditions do not exempt the charged cash loans in B1 and C merely because an employer arranges access. The company must therefore assess the lender’s contract and the fintech’s marketing role separately. (Financial Services (Distance Marketing) Regulations 2004, regulations 4, 6 and 6A.)
Provide one complaint intake channel with named responsibility for each issue. The employer investigates wages and deductions; the payment partner investigates execution and accounts; the lender investigates credit and collection; the controller investigates data accuracy and privacy. A complaint spanning several issues needs coordinated handling and a clear explanation to the employee. Wage underpayment and a genuinely disputed loan are related facts, but one does not automatically resolve the other.
For complaints within DISP, the ordinary rule requires a final response or the prescribed delay response within eight weeks after receipt of the complaint. Qualifying payment-service and e-money complaints require a final response by the end of 15 business days after the day of receipt. Exceptional reasons beyond the respondent’s control can permit a final response by the end of 35 business days, with a reasoned holding response within the first 15. Financial Ombudsman jurisdiction depends on the activity, respondent and eligible complainant relationship. A payment partner does not confer Ombudsman jurisdiction over every wage or software dispute. The Consumer Duty applies by the regulated firm’s retail activities and influence over outcomes, including relevant distribution functions; it does not automatically regulate an independent software supplier. (FCA DISP 1.6.1R–1.6.2AR, 2.3 and 2.7; FCA PRIN 3.2.6R–3.2.8R and PRIN 2A.1.13G–2A.1.15G.)
UK privacy and processing in the Philippines
Under the defined A, the employer determines the payroll purpose and eligibility rules, and the fintech can process on its instructions under an article 28 agreement. The payment partner can be an independent controller for its payment and legal-compliance purposes. In B or C, a provider deciding credit eligibility, repayment risk and collection is likely to control those purposes. Jointly determined purposes and means require an article 26 arrangement. The contracts must follow the actual decisions rather than assign every company a processor label. (UK GDPR, articles 4(7)–(8), 26 and 28.)
Each controller needs a lawful basis for each purpose. The employer’s contract with the fintech is not itself an employee contract supporting article 6(1)(b). Employment consent requires genuine choice despite the power imbalance. Keep the wage-payment request, deduction authority and any data-processing consent legally distinct. Limit the feed to identifiers, verified payment details, approved earnings, adjustments, pay dates and necessary employment-status changes. Detailed health absence reasons, union information and biometric clocking data require an additional special-category assessment if used. Payroll access does not authorise unrelated marketing or performance monitoring. (UK GDPR, articles 5–7 and 9; ICO, “Data protection and monitoring workers”.)
An overseas company can fall within UK GDPR through the relevant UK establishment, service-offering or behavioural-monitoring tests. Employee payment is not required for the service-offering limb. Where article 3(2) applies without a UK establishment, assess the article 27 representative obligation; continuous payroll processing does not become occasional merely because one employer participates. Employee notices must identify purposes, sources, recipients, overseas processing, retention criteria and routes to correct data and challenge decisions. Article 14 matters where information comes from the employer. Subject to the applicable exceptions, that information is due within a reasonable period no later than one month, and earlier where the first communication or disclosure triggers the rule. (UK GDPR, articles 3, 13–14 and 27.)
Current automated-decision rules sit in articles 22A–22D. A solely automated decision producing legal or similarly significant effects requires the applicable information, representation, human-intervention and challenge safeguards. Additional restrictions govern special-category data and the specified recognised-legitimate-interest basis. A nominal approval click is not meaningful human review. A worker disputing accrued wages should be able to obtain review by someone who can inspect the records and change the outcome. (UK GDPR, articles 22A–22D.)
Remote access by a separate Philippine company can be a restricted international transfer even when the server remains in the UK. The Philippines is outside the UK’s adequacy list. The proposed route uses a completed UK International Data Transfer Agreement or UK Addendum to the EU standard contractual clauses, with the required reasonable and proportionate assessment of whether protection after transfer would be materially lower. EU clauses alone do not complete the UK route. Map support access, backups, onward processing, encryption keys and legal demands, and document necessary additional protections. (UK GDPR, articles 44A and 46(1A)–(3), (6)–(8); ICO, “Is the restricted transfer covered by adequacy regulations?” and “What are standard data protection clauses (the UK IDTA and the Addendum)?”)
The controller must assess whether the processing requires a data protection impact assessment because it is likely to present high risk. The combination of employment information, financial vulnerability, automated decisions and overseas access warrants a documented assessment. Proposed controls include multi-factor authentication, least-privilege access, encryption, separation of employer records, controlled bank-detail changes, audit logs and tested recovery. Processor terms must cover subprocessors, rights requests, breach assistance, audits and exit. These are controls selected for the product’s risks, not a claim that one software configuration guarantees compliance. (UK GDPR, articles 28, 32 and 35.)
Controllers must facilitate data-protection complaints, acknowledge them within 30 days beginning when received and take appropriate steps to investigate, report progress and communicate the outcome without undue delay. Thirty days is not a universal resolution deadline. Processors report breaches to controllers without undue delay; controllers apply the notification risk test and, where required, the 72-hour period after becoming aware of the breach, where feasible, with a separate high-risk assessment for employee notification. The support system must distinguish a wage dispute, an access request, a complaint and a security incident while allowing the employee to report them through one channel. (Data Protection Act 2018, section 164A; UK GDPR, articles 33–34.)
Philippine obligations follow the activity retained at home
A Philippine software company needs corporate authority for the business it undertakes. Incorporation does not authorise separately regulated lending, financing, payment operations or e-money issuance. If the Philippine entity originates employee loans, funds employers as a lending business or purchases receivables as financing, it must assess the SEC lending-company or financing-company requirements for those functions. A’s confined software role and B’s or C’s retained funding roles therefore need different home-law reviews. No Philippine classification supplies a UK exemption. (Republic Act No. 11232, sections 13, 18, 22, 35 and 44; Republic Act No. 9474, sections 3–4; Republic Act No. 5980, as amended by Republic Act No. 8556, sections 3–4 and 7.)
The National Payment Systems Act distinguishes an operator performing the relevant clearing, settlement or system functions from a provider of technology or infrastructure to an operator. BSP rules also examine platforms enabling transfers and systems processing payments on another’s behalf. Software can be part of an operator’s business; calling the company a technology vendor does not settle the test. The company should map the decisions and functions actually retained in the Philippines. If it undertakes local e-money functions, the BSP’s separate definition and authority requirements apply, including its guidance on partnership, outsourcing and co-branding. The recommended bank-payout service contains no Philippine wallet. (Republic Act No. 11127, sections 4–6 and 10; BSP Circular No. 1049, section 1; BSP Circular No. 1166, sections 1–2; BSP Memorandum No. M-2026-030, 24 June 2026.)
Philippine data law also requires a distinct assessment. Section 4(g) of the Data Privacy Act addresses data originally collected from foreign residents in accordance with foreign law. The implementing rules place the burden of establishing that law on the party invoking the exception, limit its reach, retain security obligations and preserve compatible rights and principles. This is not a company-wide exemption for overseas payroll processing. Philippine personnel and locally collected customer data require their own analysis. (Republic Act No. 10173, sections 3–4 and 6; Implementing Rules and Regulations of Republic Act No. 10173, sections 5(f) and 6.)
UK entry and later direct distribution
Launch A with one employer in England and Wales, employer funding, employer-paid charges, a fully authorised UK payment institution and the defined Philippine software role. Use an employer-controlled payment-authorisation process and direct bank payouts. The first employer supplies a known payroll timetable, approved work records and identifiable dispute owners. This reduces the facts and systems that must be controlled; it does not create an exemption from law.
Direct-to-consumer distribution changes the premises. A payslip or bank feed does not authorise the app to discharge an employer’s wage debt or bind the employer to collect a balance. Paying an employee from provider funds against repayment from the next salary is an employee financing arrangement requiring its own credit analysis. Bank-account feeds may add account information services, and credit advertising and introductions require separate promotion and broking analysis. A direct service also loses any employer-connected exemption condition it cannot satisfy. (Regulated Activities Order 2001, articles 36A, 60B, 60F(7B)(b) and 60L; Financial Services and Markets Act 2000, section 21; Payment Services Regulations 2017, Schedule 1, paragraph 1(h).)
The launch contracts should comprise the employer-fintech software agreement, the employer-payment-provider account and execution agreement, any necessary partner outsourcing agreement, employer-employee early-pay terms, and the data-processing and transfer instruments. Together they should state who owes wages, who pays fees, who can authorise money movement, when wages are discharged, how errors and disputes are resolved, and how payroll continues after a party fails. The employee terms should preserve voluntary use and explain the reduced payday balance without inventing a fintech repayment debt.
Before release, assemble evidence that those terms match the system: the partner’s current register entry and limitations; the approved money and data flows; bank and API access rights; the wage calculation specification; employee notices and deduction documents; transaction and payroll samples; complaint routing; the transfer assessment; and tested recovery and exit procedures. Include successful, pending, failed, duplicate, corrected, disputed, leaver and insolvency scenarios. The evidence must establish that payroll money cannot enter the fintech’s lending or operating accounts.
Questions for the payment partner and, where appropriate, the FCA should identify each Schedule 1 service, the supplier, the account holder and the person entitled to instruct it. Ask whether the proposed interface is technical support, regulated outsourcing or agency, and whether initiation or account information is present. For B or C, ask which entity enters and holds the employee credit agreement, which exemption is claimed, and how fees and intermediary permissions are treated. A lender or payment-provider certificate without its product scope cannot answer those questions. Payroll counsel and HMRC should address wage discharge, deductions, minimum pay, statements and the actual regulation 67BD predicates.
Changes requiring a fresh decision include provider funding against employee repayment, personal recourse for employer default, future-shift advances, mandatory employee charges, employee guarantees, wage assignments, refinancing, autonomous payment instructions, custody, wallets and direct distribution. Each change can remove a premise supporting A even where the app’s branding is unchanged. The company should permit it only after the affected contracts, law and operating controls have been reassessed.
Before entering another market, repeat the analysis for the local borrower and credit definitions, fee and subscription rules, employer exemptions, wage-payment and assignment law, deductions and minimum pay, tax reporting, payment services, stored value and safeguarding. Recheck the partner’s territorial permissions, agent and outsourcing routes, local establishment requirements, consumer language and complaints, collection practices, privacy roles and international transfers. Within the UK, employment expansion into Northern Ireland needs its separate employment-law review. The defined A is the starting product; expansion should preserve its obligations deliberately or adopt and resource a different regulated structure.