Full payload

Every FarPay element in a single payload

Full payload

A single payload exercising every element defined in FarPayType. All children are optional — this example is intentionally exhaustive and would rarely be sent in full.

<ExtensibleContent>
  <FarPay>
    <!-- General (OIOUBL / OIOXML) -->
    <CustomerNumber>ABCDE0123456</CustomerNumber>
    <PaymentReference>REF-2026-001</PaymentReference>
    <PaymentTypes>Card,MobilePay</PaymentTypes>
    <TextLines>Monthly subscription fee</TextLines>
    <CaptureAmount>125.75</CaptureAmount>
    <OrderToken>9f8c2b1a-4d3e-4c7a-9f11-2b6d8e0a1c34</OrderToken>
    <Brand>FarPay</Brand>
    <PaymentDueDate>2026-12-31</PaymentDueDate>
    <LanguageCode>DA</LanguageCode>
    <Ssn>0101801234</Ssn>

    <!-- Shared (OIOUBL / OIOXML / Bill) -->
    <Reminder>1</Reminder>
    <DeliveryMethod>Default</DeliveryMethod>
    <MarkedAsPaid>2026-06-01</MarkedAsPaid>
    <PaymentMethod>Automatic</PaymentMethod>
    <Template>welcome</Template>

    <!-- Bill only -->
    <SendingInvoiceChannel>
      <ChannelType>Email</ChannelType>
      <ChannelAddress>[email protected]</ChannelAddress>
      <Notes>Send after 09:00</Notes>
    </SendingInvoiceChannel>
    <Payout>
      <ReceiverIdentifier scheme="BANK">1234:567890123</ReceiverIdentifier>
      <SenderIdentifier scheme="BANK">4321:987654321</SenderIdentifier>
    </Payout>
    <PaymentStatus>Pending</PaymentStatus>
  </FarPay>
</ExtensibleContent>

📘
Element order is shown grouped for readability only. Because FarPayType uses xs:all and readers look up children by local name, any order is valid.

🚧
PaymentMethod and Payout interact: to trigger the FarPay Bill payout flow, set <PaymentMethod>Payout</PaymentMethod> alongside the Payout block. This full example uses Automatic for illustration.