Skip to content

Commit 76e9df1

Browse files
committed
Mention a single payment per transaction in payments overview
1 parent fd403df commit 76e9df1

1 file changed

Lines changed: 8 additions & 1 deletion

File tree

  • content/concepts/payments/payments-overview

content/concepts/payments/payments-overview/index.mdx

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ description:
66
published: true
77
---
88

9-
import { Steps } from 'nextra/components';
9+
import { Callout, Steps } from 'nextra/components';
1010

1111
# Payments
1212

@@ -176,6 +176,13 @@ over the transaction process. In terms of payments, you can make
176176
parallel paths depending on your payment strategy, and you can fine-tune
177177
the timeline of different actions to suit your marketplace.
178178

179+
<Callout type="info">
180+
Even when using parallel paths, a single transaction can only ever
181+
have a single PaymentIntent associated with it. When customizing your
182+
transaction process, make sure that a single path can only process a
183+
single payment to avoid issues.
184+
</Callout>
185+
179186
You can edit the transaction processes on your marketplace with
180187
[Sharetribe CLI](/how-to/transaction-process/edit-transaction-process-with-sharetribe-cli/).
181188
If you use Sharetribe Web Template, you will also need to make some

0 commit comments

Comments
 (0)