You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to map each Spree::Payment to a single Payment Intent, and thus have a single Stripe Spree::Payment for a given order that will track all the payment attempts made for the Payment Intent. Stripe recommends having a single payment intent per order.
The content you are editing has changed. Please copy your edits and refresh the page.
The following is the tentative mapping between the states in the two systems, since in Stripe the "failed" state is just going back to the starting point we'll treat anything before a final state as :processing.
Why
Since Stripe considers updates sent via webhooks to be the most reliable source of truth, we need a place in which to track the history of each payment tracking attempts, failures, refusals, successes etc.
The entity that can best take up this role seems to be Spree::Payment.
The text was updated successfully, but these errors were encountered:
What
We need to map each
Spree::Payment
to a single Payment Intent, and thus have a single StripeSpree::Payment
for a given order that will track all the payment attempts made for the Payment Intent. Stripe recommends having a single payment intent per order.Tasks
Dependencies
Mapping between Solidus and Stripe payment states
The following is the tentative mapping between the states in the two systems, since in Stripe the "failed" state is just going back to the starting point we'll treat anything before a final state as
:processing
.Why
Since Stripe considers updates sent via webhooks to be the most reliable source of truth, we need a place in which to track the history of each payment tracking attempts, failures, refusals, successes etc.
The entity that can best take up this role seems to be
Spree::Payment
.The text was updated successfully, but these errors were encountered: