<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>AndDone.js &amp; UI Components Archives - AndDone</title>
	<atom:link href="https://www.anddone.com/category/embedded-and-branded-payment-experiences/anddone-js-and-ui-components/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.anddone.com/category/embedded-and-branded-payment-experiences/anddone-js-and-ui-components/</link>
	<description>Powering Insurance Payments with AndDone</description>
	<lastBuildDate>Mon, 06 Apr 2026 22:31:23 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.3</generator>

<image>
	<url>https://www.anddone.com/wp-content/uploads/2025/09/cropped-AndDone_Logo_Secondary_Color-1-32x32.png</url>
	<title>AndDone.js &amp; UI Components Archives - AndDone</title>
	<link>https://www.anddone.com/category/embedded-and-branded-payment-experiences/anddone-js-and-ui-components/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>PROD Release &#8211; Angular Version Upgrade (AN_ANGUPD_V1)</title>
		<link>https://www.anddone.com/prod-release-angular-version-upgrade-an_angupd_v1/</link>
		
		<dc:creator><![CDATA[Samuel Yang]]></dc:creator>
		<pubDate>Thu, 26 Feb 2026 09:00:00 +0000</pubDate>
				<category><![CDATA[AndDone.js & UI Components]]></category>
		<category><![CDATA[Embedded & Branded Payment Experiences]]></category>
		<category><![CDATA[Product Updates & Status]]></category>
		<category><![CDATA[Release Notes]]></category>
		<category><![CDATA[Angular]]></category>
		<category><![CDATA[Anytime Payments]]></category>
		<category><![CDATA[Bug Fix]]></category>
		<category><![CDATA[Encryption]]></category>
		<category><![CDATA[For Developers]]></category>
		<category><![CDATA[NPM]]></category>
		<guid isPermaLink="false">https://www.anddone.com/prod-release-angular-version-upgrade-an_angupd_v1/</guid>

					<description><![CDATA[<p>Angular version upgrade (v15 to v20), NPM package consolidation, client-side payload encryption, and Anytime Portal bug fixes.</p>
<p>The post <a href="https://www.anddone.com/prod-release-angular-version-upgrade-an_angupd_v1/">PROD Release &#8211; Angular Version Upgrade (AN_ANGUPD_V1)</a> appeared first on <a href="https://www.anddone.com">AndDone</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<h2 id="block-Lb2WQG8VF3" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.375rem] font-bold">Upgrades the Payment Portal From Angular v15 to v20</h2>



<h4 id="block-Fx7h1XzJhA" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold">What&#8217;s New</h4>



<p id="block-oZ8ysRd7R7" class="wp-block-nectar-blocks-text nectar-blocks-text font-claude-response-body break-words whitespace-normal leading-[1.7]">The Anytime Payment Portal has been upgraded from Angular version 15 to version 20. This brings the portal in line with the current Angular release, incorporating the framework improvements, performance enhancements, and security patches introduced across the v16–v20 range.</p>



<h4 id="block-cMZcuvsQxj" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold">Why It Matters</h4>



<p id="block-fJajtKHVJ3" class="wp-block-nectar-blocks-text nectar-blocks-text font-claude-response-body break-words whitespace-normal leading-[1.7]">Before this upgrade, the portal was running on an Angular version that no longer receives active support. You can now build against and integrate with a portal that runs on a current, actively maintained Angular version, reducing compatibility friction and exposure to unpatched vulnerabilities.</p>



<h4 id="block-gLGushUre5" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold">Upgrade</h4>



<ol class="wp-block-list [li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-decimal flex flex-col gap-1 pl-8 mb-3">
<li>Ensure any custom Angular components or libraries embedded in or alongside the portal are compatible with Angular v20.</li>



<li>Review any peer dependencies in your integration that declared a constraint on Angular v15 and update them accordingly.</li>



<li>Re-test any portal customizations or overrides that interact with Angular lifecycle hooks, routing, or change detection, as behavior in these areas evolved between v15 and v20.</li>
</ol>



<h2 id="block-5rxEJLrHwB" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.375rem] font-bold">Introduces a Centralized Shared NPM Package for Angular Micro-Frontends</h2>



<h4 id="block-akftL4grzY" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold">What&#8217;s New</h4>



<p id="block-z6NaIge1H8" class="wp-block-nectar-blocks-text nectar-blocks-text font-claude-response-body break-words whitespace-normal leading-[1.7]">A new shared NPM package centralizes common Angular code — including services, interceptors, components, pipes, constants, and enums — that was previously duplicated across multiple micro-frontend applications. All Angular 19+ micro-frontends now consume this single package instead of maintaining their own copies of shared logic.</p>



<h4 id="block-f8qNQwnObM" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold">Why It Matters</h4>



<p id="block-A4LtDHYVuu" class="wp-block-nectar-blocks-text nectar-blocks-text font-claude-response-body break-words whitespace-normal leading-[1.7]">Before this change, the same code existed in multiple places, meaning a bug fix or enhancement had to be applied and tested in every application separately. You can now rely on a single source of truth for shared functionality, making updates faster and reducing the risk of inconsistencies across applications.</p>



<h4 id="block-8KaAaZML67" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold">Upgrade</h4>



<ol class="wp-block-list [li_&amp;]:mb-0 [li_&amp;]:mt-1 [li_&amp;]:gap-1 [&amp;:not(:last-child)_ul]:pb-1 [&amp;:not(:last-child)_ol]:pb-1 list-decimal flex flex-col gap-1 pl-8 mb-3">
<li>Remove any locally duplicated copies of shared services, interceptors, components, pipes, constants, or enums from your micro-frontend application.</li>



<li>Add the new shared package as a dependency in your <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">package.json</code>.</li>



<li>Update import paths in your application to reference the shared package rather than local copies.</li>



<li>Run your test suite to confirm no regressions from the import path changes.</li>
</ol>



<h2 id="block-LEAhVnmbvk" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.375rem] font-bold">Updates the Shared NPM Package to Support Consumer Application Requirements</h2>



