Weiter zum Inhalt
Konto erstellen
oder
anmelden
Das Logo der Stripe-Dokumentation
/
KI fragen
Konto erstellen
Anmelden
Jetzt starten
Zahlungen
Umsatz
Plattformen und Marktplätze
Geldmanagement
Entwicklerressourcen
Übersicht
Versionierung
Änderungsprotokoll
Aktualisieren Sie Ihre API-Version
Ihre SDK-Version aktualisieren
Essentials
SDKs
API
Tests
Stripe-CLI
Tools
Workbench
Entwickler-Dashboard
Stripe Shell
Stripe für Visual Studio Code
Funktionen
Arbeitsabläufe
Ereignisziele
Stripe-StatuswarnungenHochgeladene Dateien
KI-Lösungen
Agent-Toolkit
Sicherheit und Datenschutz
Sicherheit
Datenschutz
Extend Stripe
Build Stripe apps
Use apps from Stripe
    Übersicht
    Stripe-built apps
    Adobe Commerce
    Cegid
    Commercetools
    Mirakl
      Konfiguration
      Installation
      Onboarding von Verkäufer/innen
      Zahlungen
      Auszahlungen
      Verwendungszweck
    NetSuite
    Oracle Opera
    PrestaShop
    Salesforce
    SAP
    Shopware 6
    Stripe Tax for BigCommerce
    Stripe Tax für WooCommerce
    Partner apps
    Build your own app
Partner
Partner-Ecosystem
Partner-Zertifizierung
StartseiteEntwicklerressourcenUse apps from StripeMirakl

Notiz

Bis jetzt ist diese Seite noch nicht in dieser Sprache verfügbar. Wir arbeiten aber verstärkt daran, unsere Dokumentation in weiteren Sprachen bereitzustellen, und werden die Übersetzung sofort anzeigen, sobald diese verfügbar ist.

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.

Notiz

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", } }
War diese Seite hilfreich?
JaNein
Benötigen Sie Hilfe? Kontaktieren Sie den Kundensupport.
Nehmen Sie an unserem Programm für frühzeitigen Zugriff teil.
Schauen Sie sich unser Änderungsprotokoll an.
Fragen? Sales-Team kontaktieren.
LLM? Lesen Sie llms.txt.
Unterstützt von Markdoc