---
title: Prerequisites
slug: extensions/prerequisites
docTags: 
createdAt: 2026-09-22T18:20:22.602Z
---

Before installing the cartridge, gather the following.

## Forter credentials

Get these from the Forter Portal. See [API Credentials](https://docs.forter.com/extensions/api-credentials) for where to find and set them.

| Credential | Used for                                                               |
| ---------- | ---------------------------------------------------------------------- |
| Site ID    | The validate API URL, HTTP headers, and the device-fingerprint snippet |
| Secret Key | HTTP Basic Authentication                                              |

## Mapping template setup

Forter's implementation team deploys a per-merchant mapping template to your account as part of onboarding. This is what lets Forter's backend interpret the raw order data the cartridge sends — see [How Order Data Is Built and Mapped](https://docs.forter.com/extensions/how-order-data-is-built-and-mapped) for how it's used. Confirm with your Forter implementation team that it's in place before testing.

## SFCC access

- **Business Manager admin** — for metadata import and job scheduling.
- **WebDAV or IDE access** — for cartridge upload.

See [Forter Cartridge Compatibility](https://docs.forter.com/extensions/forter-cartridge-compatibility) for platform requirements.

## Payment processor compatibility

Confirm your PSP cartridge doesn't suppress the `app.post.auth` or `app.validate.order` hooks. For PSP-specific requirements, see [Payment Processor Integration](https://docs.forter.com/extensions/psp-integration-guide).