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.

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

DX-2260: Added new events in history node #2018

Merged
merged 1 commit into from
Nov 1, 2023

Conversation

arebra
Copy link
Member

@arebra arebra commented Nov 1, 2023

No description provided.

@arebra arebra requested a review from a team as a code owner November 1, 2023 15:26
@probot-autolabeler probot-autolabeler bot added the documentation Improvements or additions to documentation label Nov 1, 2023
| {% f PaymentReversedFailed, 0 %} | Will occur when the merchant has tried - but failed - to do a reversal of the **fully** captured authorization amount. The number parameter might be available on this event. If present, it will point to a number in the `financialTransaction` field for easy linking. |
| {% f PaymentPartiallyReversedFailed, 0 %} | Will occur when the merchant has tried - but failed - to do a partial reversal of the captured authorization amount. The number parameter might be available on this event. If present, it will point to a number in the `financialTransaction` field for easy linking. |
| {% f PaymentCancelledFailed, 0 %} | Will occur when the merchant has tried - but failed - to do a **full** cancel of the authorization amount. The number (nullable) of this event will point to a number in the `financialTransaction` node for easy linking. |
| {% f PaymentPartiallyCancelledFailed, 0 %} | Will occur when the merchant has tried - but failed - to cancel the remaing (uncaptured) parts of authorizated amount. The number (nullable) of this event will point to a number in the `financialTransaction` node for easy linking. |
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[misspell] reported by reviewdog 🐶
"remaing" is a misspelling of "remaining"

@arebra arebra merged commit e156570 into develop Nov 1, 2023
24 of 27 checks passed
@arebra arebra deleted the feature/dx-2260_add_new_history_events branch November 1, 2023 20:36
Copy link
Contributor

mergify bot commented Nov 1, 2023

Thank you @arebra for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant