Skip to content

Kraken Embed Integration for Apps Whose Clients Trade Through Payward Services

Payward Services, launched as Kraken Embed, runs quotes, execution and custody behind your app. Protofire builds the parts left to your firm, from client mapping to the match of UTC-day settlement reports. In 2021 The Graph Foundation funded Protofire for subgraph development and support in its second grant wave.

Luis Medeiros

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. Where books break
  3. Provider of record
  4. Payward facts
  5. What you get
  6. Why Protofire
  7. How the project runs
  8. How work starts
  9. Not the right fit
  10. Related guides and services
  11. FAQ

Work shipped for 60+ networks and 95+ protocols, including

  • Chainlink
  • Ethereum
  • Solana
  • Safe
  • Ripple
  • Aave

Payward Services executes the trade, and your systems record it

Payward Services executes your clients' trades and holds their crypto. Kraken launched the product as Kraken Embed on 30 April 2025 (Kraken). Payward, Kraken's parent company, has sold it as Payward Services since 11 March 2026 (Payward). A Kraken Embed integration connects the service to your app and your core. Protofire builds the side your firm owns: the gateway, the event intake and the match with your books.

For example, a quote execution times out. Your gateway sends the execute call. No response arrives. Payward's retry rules use an idempotency key only where an endpoint takes one (Payward). In November 2026, the API reference listed no such key for creating or executing a quote. A gateway that answers the timeout with a fresh quote can place two trades for a single tap.

Who runs what in a client trade on Payward Services

Payward Services executes the trade and holds the assets. Protofire's services connect Payward to your app and your books.

The bank or fintech

App and client records

The app shows order screens, stores each client's external reference and opens trading after onboarding.

Core banking

The core books the cash leg and each client's crypto position and closes the day in local time.
Payward Services (Kraken)

Accounts and identity checks

Payward creates users and accounts, runs hosted or firm-submitted verification and makes the eligibility decision.

Quotes, execution and custody

Payward prices and executes each quote and holds the assets in custody.
Protofire builds

Order and onboarding gateway

The gateway signs calls with your key, reads a quote by its ID after a timeout and sends no automatic deposit retry.

Event intake, postings and daily match

The intake drops repeated webhooks, the posting service books Portfolio records, and a job matches UTC-day reports to your close.

Where the books break in a Kraken Embed integration

Four documented Payward behaviors decide whether your core matches Payward's records at the close.

Webhooks that repeat and only notify

Payward's setup guide says deliveries can be repeated and tells the receiver to deduplicate them by the svix-id header (Payward). Payward's documentation also asks firms to treat each webhook as a notification and to reconcile through Portfolio Transactions, canceled withdrawals included. Protofire's receiver checks each signature, drops a repeated svix-id and reads Portfolio before your core posts the entry.

Portfolio as the record of status and history

Payward calls Portfolio "the canonical status and history surface" (Payward). A negative deposit amount "can represent a deposit reversal". Payward's guide says to keep the sign. A returned or failed deposit includes a reason such as account_details_mismatch, limit_exceeded or duplicate. Protofire's posting service books from Portfolio and matches each deposit event's transaction_id to the reference.id of its Portfolio entry.

Deposit calls that must not be retried

"Create deposit is not idempotent. Do not automatically retry after a timeout or an ambiguous error," says Payward's deposits and withdrawals guide. Address claims are not idempotent either. Withdrawals take an idempotency key, and Payward asks for a Portfolio check before a retry after an unknown outcome. Protofire's connector sends no automatic retry of a deposit or an address claim and reuses the original key and body for a withdrawal.

Settlement reports cut at midnight UTC

Payward's settlement reports follow UTC days. Each report is a file with a type, such as swaps, and a date that spans "00:00:00 UTC to 23:59:59 UTC" (Payward). So a business day that closes at midnight in Frankfurt spans two report dates. Payward generates the reports from production data only (Payward), so your team and Protofire test the report match in production. Protofire's match job pulls the reports of both dates for your business day and lists each difference against your core.

