Send EHF Invoice
The Send EHF Invoice endpoint allows merchants to generate and send standardized electronic invoices (EHF) to corporate customers in Norway. EHF invoices conform to national and PEPPOL regulations, enabling seamless delivery to customer accounting systems and public sector entities. This API integrates Front Payment’s digital invoicing with your order workflow — encapsulating products, billing details, due dates, and delivery preferences into an EHF-enabled invoice.
Upon success, you'll receive an orderUuid
and customerUuid
to track the invoice lifecycle. To check invoice status go to Get Order Status By UUID
page
Key Benefits
- Automate invoicing workflows and reduce manual billing overhead.
- Ensure compliance with Norwegian EHF (PEPPOL) standards.
- Deliver invoices directly to recipients' systems via the PEPPOL network.
- Monitor invoice status or reconcile with callbacks or queries.
Prerequisites
Before you start the integration, make sure you have:
1. API Access:
- A valid API key and Bearer Token from Front Payment
- Access to the demo and production environments
2. Technical Requirements:
- Ability to make HTTPS API calls
- Secure storage of tokens and keys
- Callback endpoints to handle payment status updates
3. Test Environment:
- For testing, contact
[email protected]
to gain access to the demo environment
Endpoint
POST https://demo-api.frontpayment.no/api/v1/connect/orders/ehf/create
Authorization
Include a Bearer Token in the Authorization
header. You can obtain this token from Front Payment.
Example:
Authorization: Bearer YOUR_FRONTPAYMENT_BEARER_TOKEN
Request Payload
Send the following parameters as a JSON object in the request body:
{
"products": {
"0": {
"name": "Hair Wash",
"productId": "VFDDF",
"quantity": "1",
"rate": 51,
"discount": 0,
"tax": "0",
"amount": 51
}
},
"orderSummary": {
"subTotal": "51.00",
"totalTax": "0.00",
"totalDiscount": "0.00",
"grandTotal": "51.00"
},
"orderDate": "1703040812",
"customerDetails": {
"countryCode": "+47",
"msisdn": "46567468",
"email": "[email protected]",
"name": "Kari Nordmann",
"preferredLanguage": "en",
"organizationId": "123456789,
"address": {
"street": "Luramyrveien 65",
"zip": "4313",
"city": "Sandnes",
"country": "NO"
}
},
"invoiceInterval": 0,
"invoiceMaturity": 10,
"invoiceFeeApplicable": true,
"separateInvoices": true,
"referenceNo": null,
"customerReference": null,
"callback": {
"callbackUrl": "https://example.com/callback-url"
}
}
Validation Rules
Make sure your request meets the following requirements:
Field | Type | Description |
---|---|---|
products.*.name |
string |
Required Name of the product. |
products.*.productId |
string |
Optional Unique identifier for the product. |
products.*.quantity |
numeric |
Required Quantity of the product. |
products.*rate |
numeric |
Required Rate per unit of the product. |
products.*.discount |
numeric |
Optional Discount applied to the product. |
products.*.tax |
numeric |
Required Tax rate must be (e.g., 0 , 12 , 15 , 25 ), Unless you have other configuration. |
products.*.amount |
numeric |
Required Total amount for the product line item. |
orderSummary.subTotal |
numeric |
Required Subtotal of all products before tax and discount. |
orderSummary.totalTax |
numeric |
Required Total tax for the order. |
orderSummary.totalDiscount |
numeric |
Required Total discount for the order. |
orderSummary.grandTotal |
numeric |
Required Grand total of the order. |
orderDate |
string |
Required Unix timestamp for the Date of the order. |
customerDetails.countryCode |
string |
Required Country code for the customer's phone number (e.g., "+47"). |
customerDetails.msisdn |
string |
Required Mobile Subscriber ISDN Number (phone number). |
customerDetails.email |
email |
Required Customer's email address. |
customerDetails.name |
email |
Required Customer's full name. |
customerDetails.preferredLanguage |
string |
Optional Customer preferred language. Available languages are en , no , sv , da , de . If nothing is given it will set default to no . |
customerDetails.organizationId |
string |
Required Organization identification number, must contain only numbers and cannot contain spaces |
customerDetails.address.street |
string |
Required Street address of the customer. |
customerDetails.address.zip |
string |
Required Zip code of the customer's address. |
customerDetails.address.city |
string |
Required City of the customer's address. |
customerDetails.address.country |
string |
Required ISO Alpha-2 country code (e.g., NO ). Custom validation IsoAlpha2Country applies. |
invoiceInterval |
numeric |
Optional Default value is = 0 . You can change it to 0 , 1 , 2 . Daily = 0 , Once a month = 1 , Twice a month = 2 . |
invoiceFeeApplicable |
boolean |
Required Default value is true . |
invoiceMaturity |
numeric |
Optional Default value is 14 . if you want to set the value then give 14 , 30 or 45 . |
separateInvoices |
boolean |
Optional Default value is true . |
referenceNo |
string |
Nullable Any reference number. |
customerReference |
string |
Nullable Any value for customer reference. |
callback.callbackUrl |
url |
Required To receive real-time notifications on order state changes, you must provide a callback url. This is an server-to-server HTTP GET request. |
Response
A successful request will return a 201 Created
status with the following JSON payload:
{
"status_code": 201,
"status_message": "OK",
"message": "orderAddedSuccessfully",
"is_data": false,
"data": {
"uuid": "ODR3506777330",
"customerUuid": "CSRT3463048878"
}
}
API returns a 500
or 510
error, it means something failed on the server side
{
"status_code": 500,
"status_message": "Internal Dependency Error",
"message": "internalErrorOccurredPleaseTryAgainLater",
"is_error": true,
"errors": {
"happenedAt": "String",
"internalErrorDetails": "Array"
}
}
{
"status_code": 510,
"status_message": "Execution Exception Occurred",
"message": "somethingWentWrong",
"is_error": true,
"errors": "Array"
}
Notifications via Callback URL
The callbackUrl
is an endpoint on your server that our system will call via an HTTP GET
request whenever the status of the specified order changes from its initial state.
See the link below to understand how to work with the callback URL on your side and how to verify the request sent from our side.