Child pages
  • Online registration of AvtaleGiro

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. The customer creates an order, containing an item that requires AvtaleGiro, via a webpage that uses the BRP REST-API. For examples see: Examples for commonly used methods
  2. The customer pays for the order (preferably using: The payment webservice in BRP)
  3. The online registration link is fetched from the REST-API using generateregisteravtalegirolink. The desired page, for the browser to go to after registration, is entered as callbackurl. This page should be able to handle success and error cases, described later.
  4. The browser, of the customer, is redirected to the returned link
  5. The customer will then be presented with Nets online registration of AvtaleGiro and is prompted to enter account number and use Bank Id to verify its identity. (There is also an option to print a prefilled form that the customer should to send to Nets via mail).
  6. BRP will handle the result of the registration and then the browser will be redirected to the callbackurl that was entered in step 3.
  7. The AvtaleGiro information stored in BRP can then be fetched and presented to the customer. Note that the account information is sent from Nets to BRP by file later so it will take a couple of days before the account information is up to date in BRP.

...

  1. Get the link to where the browser should be redirected, see generateregisteravtalegirolink
Code Block
POST:APIURL/generateregisteravtalegirolink.json
{

   "companyid"=4
   "callbackurl"="http://abc.de"
   "apikey"="338934897438"
}
 
Response json: 
{
    "url": "http://some.url.se/brponline/external/avtalegiro/register?callbackUrl=http%3A%2F%2Fabc.de&customerid=82&companyid=4&hash=someSecretHashGeneratedByBrp"
}

...