Storage Configuration
The storage configuration controls where TaprNext stores inbound PEPPOL message files and how valid messages are handled. Configure under Tapr Settings → Storage.
Storage options
Section titled “Storage options”| Mode | Credentials | Valid message | Invalid message |
|---|---|---|---|
| Default | Platform-managed bucket (new sites: eu-central-1, Frankfurt) | Attached / stored for Purchase Invoice processing | Rejected Message with file when available |
| S3 | Your access key, secret, bucket, region | Stored in your bucket and linked | Rejected Message + attachment when available |
| API | Callback URL + auth | Forwarded to your callback (minimal local store) | Rejected Message audit still created |
Default is right for most customers. S3 when you must own the object store. API when another system is the system of record for raw PEPPOL XML.
See also PEPPOL Overview.
S3 Configuration
Section titled “S3 Configuration”To use S3 storage, provide these credentials:
| Field | Description |
|---|---|
| AWS Access Key | Your IAM user’s access key |
| AWS Secret Key | Your IAM user’s secret key |
| AWS Region | e.g., eu-central-1 |
| S3 Bucket Name | Your bucket name |
| Endpoint URL | Leave blank for AWS; set for S3-compatible services |
| Presign Expiry | Download link expiration in seconds (default: 3600) |
| Max File Size | Maximum file size in MB (default: 10) |
Your IAM user requires these permissions: s3:GetObject, s3:PutObject, and s3:ListBucket.
TaprNext validates connectivity, bucket accessibility, and permissions when you save the configuration.
API Callback Configuration
Section titled “API Callback Configuration”When using API mode, configure your callback endpoint:
| Field | Description |
|---|---|
| API Callback URL | HTTPS endpoint to receive messages (required) |
| API Timeout | Request timeout in seconds (default: 30) |
The URL must use HTTPS. Private IP ranges, loopback addresses, and link-local addresses are blocked for security.
Authentication options include Bearer Token, API Key Header, or Basic Auth. You may add custom headers as JSON and optionally log a specific response field.
Plan Requirements
Section titled “Plan Requirements”| Plan | Available Options |
|---|---|
| Free & Starter | Default only |
| Growth & Enterprise | Default, S3, and API |