implementation guide for electronic contract signature ... · marketing materials. to create a qr...
TRANSCRIPT
Page 1 of 10
Implementation guide for
Electronic Contract Signature with
AvtaleGiro and eFaktura
Version 1.3
Date 13.06.2018
Page 2 of 10
Contents 1 Introduction ................................................................................................................................................... 3
1.1 The service in brief ................................................................................................................................ 3
1.2 Target group .......................................................................................................................................... 3
1.3 Contact information .............................................................................................................................. 3
1.4 Relevant documentation ....................................................................................................................... 3
1.4.1 Nets documentation ......................................................................................................................... 3
1.4.2 External documentation ................................................................................................................... 3
2 Implementation ............................................................................................................................................. 4
2.1 Introduction .......................................................................................................................................... 4
2.2 Integration............................................................................................................................................. 4
2.2.1 Integration with website and provision of link (URL) to application ................................................ 4
2.2.2 Information in link (URL) to application ............................................................................................ 5
2.2.3 Return page from application ........................................................................................................... 7
2.3 Self-test ................................................................................................................................................. 8
2.4 Contract signature ................................................................................................................................. 9
2.5 Start-up ................................................................................................................................................. 9
3 Follow-up activities ...................................................................................................................................... 10
3.1 Marketing ............................................................................................................................................ 10
3.2 Customer service ................................................................................................................................. 10
Page 3 of 10
1 Introduction
1.1 The service in brief
Electronic contract signature is an add-on to AvtaleGiro and eFaktura B2C that allows payers to enter into an
agreement for the relevant services via the payee using BankID and Mobile BankID. Contract signature is
performed directly with Nets via a web application. The application can be integrated with the payee’s website
or opened directly by the payer.
1.2 Target group
This documentation is intended for companies that plan to implement the solution.
1.3 Contact information Customer service: [email protected] and tel. 915 04949
1.4 Relevant documentation
1.4.1 Nets documentation
Documentation maintained by Nets:
► User guide for Electronic Contract Signature
► http://www.avtalegiro.no/Bedrift/Markedsmateriell/Logoer/
► http://efaktura.no/Forside-eFaktura/bedrift/Markedsmateriell/Logoer/
1.4.2 External documentation External documentation (Nets is not responsible for the content of external documentation):
► http://en.wikipedia.org/wiki/Percent-encoding
Page 4 of 10
2 Implementation
2.1 Introduction Implementation is carried out in four steps:
► Integration with customer database/accounting system and website
► Self-test of integration with Nets application
► Contract signature with own bank including desired start date
► Provision of link to the application for customers on start-up
2.2 Integration
2.2.1 Integration with website and provision of link (URL) to application
For a company to allow its customers to enter into an agreement electronically, it must direct the customer to
the application with information about the payer and payee. This is done by the company generating a URL
dynamically with (http get) parameter values. The information to be sent to the application via the URL should
be unique for each customer. The customer must therefore be identified and correct information retrieved
from the accounting system for the company. The URL may be passed to the customer, e.g. via the company’s
website or as a QR Code on a paper reply slip or invoice.
a) Provide link via company’s website
When the link is provided via the company’s website, this is best done via “My Page” or after registration
as a new customer so that the company can link the customer to the correct information in the customer
database and/or accounting system. The company’s website provider is best placed to customise the web
pages for this. If desired, Nets can arrange contact with one of its partners to assist with this part of the
integration.
b) Other provision of link directly to the customer
The company may also provide the link to the application directly to the customer by e.g. e-mail, SMS or
as a QR code.
A QR code is particularly suitable for communicating long URLs on paper – e.g. reply slip, invoice or
marketing materials. To create a QR code for the URL, you need a QR generator; there are many open-
source and commercial players on the market. The customer must still be identified so that correct and
unique information from the accounting system is in the URL.
Integration Self-testContract signature
Start-up
Integration Self-testContract signature
Start-up
Cont. on next page
Page 5 of 10
Cont. on next page
2.2.2 Information in link (URL) to application
To make it easy for the customer to enter into an agreement, the link must contain information about the
unique agreement from the company. The customer must therefore be identified in advance so that the
correct information can be retrieved from the accounting system/customer database and placed in the URL.
The URL for the application at Nets will vary depending on the services for which agreements are to be entered
into:
► AvtaleGiro: https://pvu.nets.no/pvu/pvu.do?
► eFaktura B2C: https://pvu.nets.no/pvuefaktura/logon.do?
► AvtaleGiro and eFaktura B2C: https://pvu.nets.no/pvuatgefa/atgefa.do?
NB: see self-test URL under 2.3 Self-test
The following information can be included in the URL (mandatory fields are marked with *):
Service Information element
Field name Example Comments
AvtaleGiro Company’s account number*
account 99990012345 Account number for which company has an AvtaleGiro agreement.
AvtaleGiro Company name* name Company_Ltd Name as registered by the company in its AvtaleGiro agreement.
AvtaleGiro Customer’s KID* kid 0123456789 The customer’s full KID with number of digits and modulus calculation in accordance with the company’s AvtaleGiro agreement.
AvtaleGiro Amount limit* limit 5,000 Suggested amount limit per month in whole kroner. We recommend that the suggested amount limit be no more than 2.5 times more than the amount stated in the invoice
AvtaleGiro Form (reply slip)
p n Ability to choose whether the payer should be able to print a form (reply slip) n = payer should not be able to produce a printed version of the form y = payer should be able to produce a printed version of the form
AvtaleGiro
How SignWeb should be displayed
wi f Ability to check the signature in the application to be made inside or outside of an iFrame r = open signature in an iFrame within the application (default) f = open signature standalone
Page 6 of 10
AvtaleGiro Indicates if the "Notice before payment" ( Ønsker varsel i forkant av betaling)
n Y Possibility to choose whether
the notification should be
displayed in the application. Y
= check box default Yes to pay
will be notified here must pay
self-opt-out notice By selecting
N = No for notice here, pay
must choose if they wish to be
notifiedis omitted in the
checkbox
eFaktura B2C Issuer ID* issuerid NOR999999999-1 Company’s ID for eFaktura B2C
eFaktura B2C BrandID* brandid 1 For companies that have more than one brand per issuer ID. The default is 1.
eFaktura B2C Customer’s eFaktura reference*
efakturaref 00012345 Customer’s eFaktura reference at the company.
eFaktura B2C Customer’s e-mail address
e-mail [email protected] Suggested e-mail address for notification of new eFaktura invoices to the customer.
All Return URL* url www.bedriften.no Return URL to which the customer should be returned. Must be the last parameter in the URL.
Special characters and spaces in the information elements must be URL-encoded in UTF-8 to be correctly
interpreted. Read more about URL encoding here:
http://en.wikipedia.org/wiki/Percent-encoding
Example of complete URL:
https://pvu.nets.no/pvuatgefa/atgefa.do?name=Bedriften%20AS&account=99990012349&kid=01234567892
&limit=5000&utstederid=NOR999999999-1&brandid=1&efakturaref=00012345&url=http%3A%2F%2Fwww%2
Eavtalegiro%2Eno
Page 7 of 10
URL for Mobile BankID
There are some restrictions on the number of characters for signing by FBOs with Mobile BankID. The
agreement is filled out with information from the following information elements: account, name, KID and
limit. The variable fields name (company name), KID and limit (amount limit) are therefore limited to 53
characters for the agreement to be valid. The agreement wording for Mobile BankID signature can be tested in
self-test.
NB: Some accounting systems may have a KID with 25 digits and the amount limit may be up to 6 characters.
Information element Field name Max. characters
Company name Name None
KID Kid 25
Amount limit Limit 6
2.2.3 Return page from application In the URL for the application, a return URL is defined for the customer to be directed to/from the application.
When the customer is sent to the desired URL (http redirect with URL parameter), this will be accompanied by
a “status” parameter that indicates whether the agreement was signed or not. Return URLs with status codes
can be used to provide selected information to the customer or to track contract signature, and for statistics.
It is recommended that the company’s website interpret the status code so that the customer is informed of
the desired action based on whether the agreement has been signed or not.
The following status codes have been defined:
Meaning Code
The agreement has been signed and will be created OK
Contract signature cancelled by the customer cancel
One or more subsystems are down error
Payer has printed form print
An example of a return URL might then be:
http://www.avtalegiro.no?status=ok
Page 8 of 10
2.3 Self-test
The company can perform a self-test of the integration to validate that essential information has been
included. The self-test can also be used to validate the length of the agreement signed with Mobile BankID and
return URLs with status codes.
The self-test is performed using the following URLs for the respective services:
AvtaleGiro: https://pvu-test.nets.no/pvutest/atgtest.do?
eFaktura B2C: https://pvu-test.nets.no/pvutest/efakturatest.do?
AvtaleGiro and eFaktura B2C: https://pvu-test.nets.no/pvutest/combinationtest.do?
Example of self-test URL:
https://pvu-
test.nets.no/pvutest/combinationtest.do?name=Bedriften%20AS&account=99990012349&kid=01234567892
&limit=5000&utstederid=NOR999999999-1&brandid=1&efakturaref=00012345&url=http%3A%2F%2Fwww%2
Eavtalegiro%2Eno
You can test the defined interpretation of status codes for return URLs by clicking on the desired status code to
open a return URL with a status code.
“Show example of mobile text” displays the text of the agreement signed by
customers with Mobile BankID. In order to enter into a valid contract, this may not
Integration Self-testContract signature
Start-up
Cont. on next page
Page 9 of 10
exceed 120 characters.
2.4 Contract signature
Before the service can be used, an agreement must be entered into with the company’s bank for each credit
account (AvtaleGiro) or CVR number (eFaktura B2C).
2.5 Start-up
On the desired start date, the application will be opened for use. The company can then change to the
production URL and provide a link via a web page or other desired channel.
Integration Self-testContract signature
Start-up
Integration Self-testContract signature
Start-up
Page 10 of 10
3 Follow-up activities
3.1 Marketing
It is advisable to make customers aware of the option of electronic contract signature in marketing on own
websites and through other channels.
The AvtaleGiro and eFaktura brands will be recognised by customers, thus strengthening customer confidence
in the service and increasing volumes. Logos may be downloaded here:
http://www.avtalegiro.no/Bedrift/Markedsmateriell/Logoer/
http://efaktura.no/Forside-eFaktura/bedrift/Markedsmateriell/Logoer/
3.2 Customer service
It is recommended that the company’s customer service be updated on how the application works. See user
guide for electronic contract signature for more information.