> ## Documentation Index
> Fetch the complete documentation index at: https://primer.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# FLOA via 1Point6

> Let customers pay in 3 or 4 instalments using FLOA BNPL via 1Point6.

FLOA via 1Point6 is a French BNPL product that splits the total into 3 or 4 monthly instalments. It is a redirect flow — the customer is sent to a 1Point6-hosted page to complete the payment. EUR only, targeted at the French market.

<Note>
  `sub_category_1` and `sub_category_2` are **mandatory** for FLOA — omitting them will cause FLOA to reject the payment.
</Note>

| One-Off Payment | Refund | Recurring | Cancel |
| - | - | - | - |
| ✓ | TBC | x | TBC |

## Get started with FLOA via 1Point6

### Before you begin

If this is your first payment method, make sure to follow the [Get started guide](/docs/get-started/overview) to begin processing payments with Primer.

### Configure in the Dashboard

1. **Add 1Point6 to your Dashboard**\
   Go to the [Connections](/docs/connections/payment-methods) section of the Dashboard and look for `1Point6`. Follow the instructions to connect your 1Point6 account to your Primer Dashboard.

2. **Activate FLOA via 1Point6 on the Checkout**\
   Go to the [Checkout](/docs/checkout) section of the Dashboard and activate the FLOA payment method.

3. **Configure a Workflow to process payments made with FLOA**\
   Go to [Workflows](/docs/workflows), set up the **Authorization** step to process APMs. No need to add **Capture**. Finish the workflow with a **Continue payment flow** action.

### Prepare the client session

FLOA via 1Point6 leverages the following parameters to process a payment. Pass them when creating the client session.

| Parameter Name | Required | Description |
| - | - | - |
| `customer.mobileNumber` | ✓ | Required by FLOA for eligibility. |
| `metadata.bnplPlan` | ✓ | `"floa_3x"` or `"floa_4x"` depending on the instalment plan. Required for sandbox testing. |
| `metadata.birth_date` | ✓ | Payer date of birth (`YYYY-MM-DD`). Required for FLOA eligibility. |
| `metadata.payin_items[].sub_category_1` | ✓ | Item category, e.g. `"TRAVEL"`. Mandatory for FLOA. |
| `metadata.payin_items[].sub_category_2` | ✓ | Item sub-category, e.g. `"Train Ticket"`. Mandatory for FLOA. |
| `metadata.payin_items[].metadata` | ✓ | Travel-specific metadata object (see below). Required for travel merchants. |
| `metadata.payin_items` | ✓ | Pre-assembled array — Primer's Metadata Mapper cannot produce arrays. |

#### FLOA travel metadata

For travel merchants, pass travel-specific data inside each payin item's `metadata` field:

```json theme={"dark"}
{
  "metadata": {
    "payin_items": [{
      "amount": 50000,
      "sub_category_1": "TRAVEL",
      "sub_category_2": "Train Ticket",
      "metadata": {
        "insurrance": "Sans assurance",
        "type": "OneWay",
        "departure_date": "2026-10-25",
        "return_date": "1970-01-01",
        "destination_country_code": "PT",
        "travelers_count": 1,
        "own_ticket": true,
        "main_departure_company": "TAP Air Portugal",
        "departure_airport": "ORY",
        "destination_airport": "LIS",
        "luggage_supplement": "0",
        "modification_cancellation": false,
        "class": "Economy",
        "website": "https://www.flytap.com"
      }
    }]
  }
}
```

<Note>
  The exact subset of travel metadata fields forwarded by ORX is being confirmed with FLOA. The API will not crash on missing fields, but FLOA may reject for eligibility reasons.
</Note>

## Go live

Use production credentials. Confirm the mandatory travel metadata field subset with FLOA before going live.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.