Embedding

How the FarPay payload is placed in OIOUBL, OIOXML, and FarPay Bill

Embedding

The same FarPay payload is placed differently depending on the inbound format. The examples below use the same payload so you can compare placement side by side.

OIOUBL

In OIOUBL the FarPay element lives directly inside UBLExtensions/UBLExtension/ExtensionContent (there is no ExtensibleContent wrapper). Read by OioUtil.HandleExtensibleContentFarPay.

<Invoice>
  <ext:UBLExtensions>
    <ext:UBLExtension>
      <ext:ExtensionContent>
        <FarPay>
          <CustomerNumber>ABCDE0123456</CustomerNumber>
          <PaymentReference>REF-2026-001</PaymentReference>
          <LanguageCode>DA</LanguageCode>
        </FarPay>
      </ext:ExtensionContent>
    </ext:UBLExtension>
  </ext:UBLExtensions>
  <!-- ... rest of the invoice ... -->
</Invoice>

OIOXML

In OIOXML the payload sits under an ExtensibleContent envelope. Read by OioUtil.HandleExtensibleContentFarPay.

<ExtensibleContent>
  <FarPay>
    <CustomerNumber>ABCDE0123456</CustomerNumber>
    <PaymentReference>REF-2026-001</PaymentReference>
    <LanguageCode>DA</LanguageCode>
  </FarPay>
</ExtensibleContent>

FarPay Bill

In the FarPay Bill format the ExtensibleContent envelope sits under PaymentMeans. Read by BillXmlReader.HandleFarPayContent / HandlePayout.

<Bill>
  <!-- ... invoice, customer ... -->
  <PaymentMeans>
    <PaymentChannelCode>DK:BANK</PaymentChannelCode>
    <ExtensibleContent>
      <FarPay>
        <CustomerNumber>ABCDE0123456</CustomerNumber>
        <PaymentReference>REF-2026-001</PaymentReference>
        <LanguageCode>DA</LanguageCode>
      </FarPay>
    </ExtensibleContent>
  </PaymentMeans>
</Bill>

📘
Namespaces and prefixes (e.g. ext:) follow the host document's schema. The FarPay payload itself is unqualified — readers match its children by local name.