---
title: "ABAP Extension via abapGit for Administrators - Payhawk Help Center"
slug: "installing-the-payhawk-abap-extension-via-abapgit-sap-s-4hana-private-cloud"
description: "Install the Payhawk ABAP Extension on SAP S/4HANA Private Cloud with abapGit, online or offline, then pull, assign to a transport, and activate the objects."
updated: 2026-06-10T13:07:02Z
published: 2026-06-10T13:07:02Z
canonical: "payhawk.com/installing-the-payhawk-abap-extension-via-abapgit-sap-s-4hana-private-cloud"
---

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

# Installing the Payhawk ABAP Extension via abapGit (SAP S/4HANA Private Cloud)

This article explains how to install the **Payhawk ABAP Extension** into your SAP S/4HANA® Private Cloud system.

Because Private Cloud environments allow traditional ABAP transaction access, the installation uses abapGit, the industry-standard open-source Git client for ABAP, to pull code directly into your environment. This gives you a clean, traceable, and modern installation.

## Prerequisites

Before you start the installation, make sure you have addressed the following requirements:

- **System access**: developer access to your S/4HANA Private Cloud development system (client `000` or your main configuration client, depending on your transport strategy).
- **abapGit setup**: the abapGit tool must be available in your system. It is typically run through a standalone report (for example, `ZABAPGIT_STANDALONE`) or a custom transaction code (for example, `/nZABAPGIT`).
- **Network and SSL configuration**:
  - For the online method, your SAP system must have outbound internet access to the Git repository, and the appropriate SSL certificates must be uploaded in transaction `STRUST`.
  - If your system is completely firewalled, use the offline method (ZIP upload).
- **Extension details**:
  - Target package: `ZPAYHAWK` (or a sub-package as directed by Payhawk).
  - Git repository URL or ZIP file: provided by Payhawk support.
  - Personal access token (PAT): provided by Payhawk support (for the online method).

## Step-by-step installation guide

### Step 1: Launch abapGit

1. Log in to SAP GUI for your S/4HANA Private Cloud development system.
2. Go to transaction `SE38`, enter the name of your local abapGit program (usually `ZABAPGIT_STANDALONE`), and press **Execute** (`F8`). Alternatively, if your basis team has mapped it, run transaction `/nZABAPGIT`.

### Step 2: Establish the repository

Depending on your network infrastructure, choose Method A (online) or Method B (offline).

#### Method A: Online repository (recommended)

1. In the top menu of the abapGit dashboard, click **New Online**.
2. Enter the Git repository URL provided by Payhawk.
3. In the **Target Package** field, enter `ZPAYHAWK`. If the package does not yet exist, click the option to create a new package, assign it to a valid transport layer, and save it.
4. Click **Create Online Repo**.

#### Method B: Offline repository (for firewalled environments)

1. Download the Payhawk source extension `.zip` file provided by Payhawk to your local computer.
2. In the top menu of the abapGit dashboard, click **New Offline**.
3. Provide a repository name (for example, `Payhawk_Extension`) and enter the target package `ZPAYHAWK`.
4. Click **Create Offline Repo**.
5. Once created, click **Import ZIP** from the repository options and upload the downloaded Payhawk `.zip` file.

### Step 3: Maintain authentication (online only)

With the online option, abapGit prompts you for credentials when it communicates with the Payhawk remote repository.

1. When prompted by the system, enter the Git username provided to you.
2. Paste the fine-grained personal access token in the password/token field.

> [!WARNING]
> This token provides explicit read-only access to the Payhawk extension repository. Handle it with standard corporate credential safeguards.

### Step 4: Review and pull the code objects

Once the repository link is created, abapGit displays a clear **Diff** matrix showing the incoming Payhawk objects (classes, tables, data elements, and so on) compared to your empty local package.

1. Click the **Pull** button on the repository action bar.
2. abapGit deserializes the Git files and instantiates the ABAP objects inside the `ZPAYHAWK` package.
3. Assign the incoming objects to a transport request when prompted, so they can be migrated through your landscape (Test, Quality, Production) later.

### Step 5: Object activation

After the pull finishes, the objects must be activated within your NetWeaver stack.

1. abapGit typically triggers a mass activation automatically. If any objects remain inactive, open ABAP Development Tools (ADT) in Eclipse, or transaction `SE80`.
2. Locate the `ZPAYHAWK` package.
3. Right-click the package and select **Activate**. Ensure all components change state from `Inactive` to `Active`.

### Step 6: Transporting to QA and production (non-development systems)

Run the abapGit steps 1–5 only in your Development system. Quality Assurance (QA) and Production systems are set to **Not Modifiable** to enforce environment stability, so direct Git pulls are blocked there.

To safely deploy the Payhawk extension across your landscape, use the standard SAP Change and Transport System (CTS):

1. **Release the transport**: in your Development system, open the Transport Organizer (transaction `SE09` or `SE10`). Locate the Workbench transport request created in Step 4, right-click the tasks, and release them, then release the main transport request container.
2. **Import to QA**: log in to your Quality Assurance system. Use transaction `STMS` (or your organization's deployment tool, such as SAP ChaRM) to find the released transport request in the import queue, then trigger the import.
3. **Import to production**: perform your standard business and regression testing in the QA environment. Once approved, use `STMS` to import the same transport request into your Production system.

This lifecycle keeps your business-critical environments secure, isolated from internet repositories, and structurally identical to what was verified during QA testing.

## Troubleshooting

- **SSL handshake failed (**`STRUST`**)**: the SAP system does not trust the GitHub/GitLab root certificate authority. Download the root certificate from the Git URL through your web browser, and upload it to the `SSL client (Anonymous)` and `SSL client (Standard)` identities in transaction `STRUST`.
- **Missing prerequisites**: if certain core elements fail to activate, verify that your S/4HANA Private Cloud version meets the minimum baseline architecture specified in your Payhawk contractual documentation.