Kraken's EU entity provides the crypto service to your clients

In bunq's setup, Kraken's EU entity provides the crypto trading, and the bank's app gives clients access to it.On its crypto page, bunq says "Crypto trading is provided by Payward Europe Solutions Limited t/a Kraken, authorised by the Central Bank of Ireland" (bunq). ESMA's interim MiCA register lists Payward Europe Solutions Limited as authorized by the Central Bank of Ireland on 25 June 2025 (ESMA register). The authorization covers eight crypto-asset services, among them custody, execution of orders and reception and transmission of orders. The register also lists cross-border services in 29 other EEA states.

Payward's case study of bunq says "Users accept the applicable terms during onboarding, while bunq securely transmits KYC information for verification" (Payward). The case study adds that "Each user is assigned an account". The bank "retains control of the user experience", while Payward Services operates the trading, custody and operational infrastructure. Your firm keeps the app and the brand. Kraken's EU entity serves the client.

ESMA's Q&A 2882 of 18 June 2026 sets out when introducing a client to a provider can count as advice under MiCA (ESMA). A plain reference to a provider, equally accessible to all potential investors and with no further indications, should not count as a recommendation. Your counsel decides how your app's screens and wording fit that line.

[...] introductory services consisting of the recommendation of a crypto-asset service to a potential investor (with or without recommending a specific crypto-asset service provider) [...] may be regarded as advice on crypto-assets for the purpose of MiCA, depending on the circumstances surrounding the recommendation.
European Securities and Markets Authority (ESMA), Q&A on MiCA · Question 2882, 18 June 2026

Payward Services facts your build depends on

API
REST, version 1, with separate sandbox and production hosts. Each authenticated request includes API-Key, API-Timestamp and an HMAC-SHA512 API-Sign, and Payward accepts timestamps within 15 seconds (Payward).
API keys
Keys are created in Payward Console, one Console per environment, with scopes such as query-funds and modify-trades, an optional expiry and an IP whitelist.
Quotes
A quote is valid for about 120 seconds. Its statuses are offered, executing, executed, expired and failed, and an execute call after expires_at returns 410 Gone (Payward).
Webhooks
Endpoints use HTTPS on a callback domain that Payward allowlists. Payward returns the signing secret once, when you create the webhook (Payward).
Settlement
At bunq, customer transactions are processed immediately, and "settlement takes place on a T+1 basis" (Payward).

Read on 16 November 2026 in Payward's developer documentation and in its case study of bunq.

What your firm gets from Protofire's Payward build

Protofire builds the client journey around Payward's API, from sign-up to withdrawal.

Trading opens when Payward's onboarding is complete

Your app opens trading only after Payward's onboarding is complete and reacts when requirements change. Onboarding is complete only when the state is ok and required_actions is empty. The verification.requirements_updated event "does not confirm approval" (Payward). Protofire maps each client ID to a stable external_reference, a Payward user_id and an account_id, and builds the gate on that map.

One trade for each client order after a timeout

A client who taps Buy once should get one trade, even when Payward's response does not reach your gateway. Protofire's gateway reads the quote by its quote_id before it creates another, and it requests a new quote after a 410.

Your own fee on each quote

Your pricing rules set the fee. Payward's quote takes a fee in basis points, a flat amount in the quote currency, or both combined (Payward). Without a value, the fee defaults to zero. Protofire's gateway applies your fee table to each quote and books the fee on its own ledger line.

Travel Rule requests answered inside your app

Clients answer Payward's Travel Rule requests in your app. Payward can answer a withdrawal with a 409 withdrawal_verification_required and ask for a self-attestation, a satoshi test or a digital signature. Protofire builds the step that collects the client's self-attestation and sends it to Payward.

Our record: indexing event data for The Graph

The Graph Foundation's second grant wave in July 2021 funded Protofire for subgraph development and support (The Graph).A subgraph turns onchain events into records a product can query, and a Payward build turns webhook notifications into postings checked against Portfolio. Protofire's subgraph work for The Graph has its own case study.

