Accéder directement au contenu
Créez un compte
ou
connecter-vous
Logo de la documentation Stripe
/
Demander à l'assistant IA
Créez un compte
Connectez-vous
Démarrer
Paiements
Revenus
Plateformes et places de marché
Gestion de fonds
Ressources pour les développeurs
Aperçu
Gestion des versions
Journal des modifications
Mettre à niveau votre version de l'API
Actualiser votre version du SDK
Essentials
SDK
API
Tests
CLI Stripe
Outils
Workbench
Dashboard des développeurs
Shell Stripe
Stripe pour Visual Studio Code
Fonctionnalités
Workflows
Destinations d'événements
Alertes d'intégrité de StripeChargements de fichiers
Solutions d'IA
Boîte à outils des agents
Sécurité et confidentialité
Sécurité
Confidentialité
Extensions Stripe
Build Stripe apps
Use apps from Stripe
    Présentation
    Stripe-built apps
    Adobe Commerce
    Cegid
    Commercetools
    Mirakl
      Configuration
      Installation
      Inscription des marchands
      Paiements
      Virements
      Référence
    NetSuite
    Oracle Opera
    PrestaShop
    Salesforce
    SAP
    Shopware 6
    Stripe Tax pour BigCommerce
    Stripe Tax for WooCommerce
    Partner apps
    Build your own app
Partenaires
Partner ecosystem
Certification des partenaires
AccueilRessources pour les développeursUse apps from StripeMirakl

Remarque

Cette page n'est pas encore disponible dans cette langue. Nous faisons tout notre possible pour proposer notre documentation dans davantage de langues et nous vous fournirons la version traduite dès qu'elle sera disponible.

Mirakl Plugin installation

Install and validate the Miraki plugin for Stripe.

Requirements

Installing and running the application requires the following:

  • PHP 7.3+
  • PostgreSQL
  • A web server, Nginx recommended
  • A valid SSL/TLS certificate
  • Supervisord or equivalent
  • Crontab or equivalent

Install using Docker

You can build and start the application by embedding it in a container. See our Docker sample for more information.

Install manually

  1. Install Composer.
  2. Clone or download the Mirakl App from GitHub.
  3. Move the content to your web server directory, for example, /var/www.
  4. Download dependencies:
Command Line
composer install --prefer-dist --no-dev
  1. Make sure you properly configured the .env file.
  2. Run the migrations to set up the database:
Command Line
bin/console doctrine:migration:migrate --no-interaction

If you encounter any errors at this stage, check the DATABASE_URL variable in your .env file.

  1. Update your supervisor to automatically start and restart the workers.

A configuration example is available in our Docker sample. You can skip this step in a development environment and start the workers manually when needed, for example:

Command Line
php bin/console messenger:consume process_transfers --time-limit=3600 --env=prod
  1. Update your job scheduler to run the commands periodically.

A configuration example is available in our Docker sample. You can skip this step in a development environment and start the jobs manually when needed, for example:

Command Line
php bin/console connector:dispatch:process-transfer -q 2>&1
  1. Make sure that your web server is configured to use the public directory as document root.

Check your installation

Open your terminal and run the following command to confirm that your application is up and running correctly:

Command Line
curl -X GET "https://app-url/api/mappings" \ -H "accept: application/json" \ -H "X-AUTH-TOKEN:
$OPERATOR_PASSWORD
"

You should get a 200 response code along with an empty payload.

Security

On your server, restrict all inbound traffic to the plugin except for the following endpoints:

  • /api/public/onboarding/refresh

    Stripe redirects the seller to this URL to get a new onboarding link if it expires.

  • /api/public/webhook/operator

    Stripe notifies this endpoint when a payment is updated to map it with a Mirakl order within the app.

  • /api/public/webhook/sellers

    Stripe notifies this endpoint when a Stripe account is updated to synchronize the seller’s status within the app.

These endpoints are safe to expose, they each have an internal protection mechanism. Other endpoints are not safe to expose unless protected by a strong OPERATOR_PASSWORD.

Voir aussi

  • Integration steps.
Cette page vous a-t-elle été utile ?
OuiNon
Besoin d'aide ? Contactez le service Support.
Rejoignez notre programme d'accès anticipé.
Consultez notre log des modifications.
Des questions ? Contactez l'équipe commerciale.
LLM ? Lire llms.txt.
Propulsé par Markdoc