<h4 id="block-aLlxEnI8zz" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold">What&#8217;s New</h4>



<p id="block-jYAMcLmUAI" class="wp-block-nectar-blocks-text nectar-blocks-text font-claude-response-body break-words whitespace-normal leading-[1.7]">The centralized shared NPM package has been extended to include additional common functionality required by the consumer-facing Angular application. These additions ensure the package covers the full breadth of shared logic needed across the application suite, not just the initial set of micro-frontends.</p>



<h4 id="block-UKZO8lInb8" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold">Why It Matters</h4>



<p id="block-SoI7spJUIo" class="wp-block-nectar-blocks-text nectar-blocks-text font-claude-response-body break-words whitespace-normal leading-[1.7]">You can now use the shared package as the single dependency for common Angular code across both existing micro-frontends and the consumer application, without needing to maintain parallel implementations.</p>



<h2 id="block-eEJMyj8MWd" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.375rem] font-bold">Adds Client-Side Payload Encryption for Payment Submission</h2>



<h4 id="block-BMxPJtDNOX" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold">What&#8217;s New</h4>



<p id="block-CqWBls5LQT" class="wp-block-nectar-blocks-text nectar-blocks-text font-claude-response-body break-words whitespace-normal leading-[1.7]">The payment submission API now supports full client-side payload encryption. Before a payment request is sent, the entire request body is encrypted on the client using a public key. The payload is only decrypted by backend services upon receipt. This behavior is controlled by a feature flag named cryptography — when the flag is on, all payment request payloads are encrypted in transit; when off, payloads are sent as plain text matching the existing behavior.</p>



<h4 id="block-1MdR3gY0zX" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold">Why It Matters</h4>



<p id="block-7l16gI7QB2" class="wp-block-nectar-blocks-text nectar-blocks-text font-claude-response-body break-words whitespace-normal leading-[1.7]">Before this change, payment request payloads were transmitted without client-side encryption, relying solely on transport-layer security. You can now enable end-to-end payload encryption for payment submissions, significantly reducing the risk of sensitive payment data being exposed at any intermediate layer.</p>



<h4 id="block-iwmzwH7v2E" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold">Changes</h4>



<p id="block-RcpXXicGon" class="wp-block-nectar-blocks-text nectar-blocks-text font-claude-response-body break-words whitespace-normal leading-[1.7]">Parameter: Request body of POST /payment Change type: Modified — when the cryptography feature flag is enabled, the entire request payload is encrypted before transmission and must be decryptable by the backend using the corresponding private key. When the flag is disabled, existing behavior is preserved.</p>



<h2 id="block-csn7AkB74a" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.375rem] font-bold">Fixes Stale Inline Validation Errors When Switching Payment Method Tabs</h2>



<h4 id="block-ZiFsErFd8q" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold">What&#8217;s New</h4>



<p id="block-hDGIaXqMQK" class="wp-block-nectar-blocks-text nectar-blocks-text font-claude-response-body break-words whitespace-normal leading-[1.7]">On the payment method selection page, inline validation error messages for Banking Type and Account Type fields were not cleared when a user navigated from the Card tab to the ACH tab. The form now correctly resets these error states on tab switch, so only errors relevant to the currently active tab are shown.</p>



<h4 id="block-ql4WXEVVWx" class="wp-block-nectar-blocks-text nectar-blocks-text text-text-100 mt-3 -mb-1 text-[1.125rem] font-bold">Why It Matters</h4>



<p id="block-1poFKPbSLL" class="wp-block-nectar-blocks-text nectar-blocks-text font-claude-response-body break-words whitespace-normal leading-[1.7]">Before this fix, users switching from the Card tab to the ACH tab would see leftover error messages from the Card form, creating a confusing and misleading experience. Validation errors now only appear in the context of the tab the user is actively filling out.</p>



<div class="wp-block-nectar-blocks-divider nectar-blocks-divider" id="block-1gjWWepPLd"><div class="nectar-blocks-divider__inner"><div class="nectar__bg-layers parent-block-block-1gjWWepPLd"><div class="nectar__bg-layer nectar__bg-color"></div></div><span class="nectar-blocks-divider__line"></span></div></div>



<p id="block-TdXgvH3rEj" class="wp-block-nectar-blocks-text nectar-blocks-text"><strong>Release Date: </strong>Feb 26th, 2026</p>



<p id="block-6t8RdyYdiJ" class="wp-block-nectar-blocks-text nectar-blocks-text"><strong>Release Status: </strong>Deployed to PROD</p>



<p id="block-nGrYAYL7es" class="wp-block-nectar-blocks-text nectar-blocks-text">This release contains the technical upgrades such as angular version upgrade (v15 to v20), NPMPackage for common code from UI, NPM package update, Client-Side Payload Encryption.</p>



<h4 id="block-iq6TZo4lWH" class="wp-block-nectar-blocks-text nectar-blocks-text">[AN-38395] &#8211; Anytime Payments Angular Upgrade</h4>



<p id="block-j6dDqOUiBw" class="wp-block-nectar-blocks-text nectar-blocks-text">Upgraded the Anytime Payment Portal from Angular v15 tov20.</p>



<p id="block-QnQ9YRnNnD" class="wp-block-nectar-blocks-text nectar-blocks-text">No</p>



<h4 id="block-AP3HBZaRhJ" class="wp-block-nectar-blocks-text nectar-blocks-text">[AN-30796] &#8211; NPM Package &#8211; for common code from UI</h4>



<p id="block-QagChqMmN4" class="wp-block-nectar-blocks-text nectar-blocks-text">Introduced a centralized shared package for all Angular 19MFEs to eliminate duplicate common code (services,interceptors, components, pipes, constants, enums).</p>



<p id="block-ZI9Gi5aY3M" class="wp-block-nectar-blocks-text nectar-blocks-text"><strong>This change ensures:</strong></p>



<p id="block-PR4zHYwRXa" class="wp-block-nectar-blocks-text nectar-blocks-text">Single source of truth<br>Improved consistency across MFEs<br>Simplified maintenance and bug fixes<br>Easier version upgrades for all applications</p>



<p id="block-jklkN5HvoI" class="wp-block-nectar-blocks-text nectar-blocks-text">No</p>



<h4 id="block-uomtBF0mhf" class="wp-block-nectar-blocks-text nectar-blocks-text">[AN-35616]- Update NPM Package to accommodate other application changes </h4>



<p id="block-ElOeMEdRnv" class="wp-block-nectar-blocks-text nectar-blocks-text">Changes to the NPM package to support new commonfunctionality required for the consumer Angular application.</p>



<p id="block-PxwzQFcLLJ" class="wp-block-nectar-blocks-text nectar-blocks-text">No</p>



<h4 id="block-hGmAPO9XHs" class="wp-block-nectar-blocks-text nectar-blocks-text">[AN-41602]- Client-Side Payload Encryption for PaymentSubmission</h4>



<p id="block-fj1AybN5oL" class="wp-block-nectar-blocks-text nectar-blocks-text">Changes made in {{BaseURL}}/payment API to ensure that entire payload is encrypted on the client using a secure public key before being transmitted and decrypted only bybackend services.</p>



