Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve description about supportedPaymentFlows behavior #1177

Merged
merged 4 commits into from
Jun 19, 2024
Merged

Improve description about supportedPaymentFlows behavior #1177

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
15d5409
add warning about empty supportedPaymentFlows
peelar Jun 11, 2024
25e7c2e
chore: Update explanation of `INTERACTIVE` payment flow in stored pay…
peelar Jun 13, 2024
3958d4d
Update docs/developer/extending/webhooks/synchronous-events/stored-pa…
aniav Jun 14, 2024
a732259
Add suggestion from CR to versioned_docs
aniav Jun 14, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions docs/developer/extending/webhooks/synchronous-events/stored-payment-method.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,8 +113,13 @@ The response in this case should have the following structure:

Below are the possible `supportedPaymentFlows` values and their explanations:

- `INTERACTIVE` - Payment method can be used for 1 click checkout - it's prefilled in checkout
form (might require additional authentication from user).
- `INTERACTIVE` - When the user needs to be present to prove the ownership of the payment method (instead of, for example, a subscription-based payment which does not require user interaction).

:::warning

There is no default payment flow. If the `supportedPaymentFlows` list is empty, the payment method will not be returned.

:::

## Delete stored payment method requested

Expand Down
11 changes: 7 additions & 4 deletions ...n-3.x/developer/extending/webhooks/synchronous-events/stored-payment-method.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,8 +113,13 @@ The response in this case should have the following structure:

Below are the possible `supportedPaymentFlows` values and their explanations:

- `INTERACTIVE` - Payment method can be used for 1 click checkout - it's prefilled in checkout
form (might require additional authentication from user).
- `INTERACTIVE` - When the user needs to be present to prove the ownership of the payment method (instead of, for example, a subscription-based payment which does not require user interaction).

:::warning

There is no default payment flow. If the `supportedPaymentFlows` list is empty, the payment method will not be returned.

:::

## Delete stored payment method requested

Expand Down Expand Up @@ -258,8 +263,6 @@ The application should return the status of the initialization and optionally `d
}
```

http://localhost:3000/docs/3.x/api-reference/payments/objects/payment-gateway-initialize-tokenization-error

The `result` field is an enum value of [PaymentGatewayInitializeTokenizationResultEnum](api-reference/payments/enums/payment-gateway-initialize-tokenization-result.mdx). In the event of returning a failure `result`, the `errors` message will be attached to the [error](api-reference/payments/objects/payment-gateway-initialize-tokenization.mdx) returned by the [paymentGatewayInitializeTokenization](api-reference/payments/mutations/payment-gateway-initialize-tokenization.mdx) mutation.

## Initialize payment method tokenization
Expand Down
Loading