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
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
Sicurezza e privacy
Sicurezza
Privacy
Estendi Stripe
Build Stripe apps
Use apps from Stripe
    Panoramica
    Stripe-built apps
    Adobe Commerce
    Cegid
    Commercetools
    Mirakl
      Configurazione
      Installazione
      Attivare i venditori
      Pagamenti
      Bonifici
      Riferimento
    NetSuite
    Oracle Opera
    PrestaShop
    Salesforce
    SAP
    Shopware 6
    Stripe Tax for BigCommerce
    Stripe Tax for WooCommerce
    Partner apps
    Build your own 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.

Mirakl reference

Default settings for Miraki plugin events.

Scheduled jobs

Onboarding

Command Line
php bin/console connector:sync:onboarding -q 2>&1
  • Default setting: every minute.
  • Recommended setting: as often as possible.
  • Description: fetch newly created Mirakl shops and add the onboarding link to their Mirakl back office.
  • Documentation: Onboarding workflow.

Payment validation

Command Line
php bin/console connector:validate:pending-debit -q 2>&1
  • Default setting: every 5 minutes.
  • Recommended setting: < 1 hour.
  • Description: fetch newly accepted Mirakl orders, validate the payment on Mirakl, and capture it on Stripe.
  • Documentation: Payment validation workflow.

Payment split

Command Line
php bin/console connector:dispatch:process-transfer -q 2>&1
  • Default setting: every 5 minutes.
  • Recommended setting: < 1 hour.
  • Description: fetch newly debited Mirakl orders and create Stripe Transfers from the operator to the seller.
  • Documentation: Payment split workflow.

Payment refund

Command Line
php bin/console connector:dispatch:process-refund -q 2>&1
  • Default setting: every 5 minutes.
  • Recommended setting: < 1 hour.
  • Description: fetch pending Mirakl refunds, create the refund on Stripe, validate it on Mirakl, and reverse the initial transfer.
  • Documentation: Payment refund workflow.

Payout

Command Line
php bin/console connector:dispatch:process-payout -q 2>&1
  • Default setting: every day at 1am.
  • Recommended setting: synchronized with your Mirakl billing cycles.
  • Description: fetch newly created Mirakl invoices and create Stripe Transfers and Payouts.
  • Documentation: Payouts workflow.

Alerting

Command Line
php bin/console connector:notify:failed-operation -q 2>&1
  • Default setting: every day at 8am.
  • Recommended setting: according to your preference.
  • Description: if enabled, send an email with all the failed transfers, refunds, and payouts.

Notification

If enabled, the connector sends server to server notifications in the following events.

Nota

If your endpoint is unreachable or returns an error, an email is sent to your TECHNICAL_ALERT_EMAIL.

Account updated

A Stripe connected account was updated by the seller or Stripe.

{ "type": "account.updated", "payload": { "miraklShopId": 2000, "stripeUserId": "acct_1032D82eZvKYlo2C" } }

Transfer failed

A transfer failed during the payment split job or the payout job.

{ "type": "transfer.failed", "payload": { "internalId": 5, "miraklId": 123, "type": "TRANSFER_ORDER", "stripeAccountId": "acct_1032D82eZvKYlo2C", "miraklShopId": 2003, "transferId": null, "transactionId": null, "amount": 3400, "status": "TRANSFER_FAILED", "failedReason": "Reason message", "currency": "EUR" } }

Refund failed

A refund failed during the payment refund job job.

{ "type": "refund.failed", "payload": { "internalId": 5, "miraklOrderId": "order_refunded_5", "miraklRefundId": "1100", "stripeRefundId": null, "stripeReversalId": "trr_10", "amount": 3400, "status": "REFUND_FAILED", "failedReason": "Reason message", "currency": "EUR" } }

Payout failed

A payout failed during the payout job.

{ "type": "payout.failed", "payload": { "internalId": 12, "amount": 2300, "currency": "EUR", "miraklInvoiceId": 2000, "stripePayoutId": null, "status": "PAYOUT_FAILED", "failedReason": "Reason message", } }
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