​

Merchant Integration Guide

A merchant integration gives agents a safe way to recommend products and gives Rako enough evidence to attribute payable outcomes.

​

Integration checklist

1. Publish eligible offers — expose products, services, or campaigns that agents may recommend.
2. Accept AAP context — carry the signed offer and recommendation context into checkout or the relevant conversion flow.
3. Report outcomes — send payment, order, activation, or milestone status back to Rako.
4. Reconcile commission — let the conversion ledger calculate merchant commission, Rako network fee, and builder payout.

​

Checkout and conversion paths

Checkout and conversion are separate boundaries. A hosted checkout URL starts the buyer journey, but it does not prove that a payment happened, an order was accepted, or a commission is owed. For instant checkout products, conversion can be recorded when platform-side payment status is confirmed. For delayed-service verticals such as broadband, energy, insurance, or finance, the payable conversion may be a later milestone such as approval, activation, policy start, or first bill paid. Rako keeps attribution and the conversion ledger authoritative while checkout and payment status flow through the merchant’s payment processor or configured outcome-reporting path.

​

What not to include

Do not place API keys, webhook secrets, private payment-processor configuration, or environment-specific deployment URLs in docs or examples.