Implementation models

Two paths. Same result.

Already have a promotions engine? Payloot works either way. Pick your situation and we'll show you what it looks like.

Path 1

Connect your engine

You already run a robust corporate engine. Payloot connects through a REST API to orchestrate your promotions across every channel, without touching your existing rules.

  • Your rules stay in your engine.
  • Payloot takes them to web, app and point of sale.
  • Best if you already run an established corporate engine.
Compare both paths

Which one is yours?

Both paths give your customers the same result. What changes is where the rules live, who runs each calculation and what work comes first.

AspectConnect your enginePayloot as your engine
Where the rules liveIn your current engineIn the Payloot console
Who runs each calculationYour engine, orchestrated by PaylootThe Payloot cloud
InfrastructureYour engine has to handle every real-time requestProvided by Payloot; cost varies with your volume
CachingOptional, through professional services, to protect your engineNot needed
Upfront workMap the fields your engine needsSet up your promotions in Payloot
Promotion typesAll, except card BIN and installment-plan promotionsAll, except card BIN and installment-plan promotions
Messaging in catalog, product page, cart, checkout and orderYesYes
Single store, franchises and multi-brandYesYes
Best forCompanies with an established corporate engineCompanies without an engine, or ready to stop maintaining one
Why card BIN and installment-plan promotions are excluded

Interest-free installment plans, common in Mexico as meses sin intereses, are a payment method handled by your payment gateway. And for security, card BINs aren't used inside the platform.

What happens behind every cart.

The journey is the same on both paths. The only difference is who runs the calculation in step 3.

  1. Your customer adds products

    On the web, in the app or at the point of sale.

  2. The channel queries Payloot

    With the cart and customer data.

  3. Payloot evaluates the rules in effect

    The ones live right now, with no cached results.

  4. It returns the benefit and the message

    What your customer should see in the catalog, cart or at checkout.

  5. If the order changes, it recalculates

    Even after payment. See recalculation

  6. It records loyalty and referrals

    As independent transactions.

No stale results.

Payloot doesn't serve cached results. Every cart is evaluated against the rules in effect at that moment, so customers always see the real promotion.

If you connect your own engine, every request reaches it. If it isn't built for that volume, our team can design a caching layer to protect it, without compromising cart accuracy.

With cached results

You changed the promotion a while ago, but the cart still shows the old one until the next refresh.

With Payloot

The cart shows the promotion that's live now, because it's evaluated on the spot against today's rules.

What you need to get started.

What's worth having ready on each path before the first technical meeting.

Path 1

Connect your engine

  • Your engine's REST API, available.
  • A map of the fields your engine needs to respond.
  • Infrastructure that can handle real-time requests, or a caching layer.
Path 2

Payloot as your engine

  • Catalog and customers connected to Payloot.
  • Your promotions set up in the console.

See integrations and connectors

Not sure which path fits? Let's talk about your operation.

We'll look at how you sell today and which path makes sense for you.