Webhook

EinvoiceRegistrationIdentificationMismatch Webhook

​

Webhook endpoint for receiving E-invoice registration identification mismatch events.

Markets: Finland

This event is triggered when a recipient tries to register for E-invoices, but the provided second identifier does not match the one stored with Billogram. When this event happens, the recipient themselves get no feedback from the banks. The action is also blocked, meaning no action is taken by the Billogram system other than sending the callback.

For the Finnish market, the second identifier is the personal identity code.

The two-factor verification exists to prevent incorrect registrations.

Body·
required
application/json
  • callback_id
    Type: string
    required

    Unique identifier generated for each callback.

  • callback_timestamp
    Type: stringFormat: date-time
    required

    An ISO 8601 compliant timestamp for the callback.

  • callback_type
    const:  
    EinvoiceRegistrationIdentificationMismatch
    required

    The type of callback. Value is "EinvoiceRegistrationIdentificationMismatch" for an e-invoice registration identification mismatch callback.

  • recipient_information
    Type: object ·
    required
Responses
  • application/json
Request Example for postEinvoiceRegistrationIdentificationMismatch
{
  "callback_id": "9ec1c43a-0272-46f0-b4c2-9fe53acdb861",
  "callback_timestamp": "2021-11-03T13:28:51.706784Z",
  "callback_type": "EinvoiceRegistrationIdentificationMismatch",
  "recipient_information": {
    "customer_number": "1234",
    "operation": "ADD",
    "existing_personal_identification_number": "DDMMYYCZZZQ",
    "new_personal_identification_number": "123"
  }
}

{
  "status": "OK"
}

Webhook received successfully.

Required: Your endpoint must return HTTP 200 OK for the webhook to be considered successfully delivered. Any other status code will cause the webhook to be marked as failed and retried.