Fields mapping for Hub

You can add custom fields to the payment object. In case the epp flow is used, the common approach is to use field names with a stored_ or stored_customer_ prefix.

You can still use the same naming convention with the epms flow, but be aware that fields will be automatically re-mapped according to the rules below.

Main supporter fields

EPP	EPMS
stored_customer_uuid	supporter.uuid
stored_customer_company	supporter.legal_entity
stored_customer_salutation	supporter.salutation
stored_customer_firstname	supporter.first_name
stored_customer_lastname	supporter.last_name
stored_customer_raw_name	supporter.raw_name
stored_customer_phone	supporter.phone
stored_customer_email	supporter.email
stored_customer_email_permission	supporter.email_permission
stored_customer_street	supporter.street
stored_customer_street_number	supporter.house_number
stored_customer_street2	supporter.address_addendum
stored_customer_zip_code	supporter.postal_code
stored_customer_city	supporter.city
stored_customer_state	supporter.region_level_1
stored_customer_country	supporter.country
stored_customer_raw_address	supporter.raw_address
stored_customer_birthdate	supporter.birth_year supporter.birth_month supporter.birth_day

Supporter raisenow parameters fields

Additionaly to supporter.email_permission the following is also set:

EPP	EPMS
stored_customer_email_permission	supporter.raisenow_parameters.integration.opt_in.email

Raisenow integration fields

EPP	EPMS
stored_customer_donation_receipt	raisenow_parameters.integration.donation_receipt_requested
stored_customer_message	raisenow_parameters.integration.message

Supporter custom parameters fields

EPP	EPMS
stored_customer_pobox	supporter.custom_parameters.post_office_box
stored_customer_pan	supporter.custom_parameters.pan
stored_customer_fiscal_code	supporter.custom_parameters.fiscal_code
stored_customer_{fieldname}	supporter.custom_parameters.{fieldname}

Custom parameters fields

EPP	EPMS
stored_{fieldname}	custom_parameters.{fieldname}