Add CPM toggle to playground #4633
Conversation
| if playgroundController.settings.merchantCountryCode == .US { | ||
| SettingView(setting: $playgroundController.settings.customPaymentMethods) | ||
| } |
There was a problem hiding this comment.
Seems like it's possible to turn this on while in US mode, then switch to another country and the setting will still be activated?
There was a problem hiding this comment.
Yeah it could! It would no-op internally, but better to not set it, updated this.
| switch settings.customPaymentMethods { | ||
| case .on: | ||
| // Obtained from https://dashboard.stripe.com/settings/custom_payment_methods | ||
| let customPaymentMethodType = PaymentSheet.CustomPaymentMethodConfiguration.CustomPaymentMethodType(id: "cpmt_1QpId5Lu5o3P18ZpLwSqMXws", |
There was a problem hiding this comment.
Maybe we have this vended from our merchant backend, and we add a parameter so we can test 1 or many custom payment methods? (e.g. the setting for customPaymentMethods is a value between 0-3 rather than a boolean)
There was a problem hiding this comment.
Hm, it feels needlessly complex tbh. Even if we needed multiple CPMs I'd rather have them defined client-side, this is more consistent with how merchants will integrate as well. Although nothing stopping them from using a backend to vend them as you suggested.
| _ billingDetails: STPPaymentMethodBillingDetails | ||
| ) async -> PaymentSheetResult { | ||
| return await withCheckedContinuation { continuation in | ||
| handleExternalPaymentMethod(type: customPaymentMethodType.id, billingDetails: billingDetails) { result in |
There was a problem hiding this comment.
Will handling custom payment methods always be the same as handling external payment methods? Or will it eventually differ
There was a problem hiding this comment.
Handling confirmation of CPMs and EPMs will be the same. The merchant is responsible for handling the confirmation, then returning back to us the final result.
Summary
Motivation
Testing
Changelog
N/A