How a Payward Services project runs with Protofire

  1. Step 1

    Your Payward program and core details

    You send your Payward program setup, the core or back office that books client positions, and your daily cut-off time. Protofire answers with a written proposal within one business day.
  2. Step 2

    One test client through Payward's sandbox

    A Protofire engineer takes one test client through the sandbox, from create user and onboarding to a quote and its Portfolio entry. The run shows which client IDs, events and postings your core needs mapped.
  3. Step 3

    Production checks with small real amounts

    Payward keeps the sandbox and production fully separate. Production starts once Payward enables access (Payward). So your firm sets up keys, webhooks and funding addresses again for production. Your staff then run fiat deposits and trades with small real amounts. Protofire checks the first settlement reports and each Portfolio record against your core.
  4. Step 4

    Code and runbooks your team owns

    The code belongs to your firm. So do the runbooks for the gateway, the event services and the match job. After launch, your team runs them, or Protofire runs them through its managed onchain operations service.

How work with Protofire starts

Your staff create the Payward Console API keys and keep each secret, which Payward Console shows only once.Protofire's services sign calls with those keys from inside your systems. Where Protofire operates a service under a written scope, that scope lists each call the service may make.

Proposal
In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
Price
Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
Ownership
Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
After launch
Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
Access
Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
Licenses
Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.

How we work shows a worked proposal.

Requests a Payward Services build does not cover

Four kinds of request need a different build or a different provider.

  • Your firm wants to be the provider of record. A bank that wants a provider behind its own license can compare white-label providers in Protofire's crypto-as-a-service guide. The custody platforms guide compares the platforms a bank runs itself.
  • You need only a hosted on-ramp checkout. Payward's hosted Ramp runs the payment, the identity check and the crypto delivery. The work left is a few Ramp API calls, a redirect and status updates.
  • Clients keep their own keys. A self-custody wallet is a separate wallet build from a custodial service such as Payward's.
  • You trade your firm's own treasury on Kraken's exchange. That uses Kraken's exchange API with its own API keys, a different product from Payward Services.

Protofire holds no license and does not act as broker, custodian or provider of record. After launch, Protofire holds no Payward Console key that can place a trade or move funds.

FAQ

What is a Kraken Embed integration?
A Kraken Embed integration connects a bank's or fintech's app and core to Payward Services, the B2B product Kraken launched as Kraken Embed. The integration maps clients to Payward accounts and handles each quote after a timeout. It also takes in webhooks and books Portfolio records. Protofire builds the firm's side, and Payward keeps execution and custody.
Who can build a Kraken Embed integration for a bank or fintech app?
Protofire, an engineering firm, builds the side of a Kraken Embed integration that Payward Services leaves to the firm. Protofire builds the client mapping, the onboarding gate and the order gateway. Protofire also builds the webhook intake, the postings from Portfolio and the daily match of settlement reports.
Can we use our own KYC provider with Payward Services?
In the EEA, a firm can submit its own checks through a private endpoint that Payward opens to approved integrations. Payward's documentation says this route "supports only countries in the European Economic Area (EEA)" and that "Payward makes the final eligibility decision" (Payward). Outside that route, clients go through Payward's hosted KYC. Payward asks the firm to keep "the evidence and verifier records you need in your own system". Protofire's compliance integration builds the hand-off from your KYC provider.
What happens to client accounts if we leave Payward Services later?
Payward assigns each client an account, and the client accepts the applicable terms during onboarding, as Payward's case study of bunq describes. A later change of provider therefore means moving every client account. Client consent and the transfer of client data belong in the cut-over plan.
Which assets can our clients trade through Payward Services?
Payward's case study of bunq cites 640+ assets on 130+ networks (Payward). Availability varies by jurisdiction, so your app reads the current list from Payward's assets endpoint, GET /v1/assets. An asset in the general catalog can still be unavailable for a particular account, country or action.

Get a proposal

Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.

Luis MedeirosField CTO, reads every request · LinkedIn

A demo or repository link also works.