Skip to main content
When a donor submits a transaction, the donation moves through a multi-step pipeline that handles conversion, settlement, and off-ramping. Understanding this helps you set the right expectations for your users.

​
The journey

1

Transaction confirmed

The donor submits an on-chain transaction referencing a config ID. Donate.gg detects the event and records the donation. The donor receives a confirmation that their donation has been received.
2

Donation processing

The donation funds are now in our system to be processed for delivery. They run through a pipeline that handles micro transaction pooling and stablecoin conversion. Once the donation is processed it is ready to delivered to its destination.
3

On-chain distribution

The processed donation is distributed on-chain to each beneficiary according to the weights defined in the config. The donor receives a second confirmation that their donation has been delivered.

​
What this means for your integration

  • Donations are not instant. There is a variable delay between a donor’s transaction and funds reaching the beneficiary, based on donation size or volume. This is expected behavior, not an error.
  • Confirmations are sent at two points. Donors receive an email when their donation is received (step 1) and again when it is delivered on-chain (step 3).
  • Everything is on-chain and verifiable. Every step of the pipeline emits on-chain events, so the full donation history is transparent and auditable.