Yes, that looks about right for the TMF654 V4 payload although your endpoint (URL) has a v1 and lowercase rather than lowerCamelCase for the API name. If you plan to integrate via the TMF676 Payment Management API, you can use the PaymentMethod at this level instead. All depends on your specific implementation/requirements.
Note that the TMF654 V5 has recently been published.
------------------------------
Dan d'Albuquerque
Entronica Company Limited
------------------------------
Original Message:
Sent: Jan 29, 2025 06:06
From: Imene Tekaya
Subject: Prepay Balance Management API TMF654 : Topup
Hello Thank you for your reply , so It will be like this :
POST …/api/prepaybalancemanagement/v1/topupBalance
{
"channel": {
"name": "Maxit"
},
"logicalResource": [
{
"@type": "msisdn",
"value": "010101010101"
}
],
"paymentMethod": {
"id": "PM1",
"name": "DigitalWallet",
"authorizationCode": "1234567",
"@type": "DigitalWallet",
},
"voucher":""
}
------------------------------
Imene Tekaya
Sofrecom Tunisie
------------------------------
Original Message:
Sent: Jan 28, 2025 21:01
From: Dan d'Albuquerque
Subject: Prepay Balance Management API TMF654 : Topup
Hi Imene
The voucher in the TopupBalance entity (task resource) was typically used for the (old) scratch cards PIN (Orange Top-Up).
For topping up via the Orange digital wallet, have you considered the Payment Method (see below). You can extend these entities to align with your specific use case.

------------------------------
Dan d'Albuquerque
Entronica Company Limited