<p id="block-v3IKVwhMsh" class="wp-block-nectar-blocks-text nectar-blocks-text">NoFeatures Deployed to UAT ClientFacingImpact</p>



<p id="block-MTADB2OMUW" class="wp-block-nectar-blocks-text nectar-blocks-text">Launch darkly Flag “cryptography’ is created. If Flag is ON, then the payment API entire request payload will be encrypted to secure the requested details.</p>



<p id="block-NLFA2ycQd0" class="wp-block-nectar-blocks-text nectar-blocks-text">If flag is OFF, then the payment API request payload willbe shown as is as per existing.</p>



<p id="block-9Gt8de4PaM" class="wp-block-nectar-blocks-text nectar-blocks-text">This change is implemented on anytime portal as of now.</p>



<h4 id="block-XdYqJmwRZ0" class="wp-block-nectar-blocks-text nectar-blocks-text">[AN-46112] &#8211; Bug fixes on anytime portal payment method page.</h4>



<p id="block-oplwAOSoMU" class="wp-block-nectar-blocks-text nectar-blocks-text">Existing Behavior: The Inline error of Banking Type andAccount Type remains as is if user navigate from Card tabto ACH tab.</p>



<p id="block-MupEK0sUPL" class="wp-block-nectar-blocks-text nectar-blocks-text">Yes</p>



