-
Notifications
You must be signed in to change notification settings - Fork 4
/
documentation.html
704 lines (703 loc) · 30 KB
/
documentation.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
<meta name="keywords" value="wallee, Shopware, Shopware Plugin, Payment, Payment Integration, Documentation"><meta name="description" value="The documentation for the Shopware 6 plugin that enables processing payments with wallee.">
<link rel="canonical" href="https://plugin-documentation.wallee.com/wallee-payment/shopware-6/master/WalleePayment/docs/en/documentation.html" />
<title>wallee Shopware 6 Documentation</title>
<link href="assets/monokai-sublime.css" rel="stylesheet" />
<link href="assets/base.css" rel="stylesheet" />
</head>
<body class="documentation">
<div class="layout-wrapper">
<div class="layout-title">
<h1>wallee Shopware 6 Documentation</h1>
<h2>Documentation</h2> </div>
<div class="layout-navigation">
<ul class="nav">
<li>
<a href="https://app-wallee.com/user/signup">
Sign Up
</a>
</li>
<li>
<a href="https://github.com/wallee-payment/shopware-6/releases/tag/5.0.9/">
Source
</a>
</li>
</ul> </div>
<div class="layout-content">
<div class="col-body">
<div class="col-body-wrapper">
<div class="body-container">
<div class="chapter" id="_prerequisites">
<div class="chapter-title">
<h1>
<span class="title-number">1</span>Prerequisites </h1>
</div>
<div class="chapter-body">
<div class="paragraph">
<p>If you don’t already have one, create a <a href="https://app-wallee.com/user/signup/">wallee</a> account.</p>
</div> </div>
</div> <div class="chapter" id="_installation">
<div class="chapter-title">
<h1>
<span class="title-number">2</span>Installation </h1>
</div>
<div class="chapter-body">
<div class="olist arabic">
<ol class="arabic">
<li>
<p>Install the plugin directly from the Shopware plugin store.</p>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
You also have the possibility to install the plugin using composer. See <a href="#_faq">FAQ</a>.
</td>
</tr>
</table>
</div>
</li>
<li>
<p>Log in to the backend of your Shopware store.</p>
</li>
<li>
<p>Navigate to Settings → System → Plugins. Click on the menu caret and select the <code>Install</code> link of the plugin to install it.</p>
<div class="imageblock">
<div class="content">
<img src="resource/plugin-installation.png" alt="plugin installation"/>
</div>
</div>
</li>
<li>
<p>Activate the wallee Payment plugin from the Plugin Manager.</p>
</li>
</ol>
</div> </div>
</div> <div class="chapter" id="_configuration">
<div class="chapter-title">
<h1>
<span class="title-number">3</span>Configuration </h1>
</div>
<div class="chapter-body">
<div class="olist arabic">
<ol class="arabic">
<li>
<p>Navigate to Settings → Plugins → Wallee in your Shopware backend. Enter the wallee Space ID, User ID and Authentication Key that you can create an <a href="https://app-wallee.com/en-us/doc/permission-concept#_create_application_users" target="_blank">application user</a>.</p>
<div class="imageblock">
<div class="content">
<img src="resource/plugin-configuration.png" alt="plugin configuration"/>
</div>
</div>
<div class="paragraph">
<p>If your store is configured for multiple sales channels, you may use different spaces for each store to configure different behaviours.</p>
</div>
</li>
<li>
<p>Optionally after saving your configuration you can click on <code>Set Wallee as default payment handler</code>. This will set WalleePayment as the default payment handler for the selected sales channel.</p>
</li>
</ol>
</div><div class="paragraph">
<p>The main configuration is finished now. You should see the payment methods in your checkout. To view the payment method configuration in the backend of Shopware go to Settings → Store → Payment.</p>
</div> </div>
</div> <div class="chapter" id="_payment_method_configuration">
<div class="chapter-title">
<h1>
<span class="title-number">4</span>Payment method configuration </h1>
</div>
<div class="chapter-body">
<div class="section" id="_setup">
<div class="section-title">
<h2>
<span class="title-number">4.1</span>Setup </h2>
</div>
<div class="section-body">
<div class="paragraph">
<p>The wallee payment method configurations are synchronized automatically into the Shopware store. There are just a few payment method settings in the Shopware store in Settings → Store → Payment.</p>
</div><div class="imageblock">
<div class="content">
<img src="resource/payment-method-configuration.png" alt="payment method configuration"/>
</div>
</div> </div>
</div> <div class="section" id="_payment_method_rules">
<div class="section-title">
<h2>
<span class="title-number">4.2</span>Payment method rules </h2>
</div>
<div class="section-body">
<div class="paragraph">
<p>If you would like to restrict a payment method to certain conditions (B2B, cart amount, etc), you can create or choose a rule with the Availability Rule option in the shop backend.</p>
</div><div class="imageblock">
<div class="content">
<img src="resource/payment-method-configuration-availability-rule.png" alt="payment method configuration availability rule"/>
</div>
</div><div class="paragraph">
<p><strong>How to create a new Rule?</strong></p>
</div><div class="olist arabic">
<ol class="arabic">
<li>
<p>Click on “Create new rule…” in the Availability rule option and fill out the modal form with conditions, as shown below.</p>
</li>
</ol>
</div><div class="imageblock">
<div class="content">
<img src="resource/payment-method-configuration-create-availability-rule.png" alt="payment method configuration create availability rule"/>
</div>
</div><div class="olist arabic">
<ol class="arabic">
<li>
<p>In this example the rule is as shown below:</p>
<div class="ulist">
<ul>
<li>
<p>Name: Payment method for B2B.</p>
</li>
<li>
<p>Priority: 1 (if you wish to prioritise when using several shipping methods, please adjust the value accordingly).</p>
</li>
<li>
<p>Conditions: Commercial customer | Yes
Billing address: Country | Is one of | Switzerland</p>
</li>
</ul>
</div>
</li>
</ol>
</div><div class="paragraph">
<p>You can now select the rule in the desired payment method in the item availability rule.</p>
</div><div class="paragraph">
<p>It is also conceivable to add a further condition to the rule above, e.g. to make the payment method additionally possible only from a certain purchase value (e.g. 250.00).</p>
</div><div class="paragraph">
<p>In this case, add another condition using the AND link and insert the following in the second condition.</p>
</div><div class="olist arabic">
<ol class="arabic">
<li>
<p>Select the newly created rule and save the changes to the chosen payment method.</p>
</li>
</ol>
</div><div class="paragraph">
<p>Applying this rule to a payment method will result in only those customers who meet the configured conditions.</p>
</div> </div>
</div> <div class="section" id="_customization">
<div class="section-title">
<h2>
<span class="title-number">4.3</span>Customization </h2>
</div>
<div class="section-body">
<div class="paragraph">
<p>If you want to change the payment method description, title, logo, etc you need to do this in the <a href="https://app-wallee.com/space/select?target=/payment/method-configuration/list" target="_blank">payment method configuration</a>. Changes will be synchronized automatically.</p>
</div> </div>
</div> </div>
</div> <div class="chapter" id="_state_graph">
<div class="chapter-title">
<h1>
<span class="title-number">5</span>State graph </h1>
</div>
<div class="chapter-body">
<div class="paragraph">
<p>The Payment Process of wallee is <strong>completely standardized for every payment method</strong> you can process. This gives you the ability to simply add
a payment method or processor without changes inside of your Shopware configuration. An overview about the states and the payment processes of wallee
can be found in the <a href="https://app-wallee.com/en-us/doc/payment/transaction-process" target="_blank">Payment Documentation</a>.</p>
</div><div class="paragraph">
<p>In the following section we provide you an overview about how the wallee states are mapped into the Shopware State graph for orders and payment states.</p>
</div> <div class="section" id="_state_mapping_of_shopware_orders">
<div class="section-title">
<h2>
<span class="title-number">5.1</span>State mapping of Shopware orders </h2>
</div>
<div class="section-body">
<div class="paragraph">
<p>When the order gets abandoned also Order status goes to "cancel" after approx. 40 minutes. We also change the Payment status, and the Delivery status.</p>
</div> <div class="section" id="_general_remarks_regarding_order_statuses">
<div class="section-title">
<h3>
<span class="title-number">5.1.1</span>General remarks regarding order statuses </h3>
</div>
<div class="section-body">
<div class="paragraph">
<p>We recommend that you only change the Order status once the Payment status has reached a final state.</p>
</div> </div>
</div> </div>
</div> <div class="section" id="_state_mapping_of_shopware_payment_status">
<div class="section-title">
<h2>
<span class="title-number">5.2</span>State mapping of Shopware payment status </h2>
</div>
<div class="section-body">
<div class="paragraph">
<p>Below you find a diagram that shows the state machine of Shopware for payment status including additional information for the state transitions.</p>
</div><div class="imageblock">
<div class="content">
<img src="resource/shopware_6_stage_graph_order.svg" alt="shopware 6 stage graph order"/>
</div>
</div><div class="olist glossary">
<ol class="glossary">
<li>
<p>If the transaction is <code>Authorized</code> in wallee, the Shopware order payment status is marked as <code>In Progress</code>.</p>
</li>
<li>
<p>If the transaction fails before or during the authorization process, the Shopware order payment status is marked as <code>Failed</code>.</p>
</li>
<li>
<p>If the transaction fails after the authorization, the Shopware order payment status is marked as <code>Cancelled</code>.</p>
</li>
<li>
<p>If the transaction invoice in wallee is marked as <code>Paid</code> or <code>Not Applicable</code>, the Shopware order payment status is marked as <code>Paid</code>.</p>
</li>
</ol>
</div> <div class="section" id="_general_remarks_regarding_payment_statuses">
<div class="section-title">
<h3>
<span class="title-number">5.2.1</span>General remarks regarding payment statuses </h3>
</div>
<div class="section-body">
<div class="paragraph">
<p>We recommend that you do not change the payment status manually. If you do so, it may be changed again by the plugin.</p>
</div> </div>
</div> </div>
</div> <div class="section" id="_state_mapping_of_shopware_delivery_status">
<div class="section-title">
<h2>
<span class="title-number">5.3</span>State mapping of Shopware delivery status </h2>
</div>
<div class="section-body">
<div class="paragraph">
<p>Below you find a diagram that shows the state machine of Shopware delivery status including additional information for the state transitions.</p>
</div><div class="imageblock">
<div class="content">
<img src="resource/shopware_6_stage_graph_delivery.svg" alt="shopware 6 stage graph delivery"/>
</div>
</div><div class="olist glossary">
<ol class="glossary">
<li>
<p>If the transaction is <code>Confirmed</code> status in wallee, the Shopware order delivery status is marked as <code>Hold</code>.</p>
</li>
<li>
<p>If the transaction in wallee is marked as <code>Fulfill</code>, the Shopware order delivery status is marked as <code>Open</code>.</p>
</li>
<li>
<p>If the transaction is in <code>Decline</code>, <code>Failed</code> or <code>Voided</code>, the Shopware order delivery status is marked as <code>Cancelled</code>.</p>
</li>
</ol>
</div> </div>
</div> </div>
</div> <div class="chapter" id="_transaction_management">
<div class="chapter-title">
<h1>
<span class="title-number">6</span>Transaction management </h1>
</div>
<div class="chapter-body">
<div class="paragraph">
<p>You can capture, cancel and refund transactions directly from within the Shopware backend. Please note
if you refund, void or capture transactions inside wallee the events will be synchronized into
Shopware. However, there are some limitations (see below).</p>
</div> <div class="section" id="_complete_capture_an_order">
<div class="section-title">
<h2>
<span class="title-number">6.1</span>Complete (capture) an order </h2>
</div>
<div class="section-body">
<div class="paragraph">
<p>You have the possibility for your transactions to have the payment only authorized after the order is placed. Inside the <a href="https://app-wallee.com/space/select?target=/payment/connector-configuration/list" target="_blank">connector configuration</a> you have the option, if the payment method supports it, to define whether the payment should be completed immediately or deferred.</p>
</div><div class="paragraph">
<p>In order to capture a transaction, open the order and click on the <code>Complete</code> button.</p>
</div><div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
When the completion is pending in wallee the order will stay in pending state.
</td>
</tr>
</table>
</div><div class="imageblock">
<div class="content">
<img src="resource/capture-transaction.png" alt="capture transaction"/>
</div>
</div><div class="paragraph">
<p><strong>Deferred payment completion</strong></p>
</div><div class="paragraph">
<p>Retailers often have the case that they want to authorize transactions only and start the fulfillment process once all items are shippable. This is also possible with wallee.</p>
</div><div class="paragraph">
<p>However, certain processes should be followed. If you have configured payment completion to be deferred you should capture the transaction before you initiate the shipment
as it can always happen that a completion fails. If you want to be sure that you do not ship items for which you have not been paid you should postpone the shipment until
the fulfill state is reached. Initially the transaction will be in the <code>Authorized</code> state in wallee and <code>In Progress</code> in Shopware. If you want to start the fulfillment process make sure you initiate the completion process as described above. Once the completion was successful the order will switch into the <code>Fulfill</code> state in wallee and into <code>Paid</code> state in Shopware. You can now start the fulfillment process.</p>
</div> </div>
</div> <div class="section" id="_void_a_transaction">
<div class="section-title">
<h2>
<span class="title-number">6.2</span>Void a transaction </h2>
</div>
<div class="section-body">
<div class="paragraph">
<p>In order to void a transaction, open the order and click on the <code>Cancel authorization</code> button.</p>
</div><div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
You can only void transactions that are not yet completed.
</td>
</tr>
</table>
</div><div class="imageblock">
<div class="content">
<img src="resource/void-transaction.png" alt="void transaction"/>
</div>
</div> </div>
</div> <div class="section" id="_refund_of_a_transaction">
<div class="section-title">
<h2>
<span class="title-number">6.3</span>Refund of a transaction </h2>
</div>
<div class="section-body">
<div class="paragraph">
<p>You have the possibility to refund already completed transactions. In order to do so, open the captured order. By clicking on the 3 dots (…​) on a line-item, you can refund the line-item partially (if it has a higher quantity than 1), or you can refund the whole line-item. In case the payment method does not support refunds, you will not see the possibility to issue online refunds.</p>
</div><div class="imageblock">
<div class="content">
<img src="resource/refund-transaction.png" alt="refund transaction"/>
</div>
</div><div class="paragraph">
<p>You can carry out as many individual refunds as you wish until you have reached the total amount of the original order.
The status of the order then automatically switches to complete.</p>
</div><div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
It can take some time until you see the refund in Shopware. Refunds will only be visible once they have been processed successfully.
</td>
</tr>
</table>
</div> </div>
</div> <div class="section" id="_on_hold_orders">
<div class="section-title">
<h2>
<span class="title-number">6.4</span>On hold orders </h2>
</div>
<div class="section-body">
<div class="paragraph">
<p>The delivery should not be done whilst the delivery state is <code>Hold</code>. This happens when the transaction in wallee
has not reached the fulfill state.</p>
</div><div class="paragraph">
<p>There are essentially two reasons why this can happen:</p>
</div><div class="ulist">
<ul>
<li>
<p>The transaction is not completed. In this case you have to complete the transaction as written above.</p>
</li>
<li>
<p>We are not able to tell if you should fulfill the order. The delivery decision is done automatically. If this does not happen
within the defined time frame, wallee will generate a manual task which you should observe and follow the instructions.</p>
</li>
</ul>
</div><div class="paragraph">
<p>You can find more information about manual tasks in our <a href="https://app-wallee.com/en-us/doc/manual-tasks" target="_blank">Manual Task Documentation</a>.</p>
</div> </div>
</div> <div class="section" id="_limitations_of_the_synchronization_between_whitelabelname_and_shopware">
<div class="section-title">
<h2>
<span class="title-number">6.5</span>Limitations of the synchronization between wallee and Shopware </h2>
</div>
<div class="section-body">
<div class="paragraph">
<p>Please note that captures, voids and refunds done in wallee are synchronized. However, there are some
limitations. Inside wallee you are able to change the <strong>unit price</strong> and the <strong>quantity</strong> at once. This can not
be done in the Shopware backend. We therefore recommend that you
perform the refunds always inside the Shopware backend and not inside wallee. If a refund
cannot be synchronized it will be sent to the processor but it could be that you do not see it inside
your Shopware backend.</p>
</div><div class="paragraph">
<p>You can find more information about Refunds in wallee in our <a href="https://app-wallee.com/en-us/doc/payment/refund" target="_blank">Refund Documentation</a>.</p>
</div> </div>
</div> <div class="section" id="_tokenization">
<div class="section-title">
<h2>
<span class="title-number">6.6</span>Tokenization </h2>
</div>
<div class="section-body">
<div class="paragraph">
<p>In case the payment method supports tokenization you can store the payment details of your customer for future purchases.
In order to use this feature make sure that the <strong>One-Click-Payment Mode</strong> in your <a href="https://app-wallee.com/space/select?target=/payment/method-configuration/list">payment method configuration</a> is set to <code>allow</code> or <code>force</code> storage.</p>
</div><div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
Tokenization is not available for guest checkouts.
</td>
</tr>
</table>
</div> </div>
</div> </div>
</div> <div class="chapter" id="_error_logging">
<div class="chapter-title">
<h1>
<span class="title-number">7</span>Error logging </h1>
</div>
<div class="chapter-body">
<div class="paragraph">
<p>The extension uses the Shopware logging functions which are automatically active in your Shopware store.
The extension will log various unexpected errors or information which can help identify the cause of the error. You can find the logs on the server of your store in the var/log/ folder.</p>
</div> </div>
</div> <div class="chapter" id="_faq">
<div class="chapter-title">
<h1>
<span class="title-number">8</span>FAQ </h1>
</div>
<div class="chapter-body">
<div class="section" id="_how_to_install_the_plugin_using_composer">
<div class="section-title">
<h2>
<span class="title-number">8.1</span>How to install the plugin using composer? </h2>
</div>
<div class="section-body">
<div class="paragraph">
<p>You can install the plugin using composer by updating the <code>composer.json</code> file in the root directory of your Shopware store and wait for Composer to finish updating the dependencies.</p>
</div><div class="listingblock">
<div class="content">
<pre>composer require wallee/shopware-6</pre>
</div>
</div><div class="paragraph">
<p>Once this done, continue with step 2 of the installation process. See <a href="#_installation">Installation</a>.</p>
</div> </div>
</div> <div class="section" id="_how_can_i_make_the_payment_methods_appear_in_the_checkout">
<div class="section-title">
<h2>
<span class="title-number">8.2</span>How can I make the payment methods appear in the checkout? </h2>
</div>
<div class="section-body">
<div class="paragraph">
<p>Make sure that you followed the <a href="#_configuration">Configuration</a> section by stating your wallee space ID and application user’s access information in the Shopware backend. By saving the configuration form the synchronization of the payment methods and the set up of the webhooks are initiated.</p>
</div><div class="paragraph">
<p>If this does not solve the problem, it could be that you use a special fee or coupon module that we do not support. Try to disable this plugin and see if it helps.
The payment methods are only displayed if the plugin’s total calculation matches the actual order total.</p>
</div> </div>
</div> </div>
</div> <div class="chapter" id="_sending_emails_with_flow_builder">
<div class="chapter-title">
<h1>
<span class="title-number">9</span>Sending emails with Flow Builder </h1>
</div>
<div class="chapter-body">
<div class="paragraph">
<p>In order for your emails to send when setting up custom flows using Flow Builder you must ensure that "Send order confirmation email" is disabled (located in the plugin settings).</p>
</div><div class="paragraph">
<p>If you you have already made seperate channel adjustments (using the channel dropdown in the plugin settings) you will have to ensure that the emails are disabled per channel accordingly.</p>
</div> </div>
</div> <div class="chapter" id="_troubleshooting">
<div class="chapter-title">
<h1>
<span class="title-number">10</span>Troubleshooting </h1>
</div>
<div class="chapter-body">
<div class="section" id="_webhook_error_api_version_not_available">
<div class="section-title">
<h2>
<span class="title-number">10.1</span>Webhook error (API version not available) </h2>
</div>
<div class="section-body">
<div class="paragraph">
<p>Webhooks communication fails because of a reply saying HTTP 404 with this or a similar error in the response:
<code>{"errors":[{"code":"0","status":"404","title":"Not Found","detail":"Requested api version v1 not available, available versions are v2, v3."}]}</code></p>
</div><div class="paragraph">
<p>Solution:
The Webhooks have to be updated. Shopware is using an API Version for all "URLs", which has to be updated in case shopware itself was updated.</p>
</div> </div>
</div> </div>
</div> <div class="chapter" id="_support">
<div class="chapter-title">
<h1>
<span class="title-number">11</span>Support </h1>
</div>
<div class="chapter-body">
<div class="paragraph">
<p>If you need help, feel free to contact our <a href="https://app-wallee.com/space/select?target=/support">support</a>.</p>
</div> </div>
</div> </div>
</div>
</div>
<div class="col-right">
<div class="col-right-wrapper">
<div class="table-of-contents">
<ul class="nav">
<li class="nav-level-1">
<a href="#_prerequisites">
<span class="item-number">1</span>
<span class="item-title">Prerequisites</span>
</a>
</li> <li class="nav-level-1">
<a href="#_installation">
<span class="item-number">2</span>
<span class="item-title">Installation</span>
</a>
</li> <li class="nav-level-1">
<a href="#_configuration">
<span class="item-number">3</span>
<span class="item-title">Configuration</span>
</a>
</li> <li class="nav-level-1">
<a href="#_payment_method_configuration">
<span class="item-number">4</span>
<span class="item-title">Payment method configuration</span>
</a>
<ul class="nav">
<li class="nav-level-2">
<a href="#_setup">
<span class="item-number">4.1</span>
<span class="item-title">Setup</span>
</a>
</li> <li class="nav-level-2">
<a href="#_payment_method_rules">
<span class="item-number">4.2</span>
<span class="item-title">Payment method rules</span>
</a>
</li> <li class="nav-level-2">
<a href="#_customization">
<span class="item-number">4.3</span>
<span class="item-title">Customization</span>
</a>
</li> </ul>
</li> <li class="nav-level-1">
<a href="#_state_graph">
<span class="item-number">5</span>
<span class="item-title">State graph</span>
</a>
<ul class="nav">
<li class="nav-level-2">
<a href="#_state_mapping_of_shopware_orders">
<span class="item-number">5.1</span>
<span class="item-title">State mapping of Shopware orders</span>
</a>
<ul class="nav">
<li class="nav-level-3">
<a href="#_general_remarks_regarding_order_statuses">
<span class="item-number">5.1.1</span>
<span class="item-title">General remarks regarding order statuses</span>
</a>
</li> </ul>
</li> <li class="nav-level-2">
<a href="#_state_mapping_of_shopware_payment_status">
<span class="item-number">5.2</span>
<span class="item-title">State mapping of Shopware payment status</span>
</a>
<ul class="nav">
<li class="nav-level-3">
<a href="#_general_remarks_regarding_payment_statuses">
<span class="item-number">5.2.1</span>
<span class="item-title">General remarks regarding payment statuses</span>
</a>
</li> </ul>
</li> <li class="nav-level-2">
<a href="#_state_mapping_of_shopware_delivery_status">
<span class="item-number">5.3</span>
<span class="item-title">State mapping of Shopware delivery status</span>
</a>
</li> </ul>
</li> <li class="nav-level-1">
<a href="#_transaction_management">
<span class="item-number">6</span>
<span class="item-title">Transaction management</span>
</a>
<ul class="nav">
<li class="nav-level-2">
<a href="#_complete_capture_an_order">
<span class="item-number">6.1</span>
<span class="item-title">Complete (capture) an order</span>
</a>
</li> <li class="nav-level-2">
<a href="#_void_a_transaction">
<span class="item-number">6.2</span>
<span class="item-title">Void a transaction</span>
</a>
</li> <li class="nav-level-2">
<a href="#_refund_of_a_transaction">
<span class="item-number">6.3</span>
<span class="item-title">Refund of a transaction</span>
</a>
</li> <li class="nav-level-2">
<a href="#_on_hold_orders">
<span class="item-number">6.4</span>
<span class="item-title">On hold orders</span>
</a>
</li> <li class="nav-level-2">
<a href="#_limitations_of_the_synchronization_between_whitelabelname_and_shopware">
<span class="item-number">6.5</span>
<span class="item-title">Limitations of the synchronization between wallee and Shopware</span>
</a>
</li> <li class="nav-level-2">
<a href="#_tokenization">
<span class="item-number">6.6</span>
<span class="item-title">Tokenization</span>
</a>
</li> </ul>
</li> <li class="nav-level-1">
<a href="#_error_logging">
<span class="item-number">7</span>
<span class="item-title">Error logging</span>
</a>
</li> <li class="nav-level-1">
<a href="#_faq">
<span class="item-number">8</span>
<span class="item-title">FAQ</span>
</a>
<ul class="nav">
<li class="nav-level-2">
<a href="#_how_to_install_the_plugin_using_composer">
<span class="item-number">8.1</span>
<span class="item-title">How to install the plugin using composer?</span>
</a>
</li> <li class="nav-level-2">
<a href="#_how_can_i_make_the_payment_methods_appear_in_the_checkout">
<span class="item-number">8.2</span>
<span class="item-title">How can I make the payment methods appear in the checkout?</span>
</a>
</li> </ul>
</li> <li class="nav-level-1">
<a href="#_sending_emails_with_flow_builder">
<span class="item-number">9</span>
<span class="item-title">Sending emails with Flow Builder</span>
</a>
</li> <li class="nav-level-1">
<a href="#_troubleshooting">
<span class="item-number">10</span>
<span class="item-title">Troubleshooting</span>
</a>
<ul class="nav">
<li class="nav-level-2">
<a href="#_webhook_error_api_version_not_available">
<span class="item-number">10.1</span>
<span class="item-title">Webhook error (API version not available)</span>
</a>
</li> </ul>
</li> <li class="nav-level-1">
<a href="#_support">
<span class="item-number">11</span>
<span class="item-title">Support</span>
</a>
</li> </ul>
</div> </div>
</div>
</div>
</div>
<script type="text/javascript" src="assets/jquery.js"></script>
<script type="text/javascript" src="assets/scrollspy.js"></script>
<script type="text/javascript" src="assets/sticky-kit.js"></script>
<script type="text/javascript" src="assets/highlight.js"></script>
<script type="text/javascript" src="assets/base.js"></script>
</body>
</html>