Magento payment : additional_information or payment attribute?

Magento payment : additional_information or payment attribute?

August 9, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento payment : additional_information or payment attribute?

Magento Payment: Additional Information or Payment Attribute? A Developer’s Perspective

As a senior developer specializing in e-commerce platforms like Magento, I often encounter questions about the best way to store additional information related to payments. In this post, we’ll explore the two primary methods—using additional_information or creating a custom payment attribute—and determine which approach is most suitable for your needs.

Understanding Additional Information

The additional_information field in Magento allows you to store serialized data associated with a payment method. This data is stored as an array and can be accessed using the getAdditionalInformation() method provided by the sales/payment model.

To add custom information like a “payment due date,” you can use the setAdditionalInformation() method:

$payment->setAdditionalInformation('payment_duedate', $myDate);
$payment->save();

While this approach is straightforward, it’s essential to understand its limitations. Since data is serialized, querying and retrieving information becomes more complex compared to a standard database column.

Creating a Custom Payment Attribute

An alternative method is to create a custom payment attribute, which involves adding a new field to the sales_flat_order_payment table. This approach allows you to store your “payment due date” directly in the database as an easily queryable column named payment_duedate.

To achieve this, follow these steps:

  1. Create a new XML file (e.g., app/code/local/Your_Company/Your_Module/etc/config.xml) and define your custom attribute:
<config>
    <global>
        <sales>
            <quote>
                <item_options>
                    <payment_duedate>
                        <label>Payment Due Date</label>
                        <type>date</type>
                        <input_type>text</input_type>
                        <sort_order>100</sort_order>
                    </payment_duedate>
                </item_options>
            </quote>
        </sales>
    </global>
</config>
  1. Update your payment model (e.g., app/code/local/Your_Company/Your_Module/Model/Payment.php) to include the custom attribute:
class Your_Company_Payment extends Mage_Sales_Model_Order_Payment
{
    public function setPaymentDuedate($date)
    {
        $this->setData('payment_duedate', $date);
    }

    public function getPaymentDuedate()
    {
        return $this->getData('payment_duedate');
    }
}

Now, you can save and retrieve the “payment due date” using the following methods:

$payment->setPaymentDuedate($myDate);
$payment->save();

$paymentDueDate = $payment->getPaymentDuedate();

Which Approach is Best?

The choice between additional_information and a custom payment attribute depends on your specific requirements.

Use the additional_information method if:

  • You need to store small amounts of data associated with multiple entities.
  • Querying and retrieving information is not critical for your use case.

Opt for a custom payment attribute if:

  • You require easy querying and fast retrieval of custom payment-related data.
  • The data you want to store is unique and directly related to the payment process.

In conclusion, both methods have their merits depending on your specific needs. However, creating a custom payment attribute generally provides better performance and easier data management for critical information like “payment due dates.”

Database Orders

Our network