Passa al contenuto
Crea account
o
Accedi
Il logo della documentazione Stripe
/
Chiedi all'IA
Crea un account
Accedi
Inizia
Pagamenti
Ricavi
Per piattaforme e marketplace
Gestione del denaro
Risorse per sviluppatori
Panoramica
Controllo delle versioni
Log modifiche
Aggiorna la tua versione API
Aggiornare la versione dell'SDK
Essentials
SDK
API
Test
CLI di Stripe
Progetti di esempio
Strumenti
Workbench
Dashboard per sviluppatori
Shell di Stripe
Stripe per Visual Studio Code
Funzionalità
Flussi di lavoro
Destinazioni degli eventi
Avvisi sullo stato di StripeCaricamenti file
Soluzioni di IA
Toolkit agente
Protocollo del contesto del modello
Sicurezza e privacy
Sicurezza
Stripebot web crawler
Privacy
Estendi Stripe
Crea Stripe Apps
Usa le app di Stripe
    Panoramica
    App integrate in Stripe
    Adobe Commerce
    Cegid
    Commercetools
    Mirakl
      Installa
      Configura
      Onboard sellers
      pagamenti e bonifici
      Riferimento
    NetSuite
    Oracle Opera
    Oracle Simphony
    Oracle Xstore
    PrestaShop
    Salesforce
    SAP
    Shopware 6
    Stripe Tax for BigCommerce
    Stripe Tax for WooCommerce
    App partner
    Crea la tua app
Partner
Partner Ecosystem
Certificazione di partner
Pagina inizialeRisorse per sviluppatoriUse apps from StripeMirakl

Nota

Questa pagina non è ancora disponibile in questa lingua. Stiamo lavorando alla preparazione della nostra documentazione in più lingue e ne forniremo una traduzione non appena disponibile.

Install the Mirakl app

Set up the Miraki app for Stripe.

To install and run the Mirakl app, you must meet the following requirements:

  • PHP 7.3+
  • PostgreSQL
  • A web server (Nginx recommended)
  • A valid SSL or TLS certificate
  • Supervisord or an equivalent process manager
  • Crontab or an equivalent task scheduler

Use Docker

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

Use Composer

  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
  5. Properly configure the .env file.

  6. Run the migrations to set up the database. If you encounter any errors at this stage, check the DATABASE_URL variable in your .env file.

    Command Line
    bin/console doctrine:migration:migrate --no-interaction
  7. 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
  8. 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
  9. Make sure that your web server is configured to use the public directory as document root.

Test 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.

Restrict inbound traffic

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, because they each have an internal protection mechanism. Other endpoints aren’t safe to expose unless protected by a strong OPERATOR_PASSWORD.

Questa pagina è stata utile?
SìNo
  • Hai bisogno di aiuto? Contatta l'assistenza clienti.
  • Partecipa al nostro programma di accesso anticipato.
  • Dai un'occhiata al nostro registro delle modifiche.
  • Domande? Contattaci.
  • LLM? Leggi llms.txt.
  • Realizzato da Markdoc