The Meta Info can contain some useful additional informations for donation, recurring payment and transaction. Of course all values are optional. Following keys are possible:
// personal message from the donor
message
// selected item of the form
item_id
item_name
// charity sms info
charitySms_phone
charitySms_shortId
charitySms_keyword
charitySms_operator
charitySms_message
// if company donation some employee info
employee
employee_salutation
employee_title
employee_first_name
employee_last_name
employee_birthday
// indicates if newsletter checkbox was active
wants_newsletter
// Wikando direct debit info
wikando_direct_debit_chargeback_reason
wikando_direct_debit_chargeback_purpose
wikando_direct_debit_chargeback_charges
// paypal info
paypal_mc_fee
paypal_reason_code
// stripe info
stripe_fee
// amazon pay
amazon_pay_fee
amazon_pay_reverse_reason
// micropayment info
micropayment_direct_debit_pay_date
micropayment_prepay_pay_text
micropayment_prepay_bank_name
micropayment_prepay_iban
micropayment_prepay_bic
micropayment_prepay_due_date
// donation payment failure information (for unsuccessful donations)
failed_error
// Adresslabor (not available in XML Rest-API)
adresslabor_fake_traffic_light
adresslabor_name_traffic_light
raw_salutation
raw_title
raw_first_name
raw_last_name
adresslabor_address_trafficlight
raw_address
raw_post_code
raw_city
XML
Most of the values of these keys are CDATA, except:
- item_id (integer)
- wants_newsletter (integer, 0 | 1)
- employee_salutation (predefined string see Predefined values)
- micropayment_direct_debit_pay_date (date)
- micropayment_prepay_due_date (date)
- stripe_fee (number)
<meta_info>
<message>
<![CDATA[Danke für Ihren Einsatz!]]>
</message>
<item_id type="integer">123</item_id>
<item_name>
<![CDATA[Beispiel]]>
</item_name>
...
</meta_info>
JSON
Simple key value pairs:
{
"item_id": 123,
"item_name": "Beispiel",
"wants_newsletter": 1
...
}