<p id="block-9MJ7tnSbi9" class="wp-block-nectar-blocks-text nectar-blocks-text">Fixed Behavior: No error will be displayed if user navigatefrom CARD tab to ACH Tab.</p>
<p>The post <a href="https://www.anddone.com/prod-release-angular-version-upgrade-an_angupd_v1/">PROD Release &#8211; Angular Version Upgrade (AN_ANGUPD_V1)</a> appeared first on <a href="https://www.anddone.com">AndDone</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>UAT Release &#8211; Angular Version Upgrade (AN_ANGUPD_V1)</title>
		<link>https://www.anddone.com/uat-release-angular-version-upgrade-an_angupd_v1/</link>
		
		<dc:creator><![CDATA[Samuel Yang]]></dc:creator>
		<pubDate>Mon, 16 Feb 2026 09:00:00 +0000</pubDate>
				<category><![CDATA[AndDone.js & UI Components]]></category>
		<category><![CDATA[Embedded & Branded Payment Experiences]]></category>
		<category><![CDATA[Product Updates & Status]]></category>
		<category><![CDATA[Release Notes]]></category>
		<category><![CDATA[Angular]]></category>
		<category><![CDATA[Anytime Payments]]></category>
		<category><![CDATA[Bug Fix]]></category>
		<category><![CDATA[Encryption]]></category>
		<category><![CDATA[For Developers]]></category>
		<category><![CDATA[NPM]]></category>
		<category><![CDATA[UAT]]></category>
		<guid isPermaLink="false">https://www.anddone.com/uat-release-angular-version-upgrade-an_angupd_v1/</guid>

					<description><![CDATA[<p>Angular version upgrade (v15 to v20), NPM package consolidation, client-side payload encryption, and Anytime Portal bug fixes.</p>
<p>The post <a href="https://www.anddone.com/uat-release-angular-version-upgrade-an_angupd_v1/">UAT Release &#8211; Angular Version Upgrade (AN_ANGUPD_V1)</a> appeared first on <a href="https://www.anddone.com">AndDone</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>Overview</h2>
<ul>
<li><strong>Release date:</strong> 2026-02-16</li>
<li><strong>Release status:</strong> Deployed to UAT</li>
<li><strong>Version:</strong> AN_ANGUPD_V1</li>
</ul>
<h2>Highlights</h2>
<ul>
<li>[AN-38395] Anytime Payments Angular Upgrade &#8211; Upgraded from Angular v15 to v20.</li>
<li>[AN-30796] NPM Package for common code from UI &#8211; Centralized shared package for all Angular 19 MFEs; single source of truth for services, interceptors, components, pipes, constants, enums.</li>
<li>[AN-35616] Update NPM Package &#8211; Changes to support new common functionality for the consumer Angular application.</li>
<li>[AN-41602] Client-Side Payload Encryption for Payment Submission &#8211; Entire payment payload encrypted client-side via LaunchDarkly &#8216;cryptography&#8217; flag; implemented on Anytime Portal.</li>
<li>[AN-46112] Bug fixes on Anytime Portal payment method page &#8211; Inline error cleared when navigating from Card to ACH tab.</li>
</ul>
<h2>References</h2>
<ul>
<li>AN-38395</li>
<li>AN-30796</li>
<li>AN-35616</li>
<li>AN-41602</li>
<li>AN-46112</li>
</ul>
<p>The post <a href="https://www.anddone.com/uat-release-angular-version-upgrade-an_angupd_v1/">UAT Release &#8211; Angular Version Upgrade (AN_ANGUPD_V1)</a> appeared first on <a href="https://www.anddone.com">AndDone</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>AndDone R 2.05.02</title>
		<link>https://www.anddone.com/anddone-r-2-05-02/</link>
		
		<dc:creator><![CDATA[Kirsten D]]></dc:creator>
		<pubDate>Tue, 13 Dec 2022 09:00:00 +0000</pubDate>
				<category><![CDATA[AndDone.js & UI Components]]></category>
		<category><![CDATA[Embedded & Branded Payment Experiences]]></category>
		<category><![CDATA[Product Updates & Status]]></category>
		<category><![CDATA[Release Notes]]></category>
		<category><![CDATA[Agent Portal]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[For Developers]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[Swagger / OpenAPI]]></category>
		<guid isPermaLink="false">https://www.anddone.com/anddone-r-2-05-02/</guid>

					<description><![CDATA[<p>This page is to track all production releases, Please follow the below steps to accurately document all production releases.</p>
<p>The post <a href="https://www.anddone.com/anddone-r-2-05-02/">AndDone R 2.05.02</a> appeared first on <a href="https://www.anddone.com">AndDone</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>Overview</h2>
<ul>
<li><strong>Release date:</strong> December 13, 2022</li>
<li><strong>Version:</strong> 2.05.02</li>
<li><strong>Source pages:</strong> ANDDONE-ALL RELEASE NOTES.pdf pp. 14–14</li>
</ul>
<h2>Highlights</h2>
<ul>
<li>Generic UI Updates &#8212; Impact to all UI components (ANdDone.JS, AnytimePayments, Admin</li>
<li>PaymentLinks ~ New feature, New landing page https:/ink.anddonde.com</li>
<li>PCI Compliance API ~ New feature, MVP.</li>
<li>Add virtual Account ~ Admin only functionality to add merchant level virtual account and</li>
</ul>
<h2>Original release notes excerpt</h2>
<p>AndDone R 2.05.02<br />This page is to track all production releases, Please follow the below steps to accurately<br />document all production releases.<br />Date of Release : December 13th, 2022<br />Whats new Release Items:<br />1. Generic UI Updates &#8212; Impact to all UI components (ANdDone.JS, AnytimePayments, Admin<br />portal, Agent Portal)<br />2.PaymentLinks ~ New feature, New landing page https:/ink.anddonde.com<br />Allowed origins ~ impacts the All existing server to server calls, especially AndDond.JS<br />Create intent Api Call, needs origin to be passed as header value<br />4.PCI Compliance API ~ New feature, MVP.<br />5. Add virtual Account ~ Admin only functionality to add merchant level virtual account and<br />help total pay transactions<br />6 Swagger &#8211; For devdocs</p>
<hr>
<p><em>Source:</em> Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 14–14.</p>
<p>The post <a href="https://www.anddone.com/anddone-r-2-05-02/">AndDone R 2.05.02</a> appeared first on <a href="https://www.anddone.com">AndDone</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>AndDone 2.0.3: FastFollow</title>
		<link>https://www.anddone.com/anddone-2-0-3-fastfollow/</link>
		
		<dc:creator><![CDATA[Kirsten D]]></dc:creator>
		<pubDate>Wed, 14 Sep 2022 09:00:00 +0000</pubDate>
				<category><![CDATA[AndDone.js & UI Components]]></category>
		<category><![CDATA[Embedded & Branded Payment Experiences]]></category>
		<category><![CDATA[Product Updates & Status]]></category>
		<category><![CDATA[Release Notes]]></category>
		<category><![CDATA[Admin Portal]]></category>
		<category><![CDATA[Agent Portal]]></category>
		<category><![CDATA[Anytime Payments]]></category>
		<category><![CDATA[For Developers]]></category>
		<guid isPermaLink="false">https://www.anddone.com/anddone-2-0-3-fastfollow/</guid>

					<description><![CDATA[<p>Date : 14 September 2022</p>
<p>The post <a href="https://www.anddone.com/anddone-2-0-3-fastfollow/">AndDone 2.0.3: FastFollow</a> appeared first on <a href="https://www.anddone.com">AndDone</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>Overview</h2>
<ul>
<li><strong>Release date:</strong> September 14, 2022</li>
<li><strong>Version:</strong> 2.0.3</li>
<li><strong>Source pages:</strong> ANDDONE-ALL RELEASE NOTES.pdf pp. 5–5</li>
</ul>
<h2>Highlights</h2>
<ul>
<li>Payment authorization statement &gt; Anytime payments</li>
<li>Admin portal Updates</li>
<li>Applications Impacted (check/highlight all that apply)</li>
<li>Admin Portal Users &#8211; Yes</li>
<li>Merchants &#8211; Yes</li>
<li>AndDoneJs &#8211; Yes</li>
<li>Bug Fixes</li>
<li>2,Bugs identified during previous release 2.0.3</li>
</ul>
<h2>Original release notes excerpt</h2>
<p>AndDone 2.0.3: FastFollow<br />Date : 14 September 2022<br />What&#x27;s New:<br />1. Payment authorization statement &gt; Anytime payments<br />2, Payment authorization statement &gt; AndDoneJS payments<br />Allowed origins filtering using traditional approach<br />4. Admin portal Updates<br />5. Applications Impacted (check/highlight all that apply)<br />« Admin Portal Users &#8211; Yes<br />Agent Portal Users &#8211; Yes<br />«+ Merchants &#8211; Yes<br />Anytime payment &#8211; Yes<br />« AndDoneJs &#8211; Yes<br />6.Bug Fixes<br />«2,Bugs identified during previous release 2.0.3</p>
<hr>
<p><em>Source:</em> Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 5–5.</p>
<p>The post <a href="https://www.anddone.com/anddone-2-0-3-fastfollow/">AndDone 2.0.3: FastFollow</a> appeared first on <a href="https://www.anddone.com">AndDone</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>AndDone 2.0</title>
		<link>https://www.anddone.com/anddone-2-0/</link>
		
		<dc:creator><![CDATA[Kirsten D]]></dc:creator>
		<pubDate>Tue, 10 May 2022 09:00:00 +0000</pubDate>
				<category><![CDATA[AndDone.js & UI Components]]></category>
		<category><![CDATA[Embedded & Branded Payment Experiences]]></category>
		<category><![CDATA[Product Updates & Status]]></category>
		<category><![CDATA[Release Notes]]></category>
		<category><![CDATA[Admin Portal]]></category>
		<category><![CDATA[Agent Portal]]></category>
		<category><![CDATA[For Developers]]></category>
		<guid isPermaLink="false">https://www.anddone.com/anddone-2-0/</guid>

					<description><![CDATA[<p>This is intial release for the AndDone MVP, this release marks the basic transaction flow. Status - Released Date - May 10, 2022</p>
<p>The post <a href="https://www.anddone.com/anddone-2-0/">AndDone 2.0</a> appeared first on <a href="https://www.anddone.com">AndDone</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2>Overview</h2>
<ul>
<li><strong>Release date:</strong> May 10, 2022</li>
<li><strong>Release status:</strong> Released</li>
<li><strong>Version:</strong> 2.0</li>
<li><strong>Source pages:</strong> ANDDONE-ALL RELEASE NOTES.pdf pp. 4–4</li>
</ul>
<h2>Highlights</h2>
<ul>
<li>This allows transaction to be captures with andDone]js as embedded widget,</li>
<li>Default admin portal</li>
<li>Admin Portal Users &#8211; yes</li>
<li>Bug Fixes &#8211; No First release</li>
</ul>
<h2>Original release notes excerpt</h2>
<p>AndDone 2.0<br />This is intial release for the AndDone MVP, this release marks the basic transaction flow.<br />Status &#8211; Released<br />Date &#8211; May 10, 2022<br />What&#x27;s New<br />1. This allows transaction to be captures with andDone]js as embedded widget,<br />2. Default admin portal<br />s Application Users Impacted (check/highlight all that apply)<br />« Admin Portal Users &#8211; yes<br />Agent Portal Users &#8211; no<br />Merchants &#8211; yes<br />AndDone.JS<br />4.Bug Fixes &#8211; No First release<br />5 Security Updates &#8211; nope<br />a This release includes [minor or major] security improvements.</p>
<hr>
<p><em>Source:</em> Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 4–4.</p>
<p>The post <a href="https://www.anddone.com/anddone-2-0/">AndDone 2.0</a> appeared first on <a href="https://www.anddone.com">AndDone</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
