Stripe
The Stripe integration pulls transaction data, dispute events, and fraud signals into HomeBase for payment security monitoring, anomaly detection, and PCI DSS compliance evidence.
What's ingested
- Charges & payments, transaction volume, success/failure rates, unusual patterns.
- Disputes & chargebacks, dispute events, evidence submissions, outcomes.
- Radar fraud signals, Stripe Radar risk scores and block/review decisions.
- Webhook events, charge.failed, radar.early_fraud_warning.created, review.opened.
- API key usage, unusual API access patterns from your Stripe account.
Setup
1. Create a restricted Stripe API key
In your Stripe Dashboard, go to Developers → API keys → Create restricted key. Grant read-only access to:
| Name | Type | Required | Description |
|---|---|---|---|
| Charges | read | No | Transaction history and charge details. |
| Disputes | read | No | Dispute and chargeback data. |
| Radar | read | No | Fraud signals and review decisions. |
| Events | read | No | Webhook event history. |
2. Register the integration
bash
POST /v1/integrations
{
"type": "stripe",
"tenant_id": "ten_01hxyz",
"credentials": {
"restricted_key": "rk_live_xxxxxxxxxxxxxxxxxxxx"
},
"config": {
"ingest_charges": true,
"ingest_disputes": true,
"ingest_radar": true,
"anomaly_threshold": "medium"
}
}Note:The Stripe integration is also used by HLD Slate POS customers. Transaction data from Slate flows into HomeBase automatically, no separate setup required if you use HLD Slate.
Fraud alert thresholds
Configure how aggressively HomeBase raises alerts on suspicious transaction patterns:
| Name | Type | Required | Description |
|---|---|---|---|
| low | threshold | No | Alert only on confirmed fraud signals from Stripe Radar. |
| medium | threshold | No | Alert on Radar blocks and reviews. Recommended default. |
| high | threshold | No | Alert on elevated Radar scores and unusual volume spikes. |