LogoLogo
Connect
Connect
  • 🏑Welcome to LHV Connect API
  • πŸ“ΊNews and Updates
    • πŸ“ˆPerformance and Stats
    • πŸ””Notice of Change
  • 🧭Quick Start Guide
  • πŸŽ₯Connect Fundamentals
    • Authentication and Certificates
    • Environments
    • Messaging Pattern
    • Service Provider model
    • Technical limitations
    • Encoding and Languages
    • Response Compression
    • Dates and Time Zones
    • Response Codes and Error handling
    • Onboarding
    • Live Proving
    • LHV UK and Estonia integrations
    • FAQ and Tips
  • πŸ“–Service Catalogue
    • πŸ’šHeartbeat
      • Heartbeat - GET
      • Heartbeat Advanced - GET
    • πŸ“©Messages Services
      • Get next message
      • Get list of messages
      • Get list of messages V2
      • Get message by response ID
      • Count number of messages
      • Mark message as processed
      • Mark batch of messages as processed
      • Mark batch of messages as processed V2
      • Messages Metadata
      • Get compressed message for testing
    • πŸ’°Account Information Services
      • Account Balance
      • Account Statement
      • Transaction Notification
        • Incoming Bacs Credit Notification
    • πŸ’ΈPayment Initiation Services
      • Pain.001.001.09
      • Pain.002.001.10
      • Samples
      • Authentication methods
      • Payment Scheme Selection
      • Payment Return Initiation
      • Payments Service Idempotency
      • Payments Originating Overseas
      • Legacy documents
        • pain.001.001.03 format
    • βœ…Confirmation of Payee Services
      • Confirmation of Payee - Requester
      • Confirmation of Payee - Responder
    • πŸ˜Άβ€πŸŒ«οΈVIBAN Services
      • VIBAN Open
      • VIBAN Bulk Open
      • VIBAN Modify
      • VIBAN Info
      • VIBAN Close
      • VIBAN Notification
    • πŸ”—Indirect Scheme Access
      • Agency Account Synchronization
      • RTF - Routing Table Files message
      • 🧾Payment Collection Services
        • πŸ’·Bacs Direct Debit
          • Bacs Direct Debit Mandate Initiation Request
          • Bacs Direct Debit Mandate Initiation Response
          • Bacs Direct Debit Mandate Initiation Response Confirmation
          • Bacs Direct Debit Mandate Cancellation Request
          • Bacs Direct Debit Mandate Cancellation Response
          • Direct Debit Incoming Collection Notification Request
          • Direct Debit Collection Notification Response
          • Direct Debit Collection Notification Response Confirmation
          • Direct Debit Reversal Notification Request
          • Examples
    • πŸ“¨Webhooks
      • Webhook Format and Processing
      • Managing Webhook Configurations
      • Webhook Security
      • Webhook Metadata
      • Full Bodied Webhooks
  • πŸ—“οΈReference
    • Glossary
    • Code Reference Tables
      • Balance Type Codes
      • Credit and Debit Transaction Codes
      • Payment Scheme Codes
      • Direct Debit Scheme Codes
      • Payment Reject Codes
      • Payment Return Codes
      • Bacs Direct Debit Mandate Reject Codes
      • Bacs Direct Debit Reject Codes
      • Bacs Direct Debit Reversal Reason
      • Bank Transaction Codes
      • Transaction Purpose Codes
      • Category Purpose Codes
      • Private Person Identification Codes
      • Organisation Identification Type Codes
      • Payment Priority Codes
      • Charges Bearer Codes
  • ☎️Support
    • Contact
Powered by GitBook
On this page
  • Message Format
  • Error Handling:

Was this helpful?

  1. Service Catalogue
  2. Payment Initiation Services

Payments Originating Overseas

Describing the details and requirements for FPSPOO (Faster Payments - Payments Originated Overseas)

PreviousPayments Service IdempotencyNextLegacy documents

Last updated 1 month ago

Was this helpful?

Faster Payments (FPS) Payments Originated Overseas (POO) refers to an extension of the UK's Faster Payments system, which is designed to allow overseas-originating payments to be processed through the Faster Payments infrastructure. This type of payment involves sending funds to the UK, where the original transaction occurs outside the UK but the payment is processed through Faster Payments.

A Payment Originating Overseas (POO) is a payment originally drawn on an account held outside the UK and a transaction which is believed to be subject to the Money Laundering and Terrorist Financing and Transfer of Funds Regulations 2017. Within the FPS scheme, the location of the payment service provider is based on the location of the account of the Ultimate Remitter. If the Ultimate Remitter account is outside of the UK (For example the EEA or the Americas), the payment would be classified as a POO and must be treated accordingly in line with FPS principles. All FPS payments (including POO) can only be sent to an Ultimate Beneficiary account deemed within the UK.

In determining the location of an account, the following will be relevant:

  • The jurisdiction where the institution providing the account is licensed;

  • The physical location of the institution providing the accounts;

  • The governing law of the terms of the account with its client.

Below is a flow to help determine whether you are candidates of a potential Payments Originating Oversees payments.

When defining the location of the accounts which you offer we recommend that you obtain your own legal advice. If there is a variance in either: the jurisdiction in which you are incorporated and regulated or the location of the accounts your business offers please contact your Relationship Team to discuss.

Message Format

For LHV to to correctly identify and process an FPSPOO transaction, the following criteria must be met based on the pain.001.001.09 format:

  1. ID1 - Initiating Party: Non-UK Initiating Party Country:

    • Where the initiating party is not UK, Country code and BIC off the initiating party needs to be included.

    • Ultimate debtor information to be completed - BIC of initiating party and unique reference (User/Reference)

  2. ID2 - Forwarding Party Field: Non-UK Forwarding Party Country.

    • Where the Forwarding party is not UK, Country code and BIC off the initiating party needs to be included.

    • Ultimate debtor information to be completed - BIC of forwarding party and unique reference (User/Reference)

  3. ID3 - Ultimate Debtor Fields:

    • Ultimate remitter information:

      • Full legal name;

      • Address;

    • Organisation Identification:

      • BIC. Must be owned by the institution which provides the account to the Ultimate remitter and must be a non-GB BIC;

      • Ultimate remitter’s account number or payment reference. Can be IBAN or in another format.

INITIATING PARTY NAME

GrpHdr.InitgPty.Nm

INITIATING PARTY POSTAL ADDRESS

FORWARDING AGENT NAME (if nested)

GrpHdr.FwdgAgt.Nm

FORWARDING AGENT POSTAL ADDRESS (if nested)

ULTIMATE DEBTOR NAME

PmtInf.UltmtDbtr.Nm

ULTIMATE DEBTOR POSTAL ADDRESS

ULTIMATE DEBTOR BIC

PmtInf.UltmtDbtr.Id.OrgId.AnyBIC

ULTIMATE DEBTOR ID

PmtInf.UltmtDbtr.Id.OrgId.Othr.Id

Error Handling:

FPSPOO payments cannot be sourced from the UK or its crown dependencies so will be rejected if:

a) Ultimate Debtor BIC is a UK/GI/JE/IM/GG BIC

b) Ultimate Debtor ID is a UK/GI/JE/IM/GG IBAN

GrpHdr.InitgPty.PstlAdr See for more details.

GrpHdr.FwdgAgt.PstlAdr See for more details.

PmtInf.UltmtDbtr.PstlAdr See for more details.

πŸ“–
πŸ’Έ
Address structure
Address structure
Address structure