> For the complete documentation index, see [llms.txt](https://docs.humblytics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.humblytics.com/how-to-track-purchase-events/other-providers.md).

# Other Payment Providers

If you're using a payment provider other than Stripe or Foxy, you can still capture revenue attribution with Humblytics. Trigger the purchase event after a successful payment using the snippet below:

```javascript
// Track revenue after successful payment (amount in cents)
window.Humblytics.trackRevenue(amountInCents, currencyCode);
```

Replace `amountInCents` with the payment amount (converted to cents) and `currencyCode` with the three-letter currency code (for example, `"USD"`). Run this code on the confirmation page or in the callback that fires when the payment is confirmed.

## Example Implementation

```jsx
"use client";

import { useEffect } from "react";

export default function Confirmation({ order }) {
  useEffect(() => {
    if (!order) return;

    const amountInCents = Math.round(order.total * 100);
    window.Humblytics.trackRevenue(amountInCents, order.currency);
  }, [order]);

  return (
    <div>
      <h1>Thanks for your purchase!</h1>
    </div>
  );
}
```

This approach works well for providers like Paddle, ReCharge, or any custom checkout where you control the post-payment experience. If you need hands-on guidance for a specific provider, contact **<support@humblytics.com>**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.humblytics.com/how-to-track-purchase-events/other-providers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.