Default API and third-party
integrations offering

This document is created to present what's included in our standard API and third-party systems integration procedures. It aims to clearly define which services are included and which are out of the default scope of work.

We have several goals for the API and third-party systems integration procedure:

• Ensure that the client understands the required effort that is needed to set third parties up and manage them.
• Clearly define responsibility zones and requirements for successful integration.
• Ensure that the system communicates with the other parties as it was designed.

To make this happen, we outline all required services, expectations, and deliverables.

We are happy to adjust those to the client's unique needs and guide them through technical difficulties. As those needs are mostly individual, we can estimate them precisely after several technical discovery sessions that need to happen in the first two weeks of our cooperation.

Our default payment gateway is Stripe. We prefer this provider because of the swiftness of integration and the ability to accept most payment methods.

Here are the requirements for the integration services rendering:

• Stripe account should be set up by the client.
• Client should pass the verification, AML, and KYC processes.
• Client should set up all content that is needed to facilitate business processes, like subscriptions, invoicing, payouts, etc.
• Client should invite a member of bn to the Stripe team with a Developer role.

If requirements are met, we provide the following services and deliver the subsequent outcomes:

• We integrate the payment gateway per requirements on the code level based on the official documentation provided by the gateway.
• We ensure proper data transfer between the system and the gateway in test mode.

The client gets:

• Codebase that facilitates data transfer.
• Secrets are managed the same way they are managed across the system.

• The sole client is responsible for operating, managing, and controlling the external system after project handover.
• BN Digital can not bear responsibility for the external system operations. This means if the external system misses SLA (like delivering emails, processing the payment, etc.), we will be unable to fix it on our side.
• BN Digital can not bear responsibility for any changes in external system operations after the start of the integration process. This means if the external system changes its API, documentation, or the way it functions, all subsequent changes are subject to the additional scope of work.
• The external system has its own restrictions that could impact designs and requirements for successful integration.
• The external system has its own pricing and fee structure, and BN Digital does not bear responsibility for such payments or changes in terms.

We are happy to consult and help in setting up and configuring the external system on a consulting basis that is out of the default scope of work.