Added by the PayChan amendment.

Add additional XRP to an open payment channel, update the expiration time of the channel, or both. Only the source address of the channel can use this transaction. (Transactions from other addresses fail with the error tecNO_PERMISSION.)

Example PaymentChannelFund:

    "Account": "rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn",
    "TransactionType": "PaymentChannelFund",
    "Channel": "C1AE6DDDEEC05CF2978C0BAD6FE302948E9533691DC749DCDD3B9E5992CA6198",
    "Amount": "200000",
    "Expiration": 543171558

PaymentChannelFund Fields

In addition to the common fields, a PaymentChannelFund transaction uses the following fields:

Field JSON Type Internal Type Description
Channel String Hash256 The unique ID of the channel to fund, as a 64-character hexadecimal string.
Amount String Amount Amount of XRP, in drops to add to the channel. To set the expiration for a channel without adding more XRP, set this to "0".
Expiration Number UInt32 (Optional) New Expiration time to set for the channel, in seconds since the Ripple Epoch. This must be later than either the current time plus the SettleDelay of the channel, or the existing Expiration of the channel. After the Expiration time, any transaction that would access the channel closes the channel without taking its normal action. Any unspent XRP is returned to the source address when the channel closes. (Expiration is separate from the channel's immutable CancelAfter time.) For more information, see the PayChannel ledger object type.

If the destination account has been deleted, the transaction fails with tecNO_DST. This is only possible if the payment channel was created before the fixPayChanRecipientOwnerDir amendment became enabled (on 2020-05-01).