Skip to content
brite docs
  • Technical Documentation
    Implementation Guidelines
    Implementation Guidelines

    Detailed guidelines on how to do a technical integration with Brite

    Read more

    Developer API image
    Developer API

    Technical documentation needed for offering the Britest payment solutions

    Read more

  • Checkout Guidelines
  • Marketing Guide
  • Implementation Guidelines
  • Developer API
  • Checkout Guidelines
  • Marketing Guide
  • FAQS
FAQS
Implementation Guidelines
  • Implementation Guidelines
Products
  • Brite Play
  • Brite Instant Payins
  • Brite Instant Payouts
  • Brite Data Solutions
Authorize as a merchant
  • Generate Token
  • Renew token
Brite Play
  • Brite Play
Brite Instant Payins
  • Brite Instant Payins
  • Recurring Deposits
  • Approve/Reject Deposit After Merchant Internal Check
Brite Instant Payouts
  • Brite Instant Payouts
  • Withdrawals using the Brite Client
  • Withdrawals using API-only
  • Create Reference Withdrawal
  • Time 2 Money (Withdrawal ETA)
  • Approve/Reject Withdrawal After Merchant Internal Check
KYC
  • KYC
Brite Blended
  • Brite Blended
Bank Account Selection
  • Create Bank Account Selection Session
Client Authentication
  • Create Authentication Session
Rendering the client
  • Rendering the client
Session handling
  • Session handling
Transaction handling
  • Transaction Handling
Check balance by API
  • Check balance by API
Http callbacks
  • Http Callbacks
Customer management
  • Customer management
Bank account management
  • Bank account management
Export functionality
  • Export to CSV
Error simulation in Sandbox
  • Erros Simulation in Sandbox
Error Codes
  • Aborted state errors
Brite in different Countries
  • Brite in different Countries
Brite on Native App or Mobile
  • Brite on Native App or Mobile
Brite integration test and verification
  • Brite integration test and verification
  • Home
  • Implementation Guideline
  • Brite integration test and verification
  • Brite integration test and verification

Brite integration test and verification

Table of Contents
  • Sandbox Testing
  • How to test
  • Production Testing

When integrating the Brite client, we would recommend testing the following OS and browser combinations to cover the majority of user cases:

  • Windows + Chrome
  • Windows + Firefox
  • Windows + Edge
  • Mac + Safari
  • iOS + Safari
  • iOS + Chrome
  • Android + Chrome

Sandbox Testing #

The following scenarios are recommended to test before moving from the Sandbox environment to the Production environment.

Users

  • New user
  • Returning user
  • Get KYC (Brite Play)

Deposits

  • Successful deposit
  • Failed/aborted deposit
  • Merchant approval/rejection of a deposit session
  • Ensure callbacks are successful

Withdrawals

  • Create bank account
  • Successful withdrawal
  • Failed/aborted withdrawal
  • Merchant approval/rejection of withdrawal
  • Ensure callbacks are successful

Client

  • Verify size so whole client is visible and there is no scrollbars
  • Client boarder
  • Remember Me function in the client.
  • Client Close and Exit buttons.

How to test #

Aborted session/transactionPass ‘aborted’ in the merchant reference field.
OR
1. Start the Brite payment flow using the client
2. Authenticate
3. Close the page or wait until timeout
Failed sessionPass ‘failed’ in the merchant reference field.
Failed transactionPass ‘completed’ in the merchant reference field, making the transaction never move past the Completed state. The transaction will automatically fail after some time
Multiple usersSweden: By entering any valid Swedish personal number a new customer is created.
Finland: Using numbers 0-9 as the first character in the username will create unique users. See “Test users Finland” document.
Using the Test Bank●  Fail after login
●  Abort if no funds
●  Complete with KYC
●  Incomplete KYC
●  Aborted Risk Engine
●  Fail Transaction

Production Testing #

Before going live to all users, Brite will require that a couple of production test transactions, both deposits and withdrawals, are done and verified OK. Please ensure the end user balance is credited correctly. Please provide a screen recording of the testing, both deposit and withdrawal, with Brite. With that we can verify that the sizing of the client etcetera is optimized.

If applicable, we will be checking Brite’s positioning on the cashiers between the competitors as per contractual agreement.

What are your Feelings
Still stuck? How can we help?

How can we help?

Updated on June 29, 2022
Table of Contents
  • Sandbox Testing
  • How to test
  • Production Testing

Brite
Linnégatan 5
114 47, Stockholm
Sweden

Phone: +46101888777

Brite

  • About Us
  • Careers
  • Cookies

Technical Documentation

  • Developer API
  • Implementation Guidelines

Marketing Guide

  • Assets
  • User Information

Checkout Guidelines

  • Checkout Guidelines

Contact

  • Merchant Support
  • Customer support
brite logomark gray
  • Privacy Policy
  • Terms & Conditions

Brite AB (corporate identity number: 559116-1632) is a licensed Payment Institution under the supervision of the Swedish Financial Supervisory Authority (Finansinspektionen). Brite AB provides payment services under the Swedish Payment Services Act (2010:751) as well as the EU Directive 2015/2366 about payment services in the internal market (PSD2) and has, upon notification, the authority to provide

YOUR COOKIE SETTINGS

We use cookies to provide the best experience.

 

You can find out more about which cookies we use, or switch them off by clicking `customise´. Here, you'll also find links to our Privacy Notice and Cookie Notice, which explain how we work with cookies and process your personal data.

 

Do you accept all cookies?

Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Strictly Necessary Cookies

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.

3rd Party Cookies

This website uses Google Analytics, Leadfeeder, Hotjar, LinkedIn and Meta pixels to collect anonymous information such as the number of visitors to the site, and the most popular pages.

Keeping this cookie enabled helps us to improve our website.

Please enable Strictly Necessary Cookies first so that we can save your preferences!

Cookie Policy

Download our Cookie Notice.