Where to start?

This part of the integration portal contains information about the invoice handling services Collector Bank provides. Below you'll find a step by step overview of the implementation process.

Further down we have a comparison of the B2C and B2B functionality, giving you a clear view of what differs between the two customer segments.

 
  1.  

    Integration type?

    First you'll need to decide which integration type to use. If you already have a platform up and running, you might want to check our list of pre-integrated modules. If you’re planning on integrating from scratch, you might want to check out our suggested integration packages.

  2.  

    Do we have an agreement?

    An agreement between you as a merchant and Collector bank must be signed. Keep in mind that your upcoming integration depends on what your agreement includes since we have a lot of functionality and products.

  3.  

    Install/Develop & Test

    Depending on which integration type you have chosen, the next step is to make sure that everything is installed and implemented the way you want it to be. For a module user this pretty much means installing it in you platform. For an API integration, you will actually need to develop the chosen functionality and make sure it runs smooth and is in sync with your own system. For module users, testing is optional, but for API integrations, the test step is mandatory.

  4.  

    Site inspection

    When everything's set up on your side, one of the Merchant Services integration managers will make a site inspection to make sure it's all good. If something need to change, we'll tell you, and if not, we'll of course tell you anyway! This inspection should be done on a dev site not accessed to the public.

  5.  

    Ready to rock & roll

    When the site inspection is done, we're ready to rock & roll! You can now put the site on your production domain and start selling stuff!

Are your customers both consumers and companies?

The invoice handling services for B2C and B2B are almost identically and you’re able to reuse most of your code and logic. This sounds like a typical sales pitch you might think, but please take a look at the table below where we’ve specified the differences. We would say that 90% of a B2C integration is reusable for B2B if done right from the beginning. 

FunctionCustomer typeHow it differs for B2B
GetAddress B2C
  • Not available for B2B
AddInvoice B2C/B2B
  • FirstName and Lastname must be left out
  • CompanyName must be assigned
  • The two optional parameters Reference and CostCenter can be used
  • Organization number is set in the RegNo parameter
  • Part payment products (InvoiceType 2, 4, 5) can’t be used
  • Gender is not used for companies.
  • InvoiceAddress/DeliveryAddress: As opposed to AddInvoice-requests for private customers, company invoice addresses and delivery addresses does not have to be the same for the purchase to be approved.
ActivateInvoice B2C/B2B -
PartActivateInvoice B2C/B2B -
CancelInvoice B2C/B2B -
ReplaceInvoice B2C/B2B -
SendInvoice B2C/B2B -
ExtendDueDate B2C/B2B -
CreditInvoice B2C/B2B -
PartCreditInvoice B2C/B2B -
AdjustInvoice B2C/B2B -
SetReservation B2C/B2B
  • FirstName and Lastname must be left out
  • CompanyName must be assigned
  • Organization number is set in the RegNo parameter
GetReservation B2C/B2B
  • Organization number is set in the RegNo parameter
CancelReservation B2C/B2B
  • Organization number is set in the RegNo parameter
GetAccounts B2C/B2B
  • Organization number is set in the RegNo parameter
GetAccountTransactions B2C/B2B -
GetCurrentInvoice B2C/B2B -

P.S. Keep in mind that to use both the consumer and company customer segment, your agreement need to include both.