How it works

Before integration

Before you start integration, you'll need to design your protection program. This will involve decisions about which products to offer protection for, what type(s) of protection (accidental damage protection, theft protection, extended warranty protection, etc.) to offer, what term lengths and payment cycles to provide, and how much commission to charge. You can also decide what you want to call your protection program, develop your key messages, and apply your brand colours as well as other design elements.

Your Hakuna Account Manager will work with you throughout the design process to ensure that you always find the best solutions for your business.

Integration

Our integration paths vary depending on:

• the timing of the transactions (concurrent, i.e. the protection is sold at the same time as the product, or post-purchase, i.e. the protection is sold after the product)

• the payment processor (either you or Hakuna)

Your Hakuna Account Manager will help you find the integration path that best suits your desired setup, technical capabilities, and available resources.

Here's an overview of our available integration paths:

Integration path	Transaction type	Payment processor
ERP-only integration	Concurrent	Merchant
ERP + E-commerce integration	Concurrent	Merchant
ERP + E-commerce client integration	Concurrent	Merchant
Frontend widget integration	Concurrent	Hakuna
Post-purchase integration with Hakuna Redirect	Post-purchase	Hakuna

The concurrent, merchant payment processor use case

We have multiple integration paths available for this use case. They all achieve the same outcome (enabling customers to purchase protection alongside protectable products), but differ in terms of the depth of integration and the resulting division of the following responsibilities between you and Hakuna:

• Add protection plans to your ERP system - Make protection plans available in your inventory (see ERP design for more information).

• Map the plans to your products - Connect your products with the corresponding protection plan in your inventory (i.e., using a custom property).

• Present plans to your customers - Display the protection plans to your customers alongside the protectable product(s) so they can add it as an opt-in.

• Manage the cart - Add an item representing the selected protection plan to the cart alongside the protected product, and then keep the quantity of the protection plan item in sync with that of the protected product, even if it is zeroed out (i.e., removed from the cart).

• Track the connection between products and plans - Keep track of which protection plans were added to which protectable products in order to identify the required cart management actions after any cart updates.

• Share order events - Notify Hakuna of successfully placed orders and share the respective order ID so Hakuna can connect cart and order data.

Here's an overview of the responsibilities associated with each integration path for this use case:

Integration path	Merchant responsibilities
ERP-only integration	Adding protection plans to ERP Mapping plans to products Presenting plans Managing cart Tracking connection between products and plans Sharing order events
ERP + E-commerce integration	Adding protection plans to ERP Presenting plans Managing cart Sharing order events
ERP + E-commerce client integration	Adding protection plans to ERP Managing cart Sharing order events

After integration

Having protection plans within your transactions and sharing data with Hakuna will likely have some impact on your billing and data protection practices. Please visit our Resources for more details on the required actions.