feat: added samsung pay #112
Conversation
| | (_, _, SamsungPay.Not_Started) => <SdkLoadingScreen /> | ||
| | (_, None, _) | ||
| | (Loading, _, _) => | ||
| nativeProp.hyperParams.defaultView && samsungPayValidity->SamsungPay.isSamsungPayValid | ||
| ? <PaymentSheet setConfirmButtonDataRef /> |
There was a problem hiding this comment.
Should we move this to PMListModifier.res as checks for other wallets are also handled there
| protocol: string, | ||
| allowed_brands: array<JSON.t>, | ||
| } | ||
|
|
There was a problem hiding this comment.
Are we getting a new object from backend for samsung pay or we can merge with sessions types?
As @AashuJuspay has all session objects in one type.
There was a problem hiding this comment.
As of current implementation, we have a single session type for session tokens of google pay and apply pay, so added some samsung pay specific fields here
| recurring_payment: bool, | ||
| // payment_shipping_address: paymentShippingAddress, | ||
| // payment_shipping_method: string, | ||
| } |
There was a problem hiding this comment.
How do we handle billing address requirements for a processor?
There was a problem hiding this comment.
We are not collecting it via Samsung Pay, as it will add extra friction of filling all these details in Samsung Pay Sheet. We will either accept that in create or confirm ( via HS SDK)
25harsh
force-pushed
the
main
branch
2 times, most recently
from
3988dd0 to
3230e5e
Compare
Sanskar2001
force-pushed
the
samsung-pay
branch
from
afd0bff to
f4d0ef3
Compare
Added Samsung Pay
TO DO: