Show the best card on your checkout

Two parts. (1) A one-line loader <script> you paste once, typically near the closing </body>. (2) A target <div data-kredit-widget> you drop wherever you want the widget to render on your checkout. The loader scans the DOM for the target div and mounts the widget inside it — so position is fully under your control.

Anywhere you drop a target <div data-kredit-widget>. Highest-impact placements are right above the Pay button, inside the order-summary sidebar, or below the payment-method selector. You can place multiple target divs if you want the widget in more than one spot — each becomes its own instance. Move the div, move the widget; nothing else to change.

Yes — add data-cart-total and data-currency attributes to the target div. The widget then calculates the exact AED cashback the customer earns on this order with each card. For single-page-app checkouts where the total changes without a page reload, call window.Kredit.update({ cartTotal: <value> }) after each cart change.

Each approved merchant gets a unique kr_ prefixed client key, which you pass as data-key on the loader script. The key identifies your store to Kredit's recommendation API, scopes the widget to your merchant category, and gives you partner attribution on any apply-throughs. Keys are revocable from your Kredit admin contact.

Yes — the snippet is framework-agnostic. Works on Shopify product/cart pages, WooCommerce (checkout template hooks), Magento, BigCommerce, and any custom checkout. Shopify Plus stores using Checkout Extensibility need our native Shopify app build (on our roadmap). We'll send platform-specific install instructions with your client key.

Only the merchant ID (encoded in your client key), the customer's anonymous browsing context, and any optional fields you set on the target div (e.g. cart total, category override). No PII, no card numbers, no email addresses. The widget never reads form fields on your checkout.

Cart abandonment in UAE ecommerce sits around 70%. A large chunk of that is wallet hesitation — the customer suspects their card isn't the best one for this purchase and pauses to research. Showing the optimal card inline removes that hesitation and recovers the sale before the customer leaves the page.

For the typical UAE setup — where your card form is hosted by your payment provider (Network International, Telr, Checkout.com, Stripe, Adyen) inside their own iframe — no. Our widget renders alongside that iframe but never reads it, so your PCI scope is unchanged. If you collect card data directly on your own page (rare in the UAE), our widget being on the same page technically moves you from SAQ A to SAQ A-EP, the same as any third-party script on a card-collecting page. We render inside Shadow DOM and never read form fields, but the SAQ classification is determined by browser context, not by widget behaviour.

Yes — at any time. Delete the loader <script> tag and the target <div data-kredit-widget> from your template, redeploy, and the widget is gone. Nothing is left behind on the customer's browser or in your store's data. We never write to your database, never inject into your DOM outside of the target div, and never persist anything across sessions other than a first-party analytics cookie on the Kredit domain.

No — Kredit is not a payment processor. Your Stripe, Telr, Network International, N-Genius, or Checkout.com setup stays exactly the same. Kredit only shows the customer which of their existing credit cards earns the most cashback at your store. Payment still runs through your gateway, your acquirer, your MDR. We sit one step earlier in the funnel: the wallet-choice moment.