{"title":"Affirm iOS Component integration","category":"default","creationDate":1776961628,"content":"

This page explains how to add Affirm to your existing Components integration.<\/p>\n

Requirements<\/h2>\n

Select the server-side flow<\/a> that your integration uses:<\/p>\n\n

\n
\n \n <\/tabs>\n <\/div>\n<\/div>\n\n

API reference<\/h2>\n

Select which endpoint you are using:<\/p>\n\n

\n
\n \n <\/tabs>\n <\/div>\n<\/div>\n\n

Component configuration<\/h2>\n

v5.0.0 or later<\/h3>\n

If your integration uses iOS Components v5.0.0 or later, configure and create an instance of the Affirm Component:<\/p>\n\n

\n
\n \n <\/tabs>\n <\/div>\n<\/div>\n\n

v4.x.x<\/h3>\n

If your integration uses an earlier version of iOS Components:<\/p>\n

\n <\/code-sample>\n<\/div>\n

There are no configuration steps specific to Affirm required for Components.<\/p>\n

Optional configuration<\/h3>\n

Pre-filled shopper data<\/h3>\n

You can add configuration with the shopper's information, so that you can pre-fill the payment form.<\/p>\n

The data<\/code> property includes the following information that you can pre-fill:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Property<\/th>\nDescription<\/th>\nData type<\/th>\n<\/tr>\n<\/thead>\n
personalDetails.firstName<\/code><\/td>\nThe shopper's first name.<\/td>\nString<\/td>\n<\/tr>\n
personalDetails.lastName<\/code><\/td>\nThe shopper's last name.<\/td>\nString<\/td>\n<\/tr>\n
personalDetails.dateOfBirth<\/code><\/td>\nThe shopper's date of birth. Format: YYYY-MM-DD<\/code>.<\/td>\nString<\/td>\n<\/tr>\n
personalDetails.shopperEmail<\/code><\/td>\nThe shoppers' email address.<\/td>\nString<\/td>\n<\/tr>\n
personalDetails.telephoneNumber<\/code><\/td>\nThe shopper's telephone number.<\/td>\nString<\/td>\n<\/tr>\n
billingAddress.street<\/code><\/td>\nThe street name for the billing address.<\/td>\nString<\/td>\n<\/tr>\n
billingAddress.houseNumberOrName<\/code><\/td>\nThe house number or name for the billing address.<\/td>\nString<\/td>\n<\/tr>\n
billingAddress.postalCode<\/code><\/td>\nThe postal code for the billing address.<\/td>\nString<\/td>\n<\/tr>\n
billingAddress.city<\/code><\/td>\nThe city for the billing address.<\/td>\nString<\/td>\n<\/tr>\n
billingAddress.stateOrProvince<\/code><\/td>\nThe state, province, or region for the billing address.<\/td>\nString<\/td>\n<\/tr>\n
billingAddress.country<\/code><\/td>\nThe two-character ISO 3166-1 alpha-2 country code<\/a> for the billing address.<\/td>\nString<\/td>\n<\/tr>\n
deliveryAddress.street<\/code><\/td>\nThe street name for the delivery address.<\/td>\nString<\/td>\n<\/tr>\n
deliveryAddress.houseNumberOrName<\/code><\/td>\nThe house number or building name for the delivery address.<\/td>\nString<\/td>\n<\/tr>\n
deliveryAddress.postalCode<\/code><\/td>\nThe postal code for the delivery address.<\/td>\nString<\/td>\n<\/tr>\n
deliveryAddress.city<\/code><\/td>\nThe city for the delivery address.<\/td>\nString<\/td>\n<\/tr>\n
deliveryAddress.stateOrProvince<\/code><\/td>\nThe state, province, or region for the delivery address.<\/td>\nString<\/td>\n<\/tr>\n
deliveryAddress.country<\/code><\/td>\nThe two-character ISO 3166-1 alpha-2 country code<\/a> for the delivery address.<\/td>\nString<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n <\/code-sample>\n<\/div>\n

Payment form fields configuration<\/h3>\n

In the payment form, you can configure if groups of fields are visible or can be edited by the shopper.<\/p>\n

Use the visibility<\/code> property to configure groups of fields with the possible values:<\/p>\n