AndDone

Production Release Note – Anytime Payments Enhancements

Kirsten D — Wed, 17 Jun 2026 09:00:00 +0000

Overview

Release date: June 17, 2026
Release status: Deployed to Production.
Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 154-155

Highlights

AN-32417 – [CR] Anytime Payment

References

AN-32417
AN_APENHN_V2

Original release notes excerpt

Production Release Note – Anytime Payments Enhancements
AN_APENHN_V2)
Production Release Date: June 17,2025,
Release Status: Deployed to Production.
This release contain the anytime payments enhancements phase II change requests and the
branding page has been refreshed using the latest design system components for improved
look and feel
Features Deployed to Production Client Facing Impact
AN-32417 – [CR] Anytime Payment
Setting Page Changes.
Change Details Yes
Subdomain URL addltion.
Error message correction as per
new toggle on admin anytime
feature.

Source: Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 154-155.

The post Production Release Note – Anytime Payments Enhancements appeared first on AndDone.

Production Release Notes – Technical Release (AN_TECHRL_V1)

Kirsten D — Wed, 17 Jun 2026 09:00:00 +0000

Overview

Release date: June 17, 2026
Release status: Deployed to PROD
Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 223-224

Highlights

EPIC: AN-24529: Generate Swagger using Swashbuckle
AN-24585: Integrate Swagger API Documentation Using Swashbuckle – Infrastructure
AN-24584: Integrate Swagger API Documentation Using Swashbuckle – Domain

References

AN-24529
AN-24584
AN-24585
AN_TECHRL_V1

Original release notes excerpt

Production Release Notes – Technical Release (AN_TECHRL_V1)
Release Date: June 17,2025
Release Status: Deployed to PROD
Technical Owner: Manoj Bedse
Overview: Technical Release (AN_TECHRL_V1)
This release involves the migration of the manual OpenAPI (Swagger) node js-based utility
using swaggers NPM package to a NET Core-based Swashbuckle integration using nuget
package Swashbuckle.AspNetCore. The transition enhances the API documentation process by
leveraging Swashbuckle's built-in capabilities within the NET ecosystem.
EPIC: AN-24529: Generate Swagger using Swashbuckle
User Stories in Scope for the EPIC
« AN-24585: Integrate Swagger API Documentation Using Swashbuckle – Infrastructure
AN-24584: Integrate Swagger API Documentation Using Swashbuckle – Domain

Source: Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 223-224.

The post Production Release Notes – Technical Release (AN_TECHRL_V1) appeared first on AndDone.

Production Release Note – Anytime Payment Enhancement (AN_APENHN_V1)

Kirsten D — Wed, 17 Jun 2026 09:00:00 +0000

Overview

Release date: June 17, 2026
Release status: Deployed to Production,
Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 151-153

Highlights

AN-27269- AnyTime Payments Yes

References

AN-27269
AN_APENHN_V1

Original release notes excerpt

