[Bug]: /payments/details response payload missing paymentMethod for Twint tokenization

[steindlmedia]

Description

According to Checkout API docs (/payments/details, v71), the response must include a paymentMethod object whenever resultCode is Authorised. For Twint tokenization this field is omitted, while it is returned correctly for the other payment methods we use (e.g., Visa, Mastercard, PayPal).

Steps to reproduce

1. Environment / setup

   • Mobile SDKs: iOS & Android Drop‑in, integrated via the advanced flow.
   • Backend: adyen-java-api-library 34.0.0 talking to Checkout API v71.
   • PSP reference used in this example: DVBTSD7TXRP7ZG75.

2. Create and complete a Twint payment

   • Start a payment from the mobile Drop‑in.
   • Wait until the Twint app confirms the payment
   • POST the returned details object to https://checkout-test.adyen.com/v71/payments/details.

3. Observe the response

   {
     "resultCode": "Authorised"
     // expected but missing ↓
     // "paymentMethod": { "type": "twint" }
   }
   

Actual behavior

paymentMethod object is absent in the response for Twint payments.

Expected behavior

paymentMethod object (with at least the type property) is present whenever resultCode is Authorised, consistent with documentation and other payment methods.

Code snippet or screenshots (if applicable)

No response

Adyen Java API Library version

34.0.0

Java version

21

Operating System

Linux

Additional context

This inconsistency prevents us from correctly persisting the payment method in our database and is blocking a broader Adyen rollout in one of our biggest regions.
Please investigate and provide a fix or workaround as soon as possible.

Thank you for looking into this!

[gcatanese]

Hello Alexander, apologies for the late reply. Do you still experience the problem? Is this on LIVE or TEST?

[steindlmedia]

Hey @gcatanese,
we are still experiencing this issue both on TEST (e.g. WVGFT7W79T8SXC75) and LIVE.