---
title: "Rakuten Pay Flutter Component"
description: "Add Rakuten Pay to your Components integration."
url: "https://docs.adyen.com/payment-methods/rakutenpay/flutter-component"
source_url: "https://docs.adyen.com/payment-methods/rakutenpay/flutter-component.md"
canonical: "https://docs.adyen.com/payment-methods/rakutenpay/flutter-component"
last_modified: "2026-06-01T15:33:15+02:00"
language: "en"
---

# Rakuten Pay Flutter Component

Add Rakuten Pay to your Components integration.

[View source](/payment-methods/rakutenpay/flutter-component.md)

You can add Rakuten Pay to your existing integration. The following instructions show only what you must add to your integration specifically for Rakuten Pay.

If an instruction on this page corresponds with a step in the main integration guide, it includes a link to corresponding step of the main integration guide.

The additions you must make depends on the [server-side flow](/online-payments/build-your-integration) that your integration uses:

## Sessions flow Component

## Requirements

| Requirement           | Description                                                                                                                                                                                                                  |   |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - |
| **Integration type**  | Make sure that you have an existing Sessions flow [Flutter Components integration](/online-payments/build-your-integration/advanced-flow?platform=Flutter\&integration=Drop-in).                                             |   |
| **Checkout API**      | Make sure that you use Checkout API v68 or later.                                                                                                                                                                            |   |
| **Redirect handling** | Make sure that your existing integration is set up to [handle the redirect](/online-payments/build-your-integration/sessions-flow?platform=Flutter\&integration=Components#handle-the-redirect). `action.type`: **redirect** |   |
| **Setup steps**       | Before you begin, [add Rakuten Pay in your Customer Area](/payment-methods/add-payment-methods).                                                                                                                             |   |

### Additional Parameters Sessions Request

## Add additional parameters to your /sessions request

You do not need to add any parameters when you [create a payment session](/online-payments/build-your-integration/sessions-flow?platform=Flutter\&integration=Components#create-a-payment-session).

### Additional Configuration

## Add additional configuration for Rakuten Pay

You do not need to add any configuration parameters for Rakuten Pay.

## Recurring

If you have a business model based on [subscription](/get-started-with-adyen/adyen-glossary#subscriptions) and [unscheduled card-on-file](/get-started-with-adyen/adyen-glossary#unscheduled-card-on-file-ucof) payments, Rakuten Pay permits one-off [card-on-file](/get-started-with-adyen/adyen-glossary#card-on-file-cof) transactions after a review process. If you do not have a periodic charging cadence, Rakuten Pay prohibits you from initiating the Recurring Processing Model for card-on-file, which is primarily allowed for the Food & Beverage business category. You must apply for every Recurring Processing Model when you request Rakuten Pay.

Refer to [Create tokens](/online-payments/tokenization/create-tokens/) to integrate with our tokenization feature.

We strongly recommend that you ask explicit permission from the shopper if you intend to make future recurring payments. Being transparent about the payment schedule and the charged amount reduces the risk of chargebacks.

## Test and go live

To test Rakuten Pay payments, use the acquirer account `DGFT_AcquirerAccount_RakutenPay_closedLoop` in the TEST environment.

You will be redirected you to a DGFT simulator tool to complete the transaction. You do not need the Rakuten Pay app.

You can check the status of Rakuten Pay test account transactions in your Customer Area at **Transactions** > **Payments**.

## Advanced flow Component

### Before-You-Begin

## Requirements

| Requirement           | Description                                                                                                                                                                                                                   |   |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - |
| **Integration type**  | Make sure that you have an existing Advanced flow [Flutter Components integration](/online-payments/build-your-integration/advanced-flow?platform=Flutter\&integration=Drop-in).                                              |   |
| **Redirect handling** | Make sure that your existing integration is set up to [handle the redirect](/online-payments/build-your-integration/advanced-flow/?platform=Flutter\&integration=Components#handle-the-redirect). `action.type`: **redirect** |   |
| **Setup steps**       | Before you begin, [add Rakuten Pay in your Customer Area](/payment-methods/add-payment-methods).                                                                                                                              |   |

### Add-Configuration

## Add additional configuration for Rakuten Pay

You do not need to add any configuration parameters for Rakuten Pay.

### Add-Parameters-Payments-Request

## Add additional parameters to your /payments request

You do not need to add any parameters to the [/payments](https://docs.adyen.com/api-explorer/Checkout/latest/post/payments) request when you [make a payment](/online-payments/build-your-integration/advanced-flow/?platform=Flutter\&integration=Components#make-a-payment).

## Recurring

If you have a business model based on [subscription](/get-started-with-adyen/adyen-glossary#subscriptions) and [unscheduled card-on-file](/get-started-with-adyen/adyen-glossary#unscheduled-card-on-file-ucof) payments, Rakuten Pay permits one-off [card-on-file](/get-started-with-adyen/adyen-glossary#card-on-file-cof) transactions after a review process. If you do not have a periodic charging cadence, Rakuten Pay prohibits you from initiating the Recurring Processing Model for card-on-file, which is primarily allowed for the Food & Beverage business category. You must apply for every Recurring Processing Model when you request Rakuten Pay.

Refer to [Create tokens](/online-payments/tokenization/create-tokens/) to integrate with our tokenization feature.

We strongly recommend that you ask explicit permission from the shopper if you intend to make future recurring payments. Being transparent about the payment schedule and the charged amount reduces the risk of chargebacks.

## Test and go live

To test Rakuten Pay payments, use the acquirer account `DGFT_AcquirerAccount_RakutenPay_closedLoop` in the TEST environment.

You will be redirected you to a DGFT simulator tool to complete the transaction. You do not need the Rakuten Pay app.

You can check the status of Rakuten Pay test account transactions in your Customer Area at **Transactions** > **Payments**.
