Summary
This documentation describes how Payment Method records are transferred from Shopware to iPaaS.com. The collection creates and updates iPaaS.com Payment Method records when triggered by Shopware webhook events or by Manual Sync, carrying the payment method Name and Description from Shopware and setting a payment type value on the iPaaS.com record. Payment methods flow from Shopware to iPaaS.com only; there is no collection that creates or updates Shopware payment methods from iPaaS.com data.
ID Format
Manual Sync ID Format
Payment methods can be transferred from the iPaaS.com Manual Sync page by entering the Shopware payment method ID. The ID is the Shopware payment method identifier, for example 01915630e5db7214ab1ab2dc71608955. This collection also supports bulk Initialization, so existing Shopware payment methods can be loaded in a single operation rather than entered one at a time.
External ID Format
After a transfer, the resulting iPaaS.com Payment Method record is linked back to its Shopware source using the Shopware payment method ID (for example 01915630e5db7214ab1ab2dc71608955) as the external identifier.
Deleted Record Support
Payment method deletions are not propagated by this integration. The family includes only an Add/Update collection for this record type, with no Delete collection, so removing a payment method in Shopware does not remove the corresponding record in iPaaS.com by default. Subscribers or their MiSP should remove obsolete payment methods in iPaaS.com manually if required.
Mapping Collection Status
Status: Enabled
Trigger Events
paymentmethod/created: a payment method is created in Shopware, triggering an Add transfer.
paymentmethod/updated: a payment method is updated in Shopware, triggering an Update transfer.
Manual Sync / bulk Initialization: payment methods can be transferred on demand by entering the Shopware payment method ID, or loaded together through bulk Initialization.
Duplicate or Conflicting Mappings
This mapping transfers Payment Methods from Shopware to iPaaS.com. There is no opposite-direction collection in this integration that creates or updates Shopware payment methods from iPaaS.com data, so no conflicting "From iPaaS.com" collection exists for this record type and no circular-update risk applies.
Unmapped Field Overwrite Risk
Because this collection handles both Add and Update, and the iPaaS.com API replaces the full record on every Update transfer, subscribers should keep all standard Payment Method fields mapped. The default template already maps all of them (Name, Description, and PaymentType). If a subscriber introduces a new standard Payment Method field, they should add a Dynamic Formula mapping that uses the DestinationValue function to carry the existing iPaaS.com value forward, so the new field is not blanked out on each Update transfer.
Shopware Caveats
Webhook workflow actions require Enterprise Shopware: The automatic-transfer workflows described under Setup Requirements can only be created on Enterprise editions of Shopware. Subscribers on other editions should rely on Manual Sync or bulk Initialization instead.
If the Shopware API is temporarily unavailable when a transfer is triggered, the transfer fails and an error appears in Dashboard / Integration Monitoring / Error Logs. The record can be retried by triggering a new webhook event or by using Manual Sync.
iPaaS.com Caveats
This collection does not perform record matching to link Shopware payment methods to existing iPaaS.com payment methods, and it does not provide collision handling. Subscribers should validate payment method transfers in a staging environment before relying on them in production to confirm the records appear as expected.
Subscribers should stagger large manual jobs and rely on the configured API throttle limits when loading many payment methods through bulk Initialization.
Setup Requirements
Automatic transfers require subscribers or their MiSP to subscribe to the Shopware payment method events on the Inbound Data Flows (External Webhooks) page of the Shopware subscription in iPaaS.com. Webhooks do not activate automatically — the relevant events must be subscribed before automatic transfers occur. Subscribing creates a workflow in Shopware that sends a webhook to iPaaS.com after the corresponding event; clearing the Inbound Data Flow toggle removes that workflow. On non-Enterprise editions of Shopware, webhook workflow actions are unavailable, so use Manual Sync or bulk Initialization instead.
Integration Flow
A paymentmethod/created or paymentmethod/updated event occurs in Shopware (or a subscriber initiates a Manual Sync or bulk Initialization).
Shopware sends the corresponding webhook to iPaaS.com, or the Manual Sync request supplies the Shopware payment method ID.
The integration retrieves the full payment method record from Shopware, so the transferred record reflects the current state in Shopware rather than only the changed values.
The record is transformed using the field mappings below.
The Payment Method record is written to iPaaS.com — created on a paymentmethod/created event and updated on a paymentmethod/updated event.
The resulting iPaaS.com Payment Method record is linked back to its Shopware source using the Shopware payment method ID (for example
01915630e5db7214ab1ab2dc71608955) as the external identifier.
Mappings
Add/Update Shopware Payment Method TO iPaaS.com
Description: Transfers a Shopware payment method's name and description to iPaaS.com and sets a payment type value on the iPaaS.com record.
Mapping Type | Source Field (Shopware) | Destination Field (iPaaS.com) | Description |
Field | Name | Name | recommended: maps the Shopware payment method name to the iPaaS.com Payment Method name; the primary human-readable identifier, so subscribers should ensure each Shopware payment method has a name before transfer. |
Field | Description | Description | recommended: maps the Shopware payment method description; transferred empty when the Shopware payment method has no description. |
Static |
| PaymentType | optional: sets the iPaaS.com Payment Method type. Placeholder value — replace during implementation: |
Error Handling
Errors surface in Dashboard / Integration Monitoring / Error Logs.
"Shopware API unavailable": the Shopware API was temporarily unreachable when a transfer was triggered, so the full payment method record could not be retrieved. Resolution: retry the record by triggering a new webhook event or by using Manual Sync once Shopware is reachable.
Testing & Validation
Test Scenarios
Create a payment method in Shopware (or trigger a paymentmethod/created event) and confirm a new iPaaS.com Payment Method record is created with the expected Name and Description.
Update a payment method's name or description in Shopware (or trigger a paymentmethod/updated event) and confirm the existing iPaaS.com Payment Method record is updated.
Create a payment method in Shopware with no description and confirm the iPaaS.com Description field is transferred empty.
Transfer a specific payment method from the iPaaS.com Manual Sync page using the Shopware payment method ID and confirm the record appears in iPaaS.com.
Run bulk Initialization and confirm existing Shopware payment methods are loaded into iPaaS.com.
After replacing the default PaymentType Static value, transfer payment methods of different types and confirm each receives the intended type.
Validation Checklist
The iPaaS.com Payment Method Name matches the Shopware payment method name.
The iPaaS.com Payment Method Description matches the Shopware payment method description, and is empty when Shopware has none.
The PaymentType value reflects the configured Static value rather than being left as the default example for all payment methods.
The iPaaS.com Payment Method record is linked back to its Shopware source by the Shopware payment method ID.
An Update transfer does not blank out any fields that are not part of the changed values, confirming all standard fields remain mapped.
Errors, if any, appear in Dashboard / Integration Monitoring / Error Logs and clear on retry.
Additional Notes
The following limitations are inherent to the current design of the integration and the capabilities of the Shopware API, and they apply to all subscribers at the time this documentation was written.
The default PaymentType mapping is a Static example value applied to every payment method. Until it is replaced with values appropriate to each payment method, all transferred payment methods share the same type in iPaaS.com.
Webhook workflow actions are only available in Enterprise editions of Shopware. On non-Enterprise editions, use Manual Sync or bulk Initialization instead.