# 5.2. HTTP Response

### Server response

If the request registering a new payment link is successful, the server will respond with HTTP status `200` and information about the newly created payment link:

```json
{
    "status": "SUCCESS",
    "data": {
        "paymentLink": {
            "paymentId": "58b1c723-d99d-4fb3-a597-eaac08846a90",
            "url": "https://paywall.int.axepta.pl/pay/58b1c723-d99d-4fb3-a597-eaac08846a90"
        }
    }
}
```

The response contains the `status` object indicating the success of the operation, and `data.paymentLink` with the following content:

| Parameter   | Type    | Description |
|------------|---------|-------------|
| `paymentId` | string | Payment identifier in UUID v4 format. Unique for each order. |
| `url`      | string  | Payment link URL. |

### HTTP statuses

| HTTP Code | Meaning |
|----------|---------|
| `200`    | Request completed successfully. Transaction created |
| `400`    | Bad request, invalid request payload. |
| `401`    | Unauthorized access. Request for a resource that requires authentication. |
| `403`    | No permission to perform the request. |
| `404`    | Unknown resource. |
| `422`    | Payload is correct but does not contain the required parameters. |
| `500`    | Server error. |
| `503`    | System unavailable. |