Expired pending charges

[KyeRussell]

I have a transaction which (as I can see from the Up app) is a pending charge that expired, with the amount ‘returned’ to my account the next day, showing as another ‘transaction’.

App screenshots

Original purchase

Expiry (in transaction list)

Expiry (after pressing transaction list item)

I can’t see how / where this pending charge expiration is reflected in the API?

Here's how the transaction is currently represented in the API:

{
    "type": "transactions",
    "id": "229a6593-bc21-4787-be94-d992f1884bc2",
    "attributes": {
        "status": "SETTLED",
        "rawText": "AMAZON PRIME*JG2,Amzn.com/bill",
        "description": "Amazon",
        "message": null,
        "isCategorizable": true,
        "holdInfo": null,
        "roundUp": null,
        "cashback": null,
        "amount": {
            "currencyCode": "AUD",
            "value": "-22.87",
            "valueInBaseUnits": -2287
        },
        "foreignAmount": {
            "currencyCode": "USD",
            "value": "-14.99",
            "valueInBaseUnits": -1499
        },
        "cardPurchaseMethod": null,
        "settledAt": "2025-07-16T01:56:46+10:00",
        "createdAt": "2025-07-16T01:56:46+10:00",
        "transactionType": "International Purchase",
        "note": null,
        "performingCustomer": null,
        "deepLinkURL": "up://transaction/VHJhbnNhY3Rpb24tMjA2MDc0MTI4Nw=="
    },
    "relationships": {
        "account": {
            "data": {
                "type": "accounts",
                "id": "9ae6c3a2-ee9c-4498-8d01-98481c719a90"
            },
            "links": {
                "related": "https://api.up.com.au/api/v1/accounts/9ae6c3a2-ee9c-4498-8d01-98481c719a90"
            }
        },
        "transferAccount": {
            "data": null
        },
        "category": {
            "data": null,
            "links": {
                "self": "https://api.up.com.au/api/v1/transactions/229a6593-bc21-4787-be94-d992f1884bc2/relationships/category"
            }
        },
        "parentCategory": {
            "data": null
        },
        "tags": {
            "data": [],
            "links": {
                "self": "https://api.up.com.au/api/v1/transactions/229a6593-bc21-4787-be94-d992f1884bc2/relationships/tags"
            }
        },
        "attachment": {
            "data": null
        }
    },
    "links": {
        "self": "https://api.up.com.au/api/v1/transactions/229a6593-bc21-4787-be94-d992f1884bc2"
    }
}

From what I can see, nothing here indicates that the transaction shouldn't be considered to have lowered my balance. I've also been unable to find any other transactions that reconcile this. I feel like I must be missing something though!

At the end of the day, I really just want to know what I should look out for here to ensure that I correctly interpret this transaction from the perspective of tracking and accounting for balance changes, be that discounting the transaction altogether, or having another transaction that reverses the charge.

Am I missing something? Or is this a limitation of the API?

P.S.: It's also not ideal that performingCustomer wasn't populated either 😛. But I can live with that!

[KyeRussell]

Lol. Never mind. A tale as old as time... Immediately after posting this, I've realised that the charge in my screenshot is almost certainly the "charge from the same merchant in the next couple of days" that the expiration message refers to. My bad!