Production Release Note – Anytime Payment Enhancement (AN_APENHN_V1)
Production Release Date: June 17,2025
Release Status: Deployed to Production,
This release contain the anytime payments enhancements which includes the remove billing
address feature , subdomain related changes and miscellaneous items (Admin portal Revamp ~
General updates 3 CSS updates & Others, Dynamic Customer Form Behavior Based on
additionalDetallsPreference for "ManualEnter)
Features Deployed to Production Client Facing Impact
AN-27269- AnyTime Payments Yes
V2.0 : Billing Address Optional &
Subdomain Changes
Change Details
Remove Billing Address
Changes on Admin Anytime
gcativm @ News Amutinnm Gattine

Source: Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 151-153.

The post Production Release Note – Anytime Payment Enhancement (AN_APENHN_V1) appeared first on AndDone.

UAT Release Notes – Invoicing CR to support collection mode at Payment

Kirsten D — Wed, 22 Apr 2026 09:00:00 +0000

Overview

Release date: April 22, 2026
Release status: Deployed to UAT
Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 317-317

Highlights

Method level (AN_FEEINV_V3)
method level (AN-26245)

References

AN-26245
AN_FEEINV_V3
AN_FEEIN_V3

Original Release Notes Excerpt

UAT Release Notes – Invoicing CR to support collection mode at Payment Method level (AN_FEEINV_V3)

UAT Release: Invoicing CR to support collection made at Payment Method level (AN_FEEIN.V3)

Release Date: UAT Apr 22,2025

Release Status: Deployed to UAT

With this version of release, Invoicing will support collection mode at Payment method level This offers flexibility for the merchants opting in to Invoicing to be able to set collection mode as invoicing or net settled differently for different payment methods. Features Deployed to Production Client Facing ImpactInternal Invoicing [CR] – collection mode at payment YES method level (AN-26245)

Collection mode can be set at a payment method level for the merchants opting in fr Invoicing. This offers flexibility for those merchants to set the collection mode differently for each

Source: Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 317-317.

The post UAT Release Notes – Invoicing CR to support collection mode at Payment appeared first on AndDone.

UAT Release Notes – Ally Management (AN_ALMGMT_V4)

Kirsten D — Fri, 17 Apr 2026 09:00:00 +0000

Overview

Release date: April 17, 2026
Release status: Deployed to UAT
Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 291-291

References

AN-25194
AN_ALMGMT_V4

Original release notes excerpt

UAT Release Notes – Ally Management (AN_ALMGMT_V4)
UAT Release: Ally Management (AN.ALMGMT.V4)
Release Date: UAT APR 17,2025
Release Status: Deployed to UAT
With this version of release, Ally Payout APIS and webhooks will be delivered that are key for
Ales to be able to payout the required amounts to their sub-merchants
Features Deployed to Production Client Facing Impact
AndDone Aly Ver 1 Payouts (AN-25194) ves
Following capabilities are included into ths epic
Allys able to make payouts to thelr sub merchants using the
secure payouts api
Allis able to receive updates after subscribing to the
PAYOUT webhook module

Source: Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 291-291.

The post UAT Release Notes – Ally Management (AN_ALMGMT_V4) appeared first on AndDone.

UAT Release Notes – Ally Management (AN_ALMGMT_V3)

Kirsten D — Tue, 07 Apr 2026 09:00:00 +0000

Overview

Release date: April 07, 2026
Release status: Deployed to UAT
Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 288-290

Highlights

Alles can submit payments on behalf oftheir sub merchants

References

AN_ALMGMT_V3

Original release notes excerpt

UAT Release Notes – Ally Management (AN_ALMGMT_V3)
UAT Release: Ally Management (AN.ALMGMT.V3)
Release Date: UAT APR 07,2025
Release Status: Deployed to UAT
With this version of release, All the Ally changes required for IPFS Total pay migration will be
released to UAT enabling IPFS to perform an integration testing with AndDone environment.
Features Deployed to Production Client Facing Impact
AndDone Ally Ver1 Secure Payment APIs Changes (AN- YES
25193)
« Alles can submit payments on behalf oftheir sub merchants
For an Ally to submit @ payment, he would need an API key (
associated with Ally user) and a APP key (associated with
the sub-merchan)
This epic encompasses all the changes to be made tothe

Source: Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 288-290.

The post UAT Release Notes – Ally Management (AN_ALMGMT_V3) appeared first on AndDone.

AMS360 Enhanced Invoice Payments & Transaction Management

Kirsten D — Mon, 06 Apr 2026 13:47:44 +0000

Release Version: AN_AMS360_V3

Release Date: August 13, 2025

Status: Live

Overview

This release adds new ways to search, pay, and track AMS360 invoices directly through AndDone. Customers can now look up invoices by number, and merchants get better tools to filter and identify AMS360 transactions.

What’s New

1. Search Invoices by Invoice Number

What it does: Customers can now pay specific AMS360 invoices by entering the invoice number directly on the payment page.

How it works:

Customers choose between standard Anytime Payments or the new Invoice Lookup option
Enter a valid AMS360 invoice number to instantly pull up invoice details (customer info, amount due, dates)
If the invoice number is invalid, a helpful error message appears

Why it matters: Faster payments with fewer errors. Customers get exactly what they need without extra steps.

Customer-facing: Yes

2. Automatic Invoice Payment Limit Checks

What it does: The system now prevents customers from paying invoices that exceed your account’s payment limits for ACH or card transactions.

How it works:

AndDone automatically checks invoice totals against your configured limits
If an invoice exceeds the limit, customers see a clear message explaining why the payment can’t be processed that way

Why it matters: Keeps all payments within compliance and prevents failed transactions.

Customer-facing: Yes

3. Complete AMS360 Invoice Payments

What it does: Customers can now complete payments for validated AMS360 invoices with an automatic receipt.

How it works:

After invoice validation, customers only see payment methods that work for their invoice amount
Once payment is successful, a receipt is automatically generated

Why it matters: Streamlined checkout with built-in safeguards and instant confirmation.

Customer-facing: Yes

4. View AMS360 Transactions in Payment Listings

What it does: AMS360 payments are now clearly marked in your payment dashboard for easier tracking.

How it works:

AMS360 transactions show a Vertafore logo in the “Ref Value” column on the payment listing page
Payment detail pages display “AMS360” under “Initiated From”
Customer and merchant receipts still show “Anytime Payments” for consistency

Why it matters: Quickly identify where payments originated without changing the customer experience.

Customer-facing: Yes

5. Filter Payments by Source

What it does: Merchants can now filter payment listings by payment source: Anytime Payments, AndDone.js, or AMS360.

How it works:

New filter options appear based on your active Feature Access settings
Only see filters for features you’re currently using
Historical AMS360 transactions remain visible even if the feature is later disabled, but the filter option will be hidden

Why it matters: Better control and visibility into payment data. Easier to analyze transactions by source.

Customer-facing: Yes

The post AMS360 Enhanced Invoice Payments & Transaction Management appeared first on AndDone.

Outbound Payments – Enhanced Vendor Management & Check Controls

Kirsten D — Mon, 06 Apr 2026 13:47:44 +0000

Release Version: AN_OUTPAY_V7

Release Date: November 25, 2025

Status: Deployed to UAT

Overview

This release expands outbound payment capabilities in AndDone with improvements across vendor management, payment remittance, and check controls. The updates focus on giving insurance teams more flexibility, clearer validation, and better visibility when sending outbound payments.

What’s New

1. Optional DBA Field in Vendor Profiles

What it does:

The DBA (Doing Business As) field is now optional when creating or editing a vendor profile.

How it works:

Users can save vendor profiles without entering a DBA name.
Vendor creation continues even when a business operates under a single legal name.

Why it matters:

Speeds up vendor setup and removes unnecessary blockers during outbound payment preparation.

Customer-facing: Yes

2. Multiple Amount Fields in Payment Remittance

What it does:

Merchants can add multiple amount fields within payment remittance and choose which amount is applied to the check total.

How it works:

Multiple amount columns can be entered in the remittance table.
Users select the desired amount using the ¢ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬ÃƒÆ’Ã¢â‚¬¦Ãƒ¢Ã¢â€š¬Ã…â€œ$¢ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬ icon.
Only the selected amount is summed and reflected in Check Details.

Why it matters:

Supports more complex remittance scenarios while keeping check totals accurate.

Customer-facing: Yes

3. Validation for Check Amounts Over $1,000,000

What it does:

The system now blocks remittance submissions when the total check amount exceeds $1,000,000.

How it works:

During save or submit, the system evaluates the summed remittance total.
If the amount exceeds $1,000,000, an error message appears and the action is blocked.

Why it matters:

Prevents oversized check payments and reduces downstream processing issues.

Customer-facing: Yes

4. Bank Account Selection on Check Details Page

What it does:

Merchants can select which bank account is used before creating a check.

How it works:

A dropdown lists all merchant-linked bank accounts with check capability.
The default account appears at the top with a star indicator.
If no selection is made, the default account is used automatically.

Why it matters:

Gives teams more control over funding sources for outbound payments.

Customer-facing: Yes

5. Vendor Listing Pagination

What it does:

Vendor listings now support pagination instead of a fixed date filter.

How it works:

Pagination options include 10, 25, or 50 records per page.
The automatic ¢ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬ÃƒÆ’Ã¢â‚¬¦Ãƒ¢Ã¢â€š¬Ã…â€œLast 7 Days¢ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬ filter has been removed.
All available vendor records are visible by default.

Why it matters:

Improves navigation and visibility for teams managing larger vendor lists.

Customer-facing: Yes

Admin Portal Updates

Admin Notifications for Vendor Edits

What it does:

Administrators receive notifications when merchants create or update vendor records.

Why it matters:

Improves oversight and awareness of vendor changes across the platform.

Customer-facing: No

Payment Reference Visibility in Admin Portal

What it does:

Admins can view payment reference details for each outbound payment to help trace check transactions.

Why it matters:

Supports investigation and tracking of outbound payment activity.

Customer-facing: No

Key Takeaway

This release strengthens outbound payment workflows by improving vendor setup, remittance accuracy, and check-level controls. With clearer validation and expanded visibility, insurance teams gain more confidence and flexibility when managing outbound funds.

The post Outbound Payments – Enhanced Vendor Management & Check Controls appeared first on AndDone.

The CFO’s Compliance Checklist: Key Insurance Requirements and Where PCI Fits

Kirsten D — Fri, 03 Apr 2026 17:53:36 +0000

As a financial leader in Insurance, you are responsible for more than clean books. You are accountable for audit readiness, operational oversight, and choosing partners who protect your agency from compliance risk. PCI compliance goes beyond IT. It directly impacts how your payment data is handled, stored, and secured across every partner you rely on. This checklist helps you evaluate whether your payment partners, including platforms like AndDone, meet the standards your finance team needs to stay accurate, in control, and audit-ready.

1. Define PCI Scope and Ownership Across Systems and Vendors

PCI compliance for your insurance agency starts with clearly defining scope and ownership. Finance teams must understand every system, workflow, and vendor involved in accepting, processing, refunding, or adjusting card payments, especially when payment activity extends beyond internal systems.

Finance leaders should inventory every touchpoint where card data could appear, including:

Customer-facing payment portals and hosted checkout experiences.
Embedded payment links used in emails, invoices, or AMS workflows.
Internal systems that process, reconcile, refund, or adjust transactions.
Reprocessed or corrected payments handled outside the original workflow.
Third-party vendors involved in payment acceptance, processing, tokenization, refunds, chargebacks, or reporting.

Just as important as defining ownership, PCI compliance in insurance depends on documented internal accountability and clearly outlined third-party vendor compliance responsibilities. While technical controls may live with IT teams or vendors, finance remains responsible for oversight.

Finance leaders should document:

Who owns PCI oversight internally, including validation of scope, controls, and ongoing compliance.
Which vendors are responsible for PCI controls related to payment acceptance, processing, and tokenization.
How PCI evidence is collected, reviewed, and stored for audits.
Where escalation occurs when compliance questions or control gaps arise.

2. Verify How Card Data Is Handled and Stored

Understanding how card data is handled is essential for limiting compliance burden.

Key areas to review include:

Where card data is captured.
Whether tokenization occurs immediately.
Whether any system stores raw card data.
How long payment data is retained.
How data is removed or invalidated.

Platforms that rely on tokenization and limit data exposure help finance teams reduce audit scope while maintaining reporting visibility. Less exposure means fewer controls to manage and fewer questions to answer later.

Finance teams should confirm these controls are applied consistently across collections, refunds, and payment adjustments, not only initial transactions.

Look for platforms such as AndDone that tokenize payment data at capture and avoid storing raw card information to reduce audit scope and limit risk.

3. Restrict and Review Access to Payment

Access control is both compliance and financial security.

Finance teams should regularly review:

Who can view payment details.
Who can initiate refunds or adjustments.
Who can export transaction data.
How role changes are logged and approved.

Role-based permissions and access logs protect against internal risk and support clean audit trails in platforms like the AndDone Portal.

4. Validate Daily Reconciliation and Audit Trails

Reconciliation is where compliance becomes operational.

Strong payment workflows support:

Transaction-level detail.
Time-stamped audit logs.
Clear linkage between payments, refunds, and accounting entries.
Visibility into paid, pending, failed, and reversed transactions.

Manual reconciliation increases compliance risk. Finance teams benefit from systems that support daily reconciliation.

When payment records are tied to policies and customers with time-stamped logs, reconciliation becomes faster and more accurate.

5. Make Exceptions Easy to See and Prove

Refunds, chargebacks, and adjustments are part of every payment operation. But when they aren’t documented or visible, they become compliance risks.

Finance teams should ensure:

All exceptions are tracked with complete transaction history.
Refunds follow standardized and documented workflows.
Chargebacks remain visible in reporting.
Exceptions do not bypass approval or logging controls.

Auditors focus on the moments when processes break. That’s why visibility matters.

Exception workflows should stay connected to the original transaction and remain visible to the full team. This makes it easier to demonstrate control, even when workflows don’t follow the standard path.

6. Confirm Third-Party and Vendor PCI Compliance

Third-party vendors are part of your compliance footprint. As industry coverage regularly highlights, payment complexity in insurance often increases when responsibility for data handling and reporting is spread across multiple platforms and partners. Finance leaders should verify each vendor’s PCI status and document third-party service provider responsibilities across data handling, reporting, and audit support.

Key areas to confirm include:

Each vendor’s current PCI certification and scope.
Which party captures, processes, tokenizes, or stores card data.
How vendors support audits, including access to evidence and documentation.
Where responsibility shifts between internal teams and external partners.

When vendors manage payment data correctly, finance teams stay in control without taking on extra compliance work. The right platform provides visibility, reporting, and audit support without adding PCI scope to your internal systems.

¢ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬ÃƒÆ’Ã¢â‚¬¦Ãƒ¢Ã¢â€š¬Ã…â€œAt least I have the payment details, and I have no PCI compliance burdens.¢ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬

— Chase Courtney, Vice President of AndDone

The right partner keeps finance in control without adding technical PCI risk. In this short video, Chase Courtney from AndDone shares how their team helps reduce audit complexity by managing tokenization, routing, and reconciliation in one system.

7. Maintain PCI Evidence and Audit Readiness

Audit readiness depends on evidence that reflects how your business actually operates.

Finance teams should centralize:

PCI policies and procedures.
Access logs and activity records.
Transaction and reconciliation reports.
Vendor compliance documentation.

Evidence should remain current and aligned with live workflows, because faulty or outdated records can directly lead to compliance problems and audit obstacles. When documentation matches real operating conditions, audits move faster.

8. Schedule Ongoing PCI Reviews for the Year

PCI compliance in your insurance agency must remain current as systems, vendors, and workflows change.

Finance leaders should:

Align PCI reviews with monthly close cycles.
Reassess PCI scope whenever payment systems, vendors, or workflows change.
Review vendor compliance on a regular cadence.
Update documentation proactively as processes evolve.

Routine reviews prevent compliance drift and reduce last-minute remediation. Keeping PCI oversight tied to financial operations supports consistent audit readiness throughout the year.

Keeping reviews aligned with financial operations helps reduce compliance gaps. Systems like AndDone bring reporting, access controls, and vendor documentation together in one place.See how it works in practice by requesting a demo.

Frequently Asked Questions

AndDone clearly defines PCI scope, limits exposure with tokenization, and provides access controls and real-time reporting that simplify audits

PCI compliance affects how payment data is captured, stored, and reconciled. Audits require documented processes, access logs, and secure systems. Gaps in oversight increase audit risk.

While IT or operations manage technical controls, finance leaders own vendor accountability, reconciliation accuracy, and centralized audit evidence across internal teams and partners.

The post The CFO’s Compliance Checklist: Key Insurance Requirements and Where PCI Fits appeared first on AndDone.

UAT Release – GA Support to Premium Finance Lite (AN_GASPFL_V1)

anddone — Tue, 31 Mar 2026 09:00:00 +0000

Adds manual GA sync API for Premium Finance Lite

What’s new

A new API service is available in Premium Finance Lite that allows a manual sync to be triggered for updating IPFS GA (General Agent) data in the system for a specific merchant. This gives operators an on-demand alternative to waiting for the regularly scheduled cron job to run.

Why it matters

You can now trigger a GA sync programmatically at any time, making it easier to recover from data discrepancies or push updates immediately after a GA change in IPFS without waiting for the next scheduled run.

Adds manual GA sync button to the Admin Portal

What’s new

A new button has been added to the PF Lite feature page in the Admin Portal, allowing admins to trigger a manual GA sync directly from the UI at any time without waiting for the regular cron job.

Why it matters

Before this change, initiating a sync required either waiting for the scheduled job or triggering the API directly. Admins can now initiate a sync on demand from the portal without any technical intervention.

Introduces automated GA sync for Premium Finance Lite

What’s new

A new scheduled API service has been introduced that runs automatically at a configured time, retrieves all GAs from IPFS, and syncs them into the system for each relevant merchant. This replaces the need for manual intervention to keep GA data current on a routine basis.

Why it matters

GA data in the system now stays automatically up to date with IPFS on a scheduled basis, reducing the risk of stale GA records being used in quote creation and other downstream flows.

Adds GA search API by name

What’s new

A new API service allows callers to search for a General Agent by their unique name. This provides a targeted lookup mechanism for GA records without needing to retrieve the full list.

Why it matters

You can now look up a specific GA by name in a single API call, making it straightforward to integrate GA selection into quote creation flows or other workflows that require identifying a GA by name.

Integrates GA search into the quote creation UI

What’s new

A dropdown search field has been added to the quote creation flow in the UI, allowing users to find and select a General Agent to associate with a new quote. The field is powered by the GA search API and supports searching by GA name.

Why it matters

Before this change, there was no UI mechanism to associate a GA with a quote at creation time. Users can now search for and add a GA directly within the quote creation workflow without leaving the page.

Adds GA support to the Draft Quote JWT API

What’s new

The existing Draft Quote API has been updated to accept a GA object in the policy request body, enabling GA details to be included when creating a draft quote. The API for fetching quote details has also been updated to return the GA in the policy object.

Why it matters

Integrations that create draft quotes via the JWT API can now include GA information as part of the initial quote creation request, and retrieve it back when fetching quote details, without requiring a separate update step.

Changes

Parameter	Change Type	Resource / Endpoint
`ga` (in policy object)	Added	Draft Quote JWT API (Create)
`ga` (in policy object)	Added	Draft Quote JWT API (Get)

Maps GA object to quote creation UI fields

What’s new

The GA object returned from the API is now mapped to the corresponding UI text fields in the quote creation flow, enabling both adding and displaying a GA when creating or viewing a quote.

Why it matters

GA data entered or retrieved via the API is now consistently reflected in the quote creation UI, ensuring that what is stored in the system matches what the user sees and interacts with on screen.

Includes GA details in quote generation

What’s new

The existing quote creation flow has been updated to include GA details in the generated quote. When a GA is associated with a quote, that information is now carried through to the final quote output.

Why it matters

Before this change, GA information entered during quote creation was not reflected in the generated quote. GA details are now included end-to-end, from selection through to the final quote document.

Displays GA on saved policies in search results

What’s new

When a GA is added during quote creation, it is now mapped to the resulting policy and displayed when that policy is retrieved via the saved policy search. This ensures GA association is visible throughout the policy lifecycle, not just at quote time.

Why it matters

Before this change, a GA associated with a quote was not surfaced when searching saved policies, making it difficult to identify which GA was linked to a given policy. GA information is now consistently visible at both the quote and policy level.

UAT Release – GA Support to Premium Finance Lite (AN_GASPFL_V1)

Release Date: Mar 31, 2026

Release Status: Deployed to UAT

¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬¢ÃƒÆ’¢Ãƒ¢Ã¢â‚¬Å¡¬ÃƒÆ’¢Ãƒ¢Ã¢â€š¬Ã…¡¬

Create GA Manual Sync in Existing Premium Finance Lite [AN-46447]

An API service in premium finance lite to perform manual sync for updating IPFS GA in our system for a merchant.

Client Facing: No

Integrate Manual Sync API in Admin Portal [AN-46462]

UI to display a button on PF lite feature page to perform a manual sync at any time without waiting for regular Cron job.

Client Facing: Yes

Create Auto Sync for GA in Premium Finance Lite [AN-45696]

An API service which will execute on a given time and retrieve all GAs from IPFS and sync in our system for a specific merchant.

Client Facing: No

Create Get API for GA with Search by Name [AN-45749]

An API service which will be able to search a GA with its unique name.

Client Facing: No

Integrate Get GA Details to Fetch and Search GA [AN-46419]

UI to display a dropdown search option to find GA and add it in quote creation.

Client Facing: Yes

Add GA for Draft Quote in JWT API [AN-45768]

Update existing draft quote to support GA in the policy request for quote creation.

Client Facing: No

Return GA in the Draft JWT API [AN-46116]

Update existing API to fetch quote details for GA in policy object.

Client Facing: No

Integrate GA Object in Policy Details [AN-46394]

UI to map GA Object with UI text field for Add and get GA in quote creation.

Client Facing: Yes

Generate a Quote with GA Object [AN-46888]

Update existing quote creation to support GA details in the generated quote.

Client Facing: Yes

Search Saved Policies Should Show GA When Added [AN-47244]

The GA added while quote creation should be mapped to Policy and should be displayed when policy is searched.

Client Facing: Yes

The post UAT Release – GA Support to Premium Finance Lite (AN_GASPFL_V1) appeared first on AndDone.