mirror of
https://github.com/openfoodfoundation/openfoodnetwork
synced 2026-01-25 20:46:48 +00:00
23b0885f4b
This makes them more changeable and robust. Ruby will raise NoMethodError on typos while it'll silently create a new ivar without us noticing. Also, in my experience, a reader method gives more room to future refactorings and eases testing because methods are easier to stub.
33 lines
709 B
Ruby
33 lines
709 B
Ruby
# frozen_string_literal: true
|
|
|
|
class ProcessPaymentIntent
|
|
def initialize(payment_intent, order)
|
|
@payment_intent = payment_intent
|
|
@order = order
|
|
@last_payment = OrderPaymentFinder.new(order).last_payment
|
|
end
|
|
|
|
def call!
|
|
return unless valid?
|
|
|
|
last_payment.update_attribute(:cvv_response_message, nil)
|
|
last_payment.complete!
|
|
end
|
|
|
|
private
|
|
|
|
attr_reader :order, :payment_intent, :last_payment
|
|
|
|
def valid?
|
|
order.present? && valid_intent_string? && matches_last_payment?
|
|
end
|
|
|
|
def valid_intent_string?
|
|
payment_intent&.starts_with?("pi_")
|
|
end
|
|
|
|
def matches_last_payment?
|
|
last_payment&.state == "pending" && last_payment&.response_code == payment_intent
|
|
end
|
|
end
|