# Forward payment-data

This endpoint enables platform merchants to leverage payment-data bundles in their acquirer integration.
The request is forwarded to the configured destination URL of your merchant settings.

Hellgate requires certain HTTP headers for this feature. These headers are reserved and cannot be used by the caller:

{% table %}

  - Header {% width="30%" %}
  - Required
  - Description

  ---

  - x-api-key
  - Yes
  - Authentication of the request.

  ---

  - x-hellgate-version 
  - No
  - Define the API version to use for the request.

  {% /table %}

Refer to the general documentation about forwarding senstive data for more information.

Endpoint: POST /payment-data/{id}/forward
Version: 2.0
Security: APIKeyAuth

## Path parameters:

  - `id` (string, required)
    The ID of the payment-data bundle

## Response 400 fields (application/json):

  - `code` (integer)
    The corresponding HTTP status code for the error

  - `classifier` (string)
    Technical code that helps to identify the error

  - `message` (string)
    Human readable representation of the error

## Response 401 fields (application/json):

  - `code` (integer)
    The corresponding HTTP status code for the error

  - `classifier` (string)
    Technical code that helps to identify the error

  - `message` (string)
    Human readable representation of the error

## Response 403 fields (application/json):

  - `code` (integer)
    The corresponding HTTP status code for the error

  - `classifier` (string)
    Technical code that helps to identify the error

  - `message` (string)
    Human readable representation of the error

## Response 407 fields (application/json):

  - `code` (integer)
    The corresponding HTTP status code for the error

  - `classifier` (string)
    Technical code that helps to identify the error

  - `message` (string)
    Human readable representation of the error

## Response 502 fields (application/json):

  - `code` (integer)
    The corresponding HTTP status code for the error

  - `classifier` (string)
    Technical code that helps to identify the error

  - `message` (string)
    Human readable representation of the error

## Response 503 fields (application/json):

  - `code` (integer)
    The corresponding HTTP status code for the error

  - `classifier` (string)
    Technical code that helps to identify the error

  - `message` (string)
    Human readable representation of the error

## Response 504 fields (application/json):

  - `code` (integer)
    The corresponding HTTP status code for the error

  - `classifier` (string)
    Technical code that helps to identify the error

  - `message` (string)
    Human readable representation of the error