Advanced features

​This section will go through some of the more advanced features within e-Boks and Nets Share, such as Payments, Realtime delivery and two way communication 'Secure Dialogue'.

Payments in e-Boks

The payment feature in e-Boks allows the sender to activate a payment button in e-Boks, allowing the recipient to pay a bill directly in e-Boks.
The payment can be made via BetalingsService and/or via DIBS cardpayment.

The sender sends an extra xml file with the shipment zip file that includes the payment details for a message which needs the function active. Hence if there are three messages in a shipment, and two of them needs the e-Boks payment feature active, the zip file with include 3 PDF’s + 1 shipment.xml + 2 payment.xml (and x amount of attachment PDF’s).

To activate the payment feature in the shipment.xml an extra line in each required message is needed referring to a payment.xml file. Also, a special material id from e-Boks is required which is ordered through the Nets Share support team.

The extra tag for allowing payments in e-Boks in the shipment.xml is <paymentAttachment path="eBoksPayment.xml" /> which is to be added under the document tag, se below example:


 

<?xml version="1.0" encoding="UTF-8"?>
<shipment xmlns:eboks="http://www.nets.eu/nets-share/1.6/eboks"
          xmlns:print="http://www.nets.eu/nets-share/1.6/print"
          xmlns="http://www.nets.eu/nets-share/1.6">
    <shipmentInfo>
        <shipmentId>paymenttest1</shipmentId>
        <sender>
            <corporateIdentityNumber>12345678</corporateIdentityNumber>
            <country>DK</country>
        </sender>
    </shipmentInfo>
    <messages>
        <message id="paymenttest1">
            <sender>
                <senderName>Nets</senderName>
                <corporateIdentityNumber>12345678</corporateIdentityNumber>
                <eboks:eboksId>12345</eboks:eboksId>
            </sender>
            <eboks:receiver>
                <eboks:personIdentityNumber>123456781234</eboks:personIdentityNumber>
                <eboks:country>DK</eboks:country>
            </eboks:receiver>
            <eboks:config>
                <eboks:description>payment test 1</eboks:description>
            </eboks:config>
             <document>
                <documentType>123456</documentType>
                <filepath>document_0-60.pdf</filepath>
                <paymentAttachment path="EboksPayment1.xml"/>
            </document>
        </message>
	</messages>

</shipment>


 

The filename format for the extra xml is eBoksPaymentX.xml the X can be a number or blank, allowing for several different payment xml’s in the same shipment zip, as each file is uniquely related to each bill/invoice the recipient must pay.
Please see e-Boks guide for payments including an XSD in their PDF in the example file provided under Example Package & XSD’s in the left-hand menu.
An example of the payment xml can be found below.

<?xml version="1.0" encoding="UTF-8"?>
<EboksPayment xmlns="urn:eboks:invoice:2.0.0">
  <PaymentDemand>
    <Amount>99.99</Amount>
    <DueDate>2019-03-01</DueDate>
    <Currency>DKK</Currency>
    <CustomerId>0123456</CustomerId>
    <InvoiceId>12345678</InvoiceId>
    <OverdueDaysLimit>5</OverdueDaysLimit>
  </PaymentDemand>
  <Reminder>
    <DaysUntilOpeningReminder>5</DaysUntilOpeningReminder>
  </Reminder>
  <PaymentOptions>
    <DIBS>
      <MerchantId>CUS01</MerchantId>
      <BankPaymentId>12345678</BankPaymentId>
      <SubscriptionId>012345678912345</SubscriptionId>
      <SubscriptionText>Test Giro</SubscriptionText>
    </DIBS>
    <BetalingsService>
      <PbsNo>01234567</PbsNo>
      <DebGrp>00001</DebGrp>
      <CustomerNo>0123456</CustomerNo>
      <Fik>
        <FiType>+71</FiType>
        <FiPaymentId>000000012345678</FiPaymentId>
        <FiCreditorId>12345678</FiCreditorId>
      </Fik>
    </BetalingsService>
  </PaymentOptions>
</EboksPayment>

Depending on which payment options the sender allows and has deals with either the DIBS or BetalingsService parts of the xml can be omitted.
Receiving the payment information is for BetalingsService via the normal 602 file from BS and pay out via normal BS procedure. From DIBS payment data can be received from them, and the money paid out to the company bank account, according to the E-commerce aquiring agreement with Nets/Teller.
Screenshots of how the recipient payment flow is in e-Boks via browser can be seen below:

Betalingsservice:
payment_BS_flow.png

DIBS:
DIBS_payment_flow.png

Realtime (under development - release April 2019)

Realtime tranactions are usefull for customers who want to deliver documents to customers in e-Boks within few seconds.
Please note that we recommend the sender to not include more than max 50 messages per shipment zip when using realtime to secure swift handling and replies.
Realtime does not nessesarily require extra development, if needed a Material id can be registered in Nets Share as being for Realtime transactions only and hence automatically handled as such.

If the sender wishes to control if a transaction/message is to be delivered as realtime the below extra line in the shipment.xml can be added in the eboks:config section <eboks:realTime>true<eboks:realTime>

 

<?xml version="1.0" encoding="UTF-8"?>
<shipment xmlns:print="http://www.nets.eu/nets-share/1.6/print" xmlns:print-nordic="http://www.nets.eu/nets-share/1.6/print-nordic" xmlns:eboks="http://www.nets.eu/nets-share/1.6/eboks" xmlns:email="http://www.nets.eu/nets-share/1.6/email" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.nets.eu/nets-share/1.6">
  <shipmentInfo>
    <shipmentId>shipmentId1</shipmentId>
    <sender>
      <corporateIdentityNumber>12345678</corporateIdentityNumber>
<country>DK</country>
    </sender>
  </shipmentInfo>
  <messages>
    <message id="MessageID1">
      <sender>
        <senderName>sender</senderName>
        <corporateIdentityNumber>12345678</corporateIdentityNumber>
	<eboks:eboksId>15723</eboks:eboksId>
	  </sender>
      <eboks:receiver>
	<eboks:personIdentityNumber>1234561234</eboks:personIdentityNumber>
        <eboks:country>DK</eboks:country>
      </eboks:receiver>
      <eboks:config>
        <eboks:description>realtime test</eboks:description>
        <eboks:realTime>true</eboks:realTime>
      </eboks:config>
      <document>
        <documentType>172788</documentType>
	<filepath>Testdokument.pdf</filepath>
      </document>
    </message>
  </messages>
</shipment>