v3
let us not mention the version. instead link to create payment reference
8 Matching Annotations
- Last 7 days
-
redpin-preview-71d44bbd-42f7-4f80-bb7c-253f31fa1405.docs.buildwithfern.com redpin-preview-71d44bbd-42f7-4f80-bb7c-253f31fa1405.docs.buildwithfern.com
-
-
v3
no version
-
Sent when the status of a payment changes at various stages of the payment journey.
Let us add vertical navigation on the right for the items in the current page
-
Payload
Let us move the Payload to the top , so that the user gets immediate knowledge on landing on the apge.
-
Payment Status Updated Event
Our doc is primarily concentrated around the workflow. But most of the competitor documentation is based on events. Example -- https://docs.wise.com/guides/developer/webhooks/event-types https://docs.trustly.com/api/credit-notification
Should we think restructuring our docs also to be aligned with competitor structure
-
Not present
Present when provided
-
Third Party)
We should explain the user what Third party Payment is . In api guide, if we have something, then we should point the user there
-
hird Party Payment (Session-Based): Payments created via hosted payment sessions (always third-party payments)
Please link it to an api for creating the session.
-