Who Talon.One is
Talon.One is a promotion and loyalty engine. The company behind it, Talon.One GmbH, was founded in 2015 and gives its address in Berlin, with teams in Berlin, London, Boston and Singapore. In April 2026 Adyen, the financial technology company listed in Amsterdam, announced an agreement to acquire it. Adyen reported the acquisition complete on 1 July 2026, and Talon.One has said its brand will evolve to sit alongside Adyen's. Your team builds campaigns in its Campaign Manager, where the Rule Builder joins conditions to effects. Your systems tell it what happened through its Integration API, and its Rule Engine answers with the effects of every rule that matched, such as points added or a tier reached.
Its loyalty programmes keep points in a ledger of their own, with tiers, subledgers (separate balances inside one programme), a start date and an expiry date for the points, and a return policy for taking them back. The same engine runs coupons, referral codes and achievements, which count a customer's progress towards a target. Each customer's instance is kept in its own virtual private cloud on Google Cloud, in the location you choose, with St Ghislain in Belgium and London among them. Talon.One states that it is ISO 27001:2022 certified, GDPR compliant and holds a SOC 2 Type II attestation, and its documentation has a page for financial services, with cashback on card purchases as its first use case. It turns events into rewards by rules your team controls, which is why it is one of the loyalty and promotions connectors of our Rewards & referrals module.
What it does in your platform
Rewards & referrals
Works out what each settled card payment earns: points, a cashback amount or a step up a tier, by the campaigns your team builds in Talon.One's Campaign Manager. The platform decides which payments count and sends them from its server, then books the result: points in Talon.One's own loyalty ledger, or cashback as a credit in the Ledger module. A refund or a chargeback takes the reward back.
How the connection works
Nothing of Talon.One's runs in your apps. The platform's server calls Talon.One's Integration API with an API key that never leaves the server, and Talon.One's own documentation says its API should be called only from a backend. Each call returns the effects of the rules that matched, and the platform acts on them.
A customer joins the programme
In the app, a customer who has passed KYC joins your points programme. The platform checks that the programme is open for their country and product, then calls Talon.One's Join customer profile to loyalty program endpoint. If Talon.One has no profile for them yet, the same call creates one.
Talon.One knows them by a random ID
The profile's integration ID is the platform's random ID. Talon.One's own best practices say to avoid email addresses and phone numbers as profile IDs. The profile carries only the attributes your rules need, such as country and card product. Names, email addresses, card numbers, account numbers, balances and identity documents never go to it.
The customer pays by card
An authorisation alone earns nothing. When the payment settles, the platform's server sends it with Update customer session: a session whose ID is the payment's own reference, in the state closed, with the amount and the merchant category. Talon.One grants loyalty points only when a session is closed, and an Idempotency-Key header means a retried call is not counted twice.
The rules answer
Talon.One's Rule Engine checks the session against your campaigns and returns an array of effects in the same response. An addLoyaltyPoints effect carries the number of points, the programme, their start and expiry dates and a transaction ID. If the points lift the customer over a threshold, a changeLoyaltyTierLevel effect names the new tier.
The platform books it
If points live in Talon.One, its loyalty ledger is the balance, and the app shows the active, pending, spent and expired points the platform reads through Get customer's loyalty balances. If you pay cashback, the platform turns the effect's value into a credit to the customer's balance in the Ledger, from your marketing budget account, and stores Talon.One's transaction ID beside it. Either way the platform keeps its own record of every effect, because Talon.One keeps sessions and effects for 30 days by default.
A refund takes it back
When the payment is refunded or charged back, the platform sets the same session to cancelled. Talon.One answers with a rollbackAddedLoyaltyPoints effect, and the platform reverses the Ledger credit. By default Talon.One rolls back only points that are still pending. With Active points deduction switched on in the programme's return policy it takes back active points too, and with Negative balance the balance can go below zero when the points were already spent.
Next to other providers
Talon.One works from the platform's own records. The Card issuing module reports the payment, the Ledger says when it settled and holds every cashback credit, KYC / AML and Fraud & risk decide who may join and catch second accounts, and the Notifications module tells the customer what they earned. Talon.One's loyalty notifications can post tier upgrades and expiring points to the platform, which passes them on. The connector calls the Integration API from the platform's server, so it works the same whichever provider issues your cards. When points are turned into gift cards, Runa, the module's reward delivery connector, delivers them. Talon.One can also create referral codes tied to a customer's ID, next to the module's referral programme connectors, Referral Factory, GrowSurf and Friendbuy.
Talon.One is one of the module's loyalty and promotions connectors, next to Voucherify and Open Loyalty. Customer IDs, the record of every payment sent and every reward booked, the Ledger's entries, membership choices and the abuse checks live in the platform, so a move to one of the others swaps a connector and leaves your apps and your books as they are. Campaigns, rules, tiers and programme settings are built in Talon.One's Campaign Manager, and would be built again in the new tool. Points balances kept in Talon.One would be exported and loaded into the new one.
When Talon.One fits best
A strong fit when
- Your team wants to write and change earning rules, tiers and campaigns in a rule builder, with budgets per campaign and per customer, without a platform release.
- You want one engine for points, tiers, coupons, referral codes and achievements, such as a reward for a set amount of card spend in a month.
- You want to choose where the data sits, Belgium or London among eight Google Cloud locations, with your instance in its own virtual private cloud.
Also worth a look
- Voucherify or Open Loyalty, the module's other loyalty and promotions connectors, when your team already works in one of them.
- A loyalty engine your team already runs: its account becomes a connector too.
How we get you live
The contract
We help you get your Talon.One account and contract in place, and settle the deployment location and the data retention periods with Talon.One, which states custom retention plans in the contract. Talon.One became part of Adyen in July 2026. The connector uses Talon.One's own Integration API, as its documentation describes it today.
The data
We ask for a deployment in St Ghislain, Belgium, or in London, two of the eight Google Cloud locations Talon.One offers. Moving a deployment later changes its API address, so we settle it first. With your team we agree what a session carries, the amount, the merchant category, the country and the card product, and nothing more. In the Campaign Manager we set when points become active, when they expire and the return policy for refunds. Talon.One returns part of a session by cart item, so we also agree how partial refunds are sent.
The keys
An Integration API key belongs to one Application, is shown only once and has an expiry date. It goes into your platform's secrets and is rotated on a schedule. Talon.One can limit API calls and Campaign Manager sign-ins to the IP addresses you give it, and your team signs in to the Campaign Manager with two-factor authentication or single sign-on. Loyalty notifications reach the platform with a secret header we set, and a post without it is rejected.
A full test run
Talon.One has a sandbox environment beside the live one: sandbox Applications, loyalty programmes and customer profiles are kept apart from live ones. We run the whole case there with test customers, from joining to a settled payment, a tier upgrade and a refund, and try rule changes with dry requests, which Talon.One evaluates without storing them. The campaigns are then copied to the live Application before your first real customer.
