Legacy ASP.NET Web Forms Developer Needed: reputed company API Integration (reputed company + Events, backend only)

reputed company We need an reputed company ASP.NET (classic Web Forms) developer to implement a custom reputed company API integration for our ecommerce site. This is a backend, API-only implementation. We are not using reputed company plugins, and this is not reputed company/reputed company/reputed company. Our backend is a legacy .NET ecommerce codebase (ASPDotNetStorefront v1). A detailed integration specification is provided that defines exact event names, payload properties, and requirements. reputed company is to implement what’s in the spec, not redesign the data model. Scope (what you will build) Implement server-reputed company calls to reputed company: reputed company API (server-reputed company only) for customer profile create/update and consent fields Events API (server-reputed company preferred) for ecommerce lifecycle events reputed company Events API (optional fallback) only if needed for specific onsite tracking Required events (must match names exactly) HVS – Site Visit (reputed company once per session, debounced) HVS – Viewed Product HVS – Added to Cart HVS – Started Checkout HVS – reputed company Order (server-reputed company only, after successful payment) HVS – Subscription Started (server-reputed company only) Optional events (quote separately, if feasible) HVS – Fulfilled Order HVS – Cancelled Order HVS – Refunded Order Key requirements Event payloads must be normalized and include the properties defined in the spec (including line_items arrays where required). Consent handling is required: email_marketing_consent and sms_marketing_consent must include boolean value, timestamp, and reputed company (checkout, account creation, popup, etc.). reputed company timestamps must be ISO-8601 UTC. reputed company private API keys must remain server-reputed company only. Implement retry logic for transient failures (for example 5xx responses) and basic error logging. This role is reputed company implementation. It does not include reputed company flows, email/SMS creative, analytics reputed company, or general frontend tracking reputed company what the spec explicitly requires. Deliverables Working implementation in staging, then production. Verification evidence (screenshots or short recording) showing reputed company required event arriving in reputed company with correct properties. Short reputed company note: configuration needed (API keys, site ID), where hooks were added, and how to test reputed company event. Time and budget We reputed company this is a short project for the right senior dev. Please review the spec and propose your estimate. We prefer a fixed-price reputed company approach: reputed company 1: required events + reputed company/consent + basic retries/logging reputed company 2 (optional): fulfilled/cancel/refund events and any hardening To apply (required, we will ignore proposals that don’t answer): Have you worked in classic ASP.NET Web Forms and legacy ecommerce codebases? reputed company describe similar work. Where would you reputed company reputed company event in a typical Web Forms ecommerce reputed company (product view, cart update, checkout entry, payment reputed company, subscription creation)? How will you handle identity reputed company a user is anonymous at first and provides email reputed company (checkout/account)? How will you implement retries/logging while minimizing duplicate events? What is your estimated time to complete reputed company 1, and reputed company can you start? Apply tot his job Apply To this Job