# Developer Guide Published articles for Developer Guide. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Payment Gateway Integration: A Developer's Guide DevFeed: [Payment Gateway Integration: A Developer's Guide]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-13T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Back end](), [Code](), [Front end](), [Software as a service]() Tags: [architecture](), [backend](), [billing](), [checkout](), [developer-guide](), [developers](), [gateway](), [guide](), [integration](), [payments](), [tax](), [testing](), [webhooks](), [workflows]() ### AI overview A developer guide to production-ready payment gateway integrations, covering checkout initiation, customer and order mapping, payment state management, webhook processing, fulfillment, recovery, testing, tax-aware billing, and checkout model selection. It also discusses using a Merchant of Record such as Dodo Payments. ### Source excerpt Learn how to plan, build, and ship a payment gateway integration with checkout, webhooks, tax, and post-payment workflows that scale globally. ## Payment API: How to Accept Payments Programmatically DevFeed: [Payment API: How to Accept Payments Programmatically]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-13T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [API](), [Automation](), [event driven](), [SDKs](), [Back end](), [Developer experience]() Tags: [api](), [apis](), [automation](), [backend](), [developer](), [developer-guide](), [guide](), [how-to](), [merchant-of-record](), [payment](), [payments](), [saas](), [subscription](), [usage-based-billing](), [webhooks](), [workflows]() ### AI overview A practical guide to using payment APIs for programmatic checkout, subscriptions, usage-based billing, webhook-driven workflows, and keeping product access synchronized with payment state. ### Source excerpt A practical guide to using a payment API for programmatic checkout, billing automation, webhook handling, and scalable payment workflows. ## How to Set Up Webhooks for Payment Notifications DevFeed: [How to Set Up Webhooks for Payment Notifications]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-13T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [API](), [Express](), [HTTP](), [Node.js](), [JSON](), [Software as a service]() Tags: [api](), [developer-guide](), [express](), [how-to](), [http](), [json](), [node](), [payment](), [saas](), [webhooks]() ### AI overview A guide to using payment webhooks instead of polling to receive payment events promptly. It explains webhook delivery, endpoint setup with Node.js and Express, event handling, retries, idempotency, and signature verification. ### Source excerpt Learn how webhooks work for payment notifications, how to set up endpoints, verify signatures, and handle payment events reliably in your SaaS application. ## How to Test Payment Integrations: Sandbox and Testing Guide DevFeed: [How to Test Payment Integrations: Sandbox and Testing Guide]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-13T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Testing](), [CI/CD](), [API]() Tags: [ci-cd](), [developer-guide](), [guide](), [payment](), [sandbox](), [testing]() ### AI overview A developer guide to testing payment integrations across sandbox and production environments. It covers test API keys, test card numbers, payment success and failure scenarios, and CI/CD testing strategies. ### Source excerpt A developer's guide to testing payment integrations - sandbox environments, test card numbers, edge case testing, and CI/CD workflows for payment flows. ## Credit Card Decline Codes: What They Mean and How to Fix Them DevFeed: [Credit Card Decline Codes: What They Mean and How to Fix Them]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-13T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [API](), [Authentication](), [Support](), [Docker Compose]() Tags: [api](), [authentication](), [churn](), [developer-guide](), [developers](), [guide](), [how-to](), [payments](), [recovery](), [retry](), [revenue]() ### AI overview A practical guide for developers and revenue teams on interpreting credit card decline codes, grouping them into operational categories, and choosing appropriate recovery actions. It emphasizes customer self-correction, safe retries with idempotency keys, and distinguishing recoverable declines from generic issuer or authentication failures. ### Source excerpt A practical guide to credit card decline codes for developers and revenue teams, including what common declines mean and how to reduce failed payments. ## Xcode 26 Migration, UIScene Rollout, Initializr Localization Bundles, and More DevFeed: [Xcode 26 Migration, UIScene Rollout, Initializr Localization Bundles, and More]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-03-07T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Xcode](), [iOS](), [Localization (l10n)](), [Internationalization (i18n)](), [migration](), [Android](), [Documentation]() Tags: [adaptive](), [android](), [developer-guide](), [ios](), [migration](), [tooling](), [updates](), [xcode]() ### AI overview A Codename One update reports a staged Xcode 26 migration, initial UIScene support for testing, and Initializr-generated localization resource bundles. It also covers localization workflow improvements, Android adaptive icons, iOS notification replacement fixes, and UI and resource tooling updates. ### Source excerpt We started the Xcode 26 migration rollout, Initializr now generates localization resource bundles, and there are several useful platform updates you should know about. ## Media Controls and Print Developer Guide DevFeed: [Media Controls and Print Developer Guide]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-10-10T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [pdf](), [Playback](), [ui](), [amazon]() Tags: [amazon](), [developer](), [developer-guide](), [native](), [pdf](), [playback](), [regression](), [ui](), [update]() ### AI overview The article describes a print-optimized PDF version of the Codename One developer guide, available as a physical book through Amazon KDP, with fewer pages but the same information. It also reports improved media stability, support for native video controls, and ongoing fixes for regressions in the on-top side menu. ### Source excerpt I did a lot of work on the developer guide PDF making it more suitable to print, as part of this work I submitted the guide to Amazon's KDP which means you can now order a physical book of the developer guide. I reduced the page count significantly for lower cost and image size requirements. As a result the book is much smaller but contains the exact same information in a denser package. ## Improving Cross-Platform Mobile App UI and Developer Education DevFeed: [Improving Cross-Platform Mobile App UI and Developer Education]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-06-18T00:00:00Z Content type: opinion Language: en Sources: [CodeName One]() Topics: [Mobile](), [cross-platform](), [User experience (UX)](), [Bootcamp]() Tags: [cross-platform](), [developer-guide](), [developers](), [mobile](), [pitfalls](), [ui]() ### AI overview The author discusses the difficulty of creating polished mobile app interfaces with cross-platform tools. They describe lessons from a bootcamp and plans to improve developer education by focusing on real apps, practical design, and clearer tutorials. ### Source excerpt I talk to a lot of mobile developers or those who are starting out in the field and by far the number one problem is getting a refined sublime app. There are too many difficulties and pitfalls along the way and the end result is often "sub par" in terms of the UI you want to achieve. We too bear responsibility for that. We focus too much on the technology and too little on making "gorgeous" easy. I want you to join me in changing that narrative... ## Security Section DevFeed: [Security Section]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-02-21T00:00:00Z Content type: news Language: en Sources: [CodeName One]() Topics: [Security]() Tags: [developer-guide](), [security](), [update]() ### AI overview Codename One has added a security section to its developer guide, consolidating general security information and details about available security measures. The section can be edited through the project wiki. ### Source excerpt We've had a lot of security related posts in the past few months as we refined many edge cases with some customers. These posts are difficult to comb through as they are all over the place, and it's hard to get a glance of "what's available." So we added a new security section to the developer guide which adds some general information about Codename One security and includes most of the details about what you can do in terms of security. ## Questions of the Week 42 DevFeed: [Questions of the Week 42]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-02-09T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Pull Request](), [Code](), [Documentation]() Tags: [code](), [developer-guide](), [pull-request]() ### AI overview A weekly Codename One update discusses delayed release timing because of extensive ParparVM and 64-bit build changes, potential regressions, iOS redirect changes, and recent pull requests. It encourages community contributions, including code changes, typo fixes, and developer guide edits. ### Source excerpt This week's update will go out a bit late or maybe even tomorrow. The reason for the postponing is the scope of the changes. We've made a lot of changes to ParparVM and we are very concerned that there will be regressions. So we would like this update to go in later in case we need to revert that work. Steve wrote a detailed post about the changes he made to ParparVM which we will post next week... ## Codename One Questions, Features, Fixes, and Mobile Development Topics DevFeed: [Codename One Questions, Features, Fixes, and Mobile Development Topics]() Original publisher: [Read original article]() Author: Shai Almog Published: 2016-12-08T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Development](), [Mobile](), [App](), [client]() Tags: [app](), [developer](), [developer-guide](), [development](), [github](), [mobile](), [support]() ### AI overview A Codename One weekly update covers a small set of new features and fixes, answers questions about Android text-field actions, app minimization, lifecycle concepts, and command icon-gap variables, and points readers to GitHub Discussions. ### Source excerpt This week has been a bit slow with features and external progress as we've started to focus on the issues for the January release of 3.6. During December we'll probably pause blogging between December 22nd and January 2nd as it would probably get lost to the ether for most of our audience. I'll still be working and at least some of our team will, but we'll focus on support and features/issues which will give us a lot to write about when we get back. ## Tip: Disable Google Play Services DevFeed: [Tip: Disable Google Play Services]() Original publisher: [Read original article]() Author: Shai Almog Published: 2016-10-09T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Google Play](), [App](), [APK]() Tags: [apk](), [app-size](), [developer-guide](), [google-play]() ### AI overview A Codename One build hint can disable included Google Play Services when an app does not use Ads, Push, Maps, or Location. The article states that removing the unused services can reduce the final APK by about 1.5 MB and avoid an ads-framework warning when appropriate. ### Source excerpt Google Play Services is a proprietary set of tools that Google licenses to vendors under limited conditions. In recent years more and more features go into Google Play Services making it harder to build an app without it. In our effort to "do the right thing" we include some of the Google Play Services tools into applications to remain compatible with code that requires these libraries. This also makes some features (such as location) work better. However, if you don't use: Ads, Push, Maps or Location then you might not need Google Play Services at all...