You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Logo

Info
  • Offer your customers deferred payment, in 3X or 4X.
  • Fast journey and immediate response.
  • No supporting documents to process. The customer's card must be valid in the context of a refund.
  • 100% online via PC or tablet.
  • 100% Guaranteed: the merchant is protected against non-payment and fraud.
  • Settlement at Day + 2 maximum of the entire transaction.
  • Ability to configure automatic or manual capture




Sommaire







Payment journey 






*Steps 1 and 3 are performed via Axepta

** Eligibility is used to estimate the level of confidence assigned to a payment request by a customer.

This involves statistical processing of historical data relating to customer orders. Eligibility can be reassessed using information contained in the National Personal Credit Repayment Incident File (FICP).



Onboarding


After signing the contract

The merchant receives an email from 'Professional Services' Floa team, who will accompany him regarding FLOA implementation.

This team will be in charge of FLOA production plan .



Identifier : Sandbox/Production 


Once the technical configuration has been completed, FLOA sends the merchant an Excel file (see below) containing the recipe and production identifiers.


Exemple d'identifiant de recette et de production anonymisé


The key data to be used in queries are the MerchandID and the MerchantSiteID.


You will find below a short recipe description and production identifiers.


DATADetailAPI AXEPTA Mapping
MerchandID

Merchant ID created by FLOA platform - Optional data

MerchantIDExt
MerchantSiteID

Unique identifier created by FLOA for each of the payment methods purchased by the merchant (3X/4X/manual capture/automatic capture)

PayType
MIN  

Minimum customer Cart - Below this amount, payment cannot be made via FLOA

-
MAX

Maximum customer Cart - Beyond this amount, payment cannot be made via FLOA

-



FLOA registration request on Axepta


Once the Excel file has been received, the merchant sends it to his BNP Paribas account manager specifying the Axepta MerchandID.

Sharing this element is imperative so that BNP Paribas teams can proceed with the MerchandID configuration.



Onboarding on merchant website


Implementation of FLOA regulatory principles


FLOA provides merchants with a set of regulatory and marketing resources necessary due to legal obligations and optimize the conversion rate.

More information: Regulatory and marketing resources (lien a revoir) 


Once FLOA is integrated on the merchant site, the merchant contacts the marketing department of FLOA (marketing@floa.com) so that it can carry out the necessary checks to put in production.


FLOA must validate compliance with regulatory and marketing requirements in order to proceed with production environement.


Technical documentation


You will find the technical integration details in the following section: FLOA Pay Direct Integration - Documentation Axepta BNP Paribas - Axepta ( lien a revoir)


The FLOA Test contains test data as well as a step-by-step to perform a FLOA payment request



Recommendations


Standard case

You will find below the mandatory parameters to include in your request in order to calculate eligibility.

These parameters are used to calculate the customer score associated for each transaction.


ParamètresDescriptionLienFormat minimal préconisé
SalutationGender--
MaidenName

Maiden name - mandatory if Mrs Mrs

--
DateOfBirthDate of birth --
PlaceOfBirthDépartement de naissance --
CustomerHistory

Customer data


Customer History JSON Object
{
  "firstOrderDate": "01/01/2023",
  "lastOrderDate": "01/02/2023"
}
ProductDetailsCustomer cart dataProduct Details JSON Object
{
    "categorie1": "Categorie 1 de produit",
    "categorie2": "Categorie 2 de produit"
} 


Travel/Tourism

In addition, if the merchant  an activity related to tourism or travel, it is necessary to add the following parameters.

ParamètresDescriptionLienFormat minimal préconisé
ProductDetailsCustomer cart dataProduct Details JSON Object

Use the following values :

  • AIRLINE TICKET
  • TRAIN TICKET
  • BUS TICKET
  • HOTEL
  • CAMPING
  • STAY
  • CRUISE
  • CAR RENTAL
  • OTHER


{
    "categorie1": "AIRLINE TICKET"
} 
TravelDetails

Travel parameter: airline tickets, passport information, etc.

Travel Details JSON Object
{
  "insurance": "AXA",
  "travelType": "TwoWay",
  "departureDate": "21/11/2022 12:20",
  "returnDate": "14/12/2022 12:20",
  "destinationCountry": "FR",
  "ticketCount": 2,
  "travellerCount": 2,
  "travelClass": "Economy",
  "ownTicket": 1,
  "mainDepartureCompany": "CDG",
  "departureAirport": "cdg",
  "arrivalAirport": "dub",
  "luggageSupplement": "1"
}
StayDetails

Hotel services parameter

Stay Details JSON Object
{
    "company": "Ibis",
    "destination": "Dublin",
    "roomRange": 2
}



Country

Depending on contracted countries, additional parameters are mandatory.

You will find below a summary table listing the specific parameters for each country.

Paramètres API AXEPTABelgiumSpainItalyPortugal
Language

nl-BE

en-BE

es-ESit-ITpt-PT
AddrCountryCodeBEESITPT
PersonIDNAMandatoryMandatoryMandatory


You will find test PersonIDs in the section: Test FLOA


Recipe

FLOA test recommendation and prerequisites

During your testing activities we invite you to check that:

    • The MerchantIDExt and Paytype recipe fields are well informed.
    • The value of the Amount  field is between the minimum and maximum amount previously contractualized
    • The value of the Amount  field is the amount expressed in cents
    • The ProductDetails and CustomerHistory  fields contain base64-encoded JSON objects - Basics of Base64-encoding EN
    • The AddrCountryCode  parameter is populated
    • The Language  parameter corresponds to the country language 



Mise en production

La mise en production se déroule selon les étapes suivantes : 

  1. Validation fonctionnelle par FLOA
    1. L'équipe 'Professional Services' de FLOA, qui accompagne le commerçant dans la mise en place de FLOA, réalise un test jusqu’au paiement pour chaque solution intégrée sur le site marchand. Tous les produits seront testés.
    2. Ex : si le marchand a demandé du 3XG et 4XG, FLOA fera donc 1 test sur la solution 3XG et 1 test sur la solution 4XG.
  2. Validation Marketing par FLOA
    1. L'équipe Marketing de FLOA vérifie :
      1. Toutes les mises en avant de FLOA ou des solutions de paiement en plusieurs fois dans le parcours
      2. L’affichage des mentions légales dans les conditions générales de vente du commerçant
  3. Mise en production par le commerçant
    1. Le commerçant ouvre FLOA sur son site marchand
  • No labels