Assets

Automated Asset Delivery

Our Service Presentation API is designed to provide seamless access to image and text assets and help ensure an optimised checkout experience.

After all, a great user experience is key to encouraging customers to adopt Pay by Bank. By making the checkout process as simple and clear as possible, more people are likely to use it and stick with it.

Benefits

User
Experience

Simplify the checkout process to minimise confusion and enhance the overall user experience, for higher conversion rates.

Easy
Integration

Effortlessly integrate with minimal setup, reducing manual efforts and allowing for automated updates.

Continuous
Optimisation

Brite continuously refines assets, optimising the service presentation to boost adoption and conversion. Our integration ensures you stay future-proofed and benefit from ongoing UX enhancements.

API Documentation

Query Parameters

Parameter	Description	Requiered
merchant_id	Unique ID to identify your business. If you don’t know your merchant_id, contact the Merchant Solutions Team.	Yes
vertical	Business type. Options: ecommerce, gaming, marketplace, financialServices.	No
product_type	Type of product: payment, payout, ais, or play.	Yes
locale	Language code(ISO 639-1) + country code(ISO 3166-1 alpha-2). Example: en_BE.	Yes

API Request

Endpoint
GET /assets

Content-Type
application/json

				
					https://presentation.britepayments.io/v1/assets/?merchant_id=ag9ofmFib25lYS0yNDkwMDlyFQsSCE1lcmNoYW50GICAgKTihcsJDA&vertical=ecommerce&product_type=payment&locale=en_BE

API Response

				
					{"badge":"string","title":"string","tagline":"string","extended_descriptor_text":["string"],"bank_logos":["string"]}

Response Fields

Field	Description
badge	URL to SVG. Where possible, our badge should be displayed at no less than 24px in height to ensure sufficient legibility.
title	Title of the service.
tagline	Brief description of the service.
extended_descriptor_text	Array of strings with detailed information.
bank_logos	Array of URLs to SVG.

Response Codes

Response Code	Description
200 OK	Successful request with the requested data.
400 Bad Request	Invalid request due to missing or incorrect query parameters.

Usage Tips

Include all required parameters in your request.
Use correct ISO codes for country and language fields.
The vertical parameter is optional but helps tailor the response.
We recommend triggering the Service Presentation API in real-time, specifically upon the page-load of your checkout. This approach guarantees that the latest assets are fetched and displayed to the user immediately as they reach the checkout. Implementing the API call at this point ensures that the assets are fully loaded and ready, providing a seamless and enhanced user experience without delays.

Error Handling

For 400 errors, check for missing or incorrect fields.
Contact the Merchant Solutions Team for any other issues.

On this page