Plugin cannot connect to Adyen LIVE: no setting for the live endpoint URL prefix
@kccrcodes is already working on this.
Since Nov 18, 2026.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 74/100
Research direction
Start with AdyenSDKClientImpl.java and AdyenConfigProperties.java to trace how tenant settings reach the Adyen client; check README.md for the documented configuration. Add support for the merchant's LIVE URL prefix and pass it when building the client. Update or add tests for client configuration, then confirm the README explains the setting and LIVE operations can use the merchant endpoint.
Written by the indexing model from the issue text.
Description
Description
With enviroment=LIVE, every call from the plugin to Adyen (checkout session, purchase, void, refund) fails before reaching Adyen. Adyen's LIVE Checkout API address is unique per merchant (https://<prefix>-checkout-live.adyenpayments.com/checkout). The Adyen SDK requires this prefix for LIVE, but the plugin has no setting for it and never passes one. TEST is unaffected because it uses a single fixed address.
Steps to reproduce
- Upload the tenant Adyen config with
org.killbill.billing.plugin.adyen.enviroment=LIVEand a LIVE API key and merchant account. - Trigger any Adyen operation for that tenant: a checkout session, a recurring purchase, a refund or a void.
Expected
The plugin calls the merchant's LIVE endpoint, https://<prefix>-checkout-live.adyenpayments.com/checkout/v68/..., and the operation reaches Adyen.
Actual
The Adyen client cannot be created and the operation fails with:
IllegalArgumentException: Please provide your unique live url prefix on the setEnvironment() call on the Client or provide checkoutEndpoint in your config object.
No request reaches Adyen.
Evidence
Plugin
- The client is created with the API key and environment only, with no prefix:
AdyenSDKClientImpl.java#L47-L50 - The tenant config has no prefix or endpoint property:
AdyenConfigProperties.java#L52-L59 - The README documents only
TEST/LIVE:README.md#L87 - The client is built for every Adyen operation (
GatewayProcessorFactory.java#L25), called from:
Adyen SDK 17.3.0
- For LIVE without a prefix, the checkout endpoint is set to
null:Client.java#L205-L215 - Reading a
nullendpoint throws:Config.java#L165-L171
Reproduced with SDK 17.3.0, building the client the same way as the plugin:
TEST, no prefix -> https://checkout-test.adyen.com/checkout/v68/sessions
LIVE, no prefix -> IllegalArgumentException: Please provide your unique live url prefix ...
LIVE + prefix -> https://abc123-XYZ-checkout-live.adyenpayments.com/checkout/v68/sessions
- Dominant language
- Java
- Stars
- 11
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from killbill/killbill-adyen-plugin
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Amount sent to Adyen is wrong unless it has exactly two decimal places (e.g. 10 is charged as 0.10)Open
Difficulty 3/5 1-2 days Newbie friendliness 76/100
killbill/killbill-adyen-plugin#152 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 56/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
All issues in killbill/killbill-adyen-plugin
Similar issues
-
component/data-layer
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
RegistryExceptionHandler uses self-referencing basePackageClasses instead of a controller classOpenbug finsim-registry good-first-issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
? - Needs Triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
NVIDIA/cudf-spark#17063 ·
Maintainers usually reply within 2 days
-
status:pending type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100