Payment Logs

The Payment Logs page allows administrators to search payment webhook events, inspect processing results, and open detailed webhook log records.

This page is used for reviewing payment provider event history. It helps administrators check whether webhook events were received, processed successfully, failed during processing, or mapped to customer and billing records.

Overview

Payment Logs records payment-related events received from payment providers. These events may include payment capture events, recurring subscription updates, subscription creation events, failed processing records, and other webhook notifications.

The list page shows a summary of each event, and the detail page displays the raw webhook record, request headers, raw body, signature, process result, and normalized billing event data.

Search and Filter

Use the Search & Filter area to find specific payment events by keyword, provider, event type, processing status, and date range.

Filter	Description
Keyword	Searches by customer, event ID, delivery ID, subscription token, transaction token, or other supported keyword values.
Provider	Filters events by payment provider. Example: `AUTHNET`.
Event Type	Filters logs by event type, such as `invoice.paid`, `net.authorize.payment.authcapture.created`, or `net.authorize.customer.subscription.updated`.
Process Status	Filters logs by processing result, such as SUCCESS, FAILED, PROCESSED, or other internal statuses.
From	The start date of the payment event search range.
To	The end date of the payment event search range.
Search	Runs the search using the selected filters.

Payment Log List

The Payment Log List displays webhook and event history records. Each row represents one event received from a payment provider or processed by the billing system.

Column	Description
Date	The date and time when the event was received or recorded.
Provider	The payment provider that sent the event. Example: `AUTHNET`.
Event Type	The provider event type and event ID or delivery ID.
CustomerId	The mapped customer ID or token if the event was connected to a customer record.
Customer	The mapped customer name and email address. If not mapped, the value may show `unmap`.
Status	The processing status of the webhook event, such as PROCESSED or FAILED.
Message	A short processing result message or error message.
Action	Provides the Detail button to open the full webhook log record.

Common Event Types

Event Type	Meaning
net.authorize.payment.authcapture.created	An Authorize.Net payment capture event was received.
net.authorize.customer.subscription.created	An Authorize.Net recurring subscription was created.
net.authorize.customer.subscription.updated	An Authorize.Net recurring subscription was updated.
invoice.paid	A payment invoice was paid, depending on provider support.

Process Status

Status	Description
PROCESSED	The webhook event was received and processed successfully.
FAILED	The webhook event was received but failed during processing.
SUCCESS	The event process completed successfully, depending on internal status naming.

A failed log does not always mean the provider payment failed. It may mean iBoard failed to map, parse, save, or normalize the received webhook event.

Payment Log Detail

Click the Detail button to open the Payment Log Detail page. This page is used to inspect the original webhook request and the normalized billing event data.

Webhook Log Section

The Webhook Log section shows the raw event information received from the payment provider.

Field	Description
Log ID	The internal webhook log ID.
Provider	The provider that sent the webhook event.
Event Type	The event type received from the provider.
Event ID	The provider event ID, notification ID, or delivery ID.
Process Status	The internal processing status of the event.
Success	Indicates whether the processing result was successful.
Received	The date and time when the webhook event was received.
Processed	The date and time when the webhook event was processed.
Message	The processing message, such as payment captured, subscription updated, or error details.

Signature

The Signature field displays the webhook signature value received from the provider. This is used to verify that the request came from the real payment provider.

Signature verification is important for webhook security. If the signature is missing or invalid, the webhook should not be trusted.

Headers

The Headers field shows the request headers received with the webhook. This may include host, content type, signature, forwarding information, trace IDs, and other HTTP metadata.

Headers are useful when troubleshooting webhook delivery, signature verification, reverse proxy behavior, or provider communication issues.

Raw Body

The Raw Body field shows the original JSON payload received from the payment provider. This is the source data used to parse and normalize the billing event.

{
    "notificationId": "provider-event-id",
    "eventType": "net.authorize.payment.authcapture.created",
    "webhookId": "provider-webhook-id",
    "payload": {
        "responseCode": 1,
        "authCode": "ABC123",
        "authAmount": 4.00,
        "invoiceNumber": "codeattack",
        "entityName": "transaction",
        "id": "120080997728"
    }
}

Normalized Data

The Normalized Data section shows the billing event information after iBoard converts the raw provider payload into an internal billing event structure.

Field	Description
BillingEventId	The internal billing event ID created from the webhook log.
Category	The normalized billing category, if available.
Status	The normalized internal event status.
Date	The normalized event date.
Customer Token	The customer token extracted from the provider payload, if available.
Subscription Token	The recurring subscription token extracted from the provider payload, if available.
Invoice Token	The invoice token or invoice number extracted from the payload, if available.
Transaction Token	The transaction token extracted from the provider payload, if available.
Failure Reason	The normalized failure reason if processing failed.

Recommended Workflow

Open Admin > Billing > Payment Logs.
Select the provider or leave it as All.
Enter an event type if you want to inspect a specific webhook event.
Select a process status, such as SUCCESS or FAILED.
Set the date range using From and To.
Click Search.
Review the event list, customer mapping, status, and message.
Click Detail to inspect the webhook log.
Check Signature, Headers, Raw Body, and Normalized Data.
Use the Back button to return to the log list.

Common Use Cases

Use Case	Recommended Action
Check whether a webhook was received	Search by event type, event ID, or date range.
Investigate failed webhook processing	Filter by FAILED status and open the Detail page.
Check recurring subscription updates	Search for `net.authorize.customer.subscription.updated`.
Check payment capture events	Search for `net.authorize.payment.authcapture.created`.
Verify webhook signature data	Open the Detail page and review the Signature and Headers sections.
Find unmapped customer events	Search logs where Customer shows `unmap`, then review Raw Body and Normalized Data.

Troubleshooting

Problem	Possible Cause	Solution
No logs are displayed	The date range may not include webhook events, or filters may be too restrictive.	Expand the date range, clear filters, and search again.
Log status is FAILED	The webhook was received but failed during parsing, mapping, saving, or normalization.	Open Detail and review Message, Raw Body, and Normalized Data.
Customer shows unmap	The provider event could not be matched to an iBoard customer record.	Review customer token values and update mapping if needed.
Signature is missing or invalid	The provider may not have sent a valid signature, or the webhook secret may be incorrect.	Check provider webhook settings and Payment Configs webhook secret.
Raw Body is difficult to read	The provider payload is shown as raw JSON.	Copy the JSON into a formatter or review the Normalized Data section.
Normalized Data is empty	The raw payload may not contain expected fields, or parsing rules may not support the event type.	Check the event type and update parsing or mapping logic if needed.

Important Notes

Payment Logs are used to inspect webhook and event processing history.
This page does not create payment transactions or recurring subscriptions.
A PROCESSED status means the event was handled by iBoard.
A FAILED status means the webhook was received but processing failed internally.
Raw Body contains the original provider payload and should be reviewed carefully when troubleshooting.
Webhook signature and secret configuration should be treated as security-sensitive information.
Customer mapping may be required when provider events cannot be matched automatically.

Best Practices

Use date filters before searching large webhook history.
Filter by FAILED status first when investigating processing problems.
Use Event Type to isolate specific provider events.
Review Signature and Headers when debugging webhook delivery or security issues.
Review Raw Body before changing parsing or mapping logic.
Do not expose webhook raw payloads or secrets to unauthorized users.

Payment Logs provide the technical evidence of what the payment provider sent and how iBoard processed it. Use this screen when troubleshooting payment events, recurring subscription updates, webhook delivery, and customer mapping issues.