> ## Documentation Index
> Fetch the complete documentation index at: https://docs.amlok.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Stripe

> Processor - access route, data references, and integration requirements.

> [!NOTE]
>
> **Active (Beta).** This integration is available in beta. Coverage depends on market, product, and account permissions. [View integration status](https://docs.amlok.io/integrations/status.md).

| Property | Definition |
| - | - |
| Provider ID | PAY-02 |
| Integration status | Active (Beta) |
| Category | Payments and POS |
| Product type | Processor |
| Evidence reviewed | 2026-10-22 |

## Integration approach

Balance Transactions, Payments, Payouts, and dispute APIs; determine approved account-linking and read permissions.

## Access and approval

Confirm Connect/platform or Stripe Apps route; public app review ETA ND. Review source.

**Documentation availability:** Public API/docs.

*ND means the source catalog does not disclose an approval estimate.*

## Data refresh

**Provider update cadence:** On supported events; API reads for reconciliation.

Stripe emits webhooks when supported payment, refund, dispute, and payout events occur. API reads retrieve the corresponding resources; there is no single recurring refresh interval for all payment data.

Event delivery can be delayed, duplicated, or out of order. Settlement and funds availability follow the payment lifecycle, so an event does not imply funds have settled.

**AMLOK synchronization:** The enabled refresh mode and schedule are agreed for your connection. Provider timing describes upstream capability; allow for retrieval and processing before changes appear in AMLOK. See [data refresh and freshness](https://docs.amlok.io/integrations/data-refresh.md).

Provider references: [Stripe webhooks](https://docs.stripe.com/webhooks), [Stripe event types](https://docs.stripe.com/api/events/types).

## Data reference

Open a resource to review its field definitions. Available fields depend on the connected product, account permissions, and source data.

| Resource |
| - |
| [merchant\_account](https://docs.amlok.io/data-model/field-dictionary.md#merchant-account) |
| [payment](https://docs.amlok.io/data-model/field-dictionary.md#payment) |
| [processor\_transaction](https://docs.amlok.io/data-model/field-dictionary.md#processor-transaction) |
| [payout](https://docs.amlok.io/data-model/field-dictionary.md#payout) |
| [refund](https://docs.amlok.io/data-model/field-dictionary.md#refund) |
| [dispute](https://docs.amlok.io/data-model/field-dictionary.md#dispute) |

## Coverage conditions

| Property | Definition |
| - | - |
| Country / deployment conditions | Verify target country, product edition, tenant and deployment. |
| History | Available payment and charge history retained in the account; no fixed maximum number of months is published for charge retrieval. [Provider reference](https://docs.stripe.com/api/charges/list). |
| Refresh | On supported events; API reads for reconciliation. [Details](#data-refresh). |
| Commercial / use rights | Client permission and applicable commercial use rights required. |

## Documented field mappings

These mappings show how source fields relate to normalized AMLOK fields. Review the source conditions for each mapping.

| Mapping | Source field | AMLOK target |
| - | - | - |
| [M027](https://docs.amlok.io/data-model/field-mappings.md#m027) | `id` | `processor_transaction.source_transaction_id` |
| [M028](https://docs.amlok.io/data-model/field-mappings.md#m028) | `amount` | `processor_transaction.gross.amount` |
| [M029](https://docs.amlok.io/data-model/field-mappings.md#m029) | `fee` | `processor_transaction.fee.amount` |
| [M030](https://docs.amlok.io/data-model/field-mappings.md#m030) | `net` | `processor_transaction.net.amount` |
| [M031](https://docs.amlok.io/data-model/field-mappings.md#m031) | `currency` | `processor_transaction.net.currency` |
| [M032](https://docs.amlok.io/data-model/field-mappings.md#m032) | `type` | `processor_transaction.event_type` |
| [M033](https://docs.amlok.io/data-model/field-mappings.md#m033) | `reporting_category` | `processor_transaction.reporting_category` |
| [M034](https://docs.amlok.io/data-model/field-mappings.md#m034) | `status` | `processor_transaction.availability_status` |
| [M035](https://docs.amlok.io/data-model/field-mappings.md#m035) | `available_on` | `processor_transaction.available_on` |
| [M036](https://docs.amlok.io/data-model/field-mappings.md#m036) | `created` | `processor_transaction.occurred_at` |
| [M037](https://docs.amlok.io/data-model/field-mappings.md#m037) | `source` | `processor_transaction.source_object_id` |

## Provider documentation

* [docs.stripe.com/api/balance\_transactions](https://docs.stripe.com/api/balance_transactions)
* [support.stripe.com/questions/how-do-i-submit-an-app-for-review-and-what-does-the-review-entail](https://support.stripe.com/questions/how-do-i-submit-an-app-for-review-and-what-does-the-review-entail)

## Related model reference

* [Provider coverage](https://docs.amlok.io/data-model/provider-coverage.md#pay-02)
* [Resource coverage](https://docs.amlok.io/data-model/resource-coverage.md#pay-02)
* [Field dictionary](https://docs.amlok.io/data-model/field-dictionary.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.