Versions Compared

Old Version 4

changes.mady.by.user writer

Saved on

compared with

New Version 5

changes.mady.by.user writer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


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



Table of Contents





Payment journey 






*Steps 1 and 3 are performed via by 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

-




FLOAregistrationrequestonAxepta


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.



Warning

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)



Tip

The FLOA Test contains test data aswellas a step-by-steptoperformaFLOA 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


Code Block
languagejson
{
  "firstOrderDate": "01/01/2023",
  "lastOrderDate": "01/02/2023"
}


ProductDetailsCustomer cart dataProduct Details JSON Object


Code Block
languagejson
{
    "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


Code Block
languagejson
{
    "categorie1": "AIRLINE TICKET"
}


TravelDetails

Travel parameter: airline tickets, passport information, etc.

Travel Details JSON Object


Code Block
languagejson
{
  "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

Hotelservicesparameter

Stay Details JSON Object


Code Block
languagejson
{
    "company": "Ibis",
    "destination": "Dublin",
    "roomRange": 2
}





Country

Dependingoncontractedcountries, additional parametersaremandatory.

You will find belowasummarytablelistingthespecificparametersforeachcountry.


Paramètres API AXEPTABelgiumSpainItalyPortugal
Language

nl-BE

en-BE

es-ESit-ITpt-PT
AddrCountryCodeBEESITPT
PersonIDNAMandatoryMandatoryMandatory




Tip

You will find test PersonIDs in the section: Test FLOA



Recipe

FLOAtest recommendation andprerequisites

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 



Production environnement

the implémentation of production environnement takes placeaccordingtothefollowingsteps below.

  1.  FLOA Functional validation
    1. FLOA's 'Professional Services' team, which supports the merchant FLOA implementation, carries out testing until payment for each solution integrated on the merchant site. All products will be tested.
    2. Ex: if the merchant has requested 3XG and 4XG, FLOA will do 1 test on the 3XG solution and 1 test on the 4XG solution.
  2. FLOA Marketing validation
    1. The FLOA Marketing team verifies:
      1. All the highlights of FLOA or payment solutions along the way
      2. The display of legal notices in the merchant's general sales conditions
    2. Production by the merchant
      1. The merchant opens FLOA on his website.