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
[BUG] starting a transaction of paymentMethod.type: "afterpay_default" is not possible due to a mismatch between the required payload and the PaymentRequest type
#1379
Open
pvaneveld opened this issue
Aug 1, 2024
· 0 comments
Describe the bug
starting a transaction of paymentMethod.type: "afterpay_default" is not possible due to a mismatch between the required payload - which should contain shopperName.gender - and the PaymentRequest type - which does not contain shopperName.gender
To Reproduce
start a transaction (PaymentsApi.payments) of paymentMethod.type: "afterpay_default" using "@adyen/api-library": "18.1.0",
use a payload compatible with the PaymentRequestType, containing all the fields required for this payment method type. See the payload below as a reference
pvaneveld
changed the title
[BUG]
[BUG] starting a transaction of paymentMethod.type: "afterpay_default" is not possible due to a mismatch between the required payload
Aug 2, 2024
pvaneveld
changed the title
[BUG] starting a transaction of paymentMethod.type: "afterpay_default" is not possible due to a mismatch between the required payload
[BUG] starting a transaction of paymentMethod.type: "afterpay_default" is not possible due to a mismatch between the required payload and the PaymentRequest type
Aug 2, 2024
Describe the bug
starting a transaction of
paymentMethod.type: "afterpay_default"
is not possible due to a mismatch between the required payload - which should containshopperName.gender
- and thePaymentRequest
type - which does not containshopperName.gender
To Reproduce
PaymentsApi.payments
) ofpaymentMethod.type: "afterpay_default"
using"@adyen/api-library": "18.1.0",
PaymentRequestType
, containing all the fields required for this payment method type. See the payload below as a referenceshoperName
object, e.g.gender: "MALE"
, the same issue occurs.Expected behavior
PaymentRequest
type does not result in errors about fields that are not present in this type.Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: