1.3.2

• Upgraded the Magnes SDK to version 5.5.1

1.3.0

• Add hasUserLocationConsent parameter to PayPalCheckout.start(), PayPalCheckout.startCheckout(), PaymentButtonContainer.setup(), and PaymentButton.setup()

Note: Merchant applications are responsible for collecting user data consent. If your app has obtained consent from the user to collect location data in compliance with Google Play Developer Program policies, set hasUserLocationConsent to true. This flag enables PayPal to collect necessary information required for Fraud Detection and Risk Management.

Merchant applications may be required to display a disclosure before collecting user location data in accordance with Google’s Best practices for prominent disclosures and consent. By setting userHasLocationConsent to true, your app is enabled to share device location data with a third party (PayPal) for Fraud Detection and Risk Management.

Examples of prominent in-app disclosures

Note: If you are seeing the Play Store flag your APK after updating to this version, please try following these steps:

1. Go to your Play Console
2. Select the app
3. Go to App bundle explorer
4. Select the violating APK/app bundle's App version at the top right dropdown menu, and make a note of which releases they are under
5. Go to the track with the violation. It will be one of these 4 pages: Internal / Closed / Open testing or Production
6. Near the top right of the page, click Create new release. (You may need to click Manage track first)
   If the release with the violating APK is in a draft state, discard the release
7. Add the new version of app bundles or APKs
   Make sure the non-compliant version of app bundles or APKs is under the Not included section of this release
8. To save any changes you make to your release, select Save
9. When you've finished preparing your release, select Review release, and then proceed to roll out the release to 100%.
10. If the violating APK is released to multiple tracks, repeat steps 5-9 in each track

1.2.1

• Upgraded the data-collector SDK to version 3.21.0 which made updates to Device Data collection related to Google Play's User Data Policy

Note: If you are seeing the Play Store flag your APK after updating to this version, please try following these steps:

1. Go to your Play Console
2. Select the app
3. Go to App bundle explorer
4. Select the violating APK/app bundle's App version at the top right dropdown menu, and make a note of which releases they are under
5. Go to the track with the violation. It will be one of these 4 pages: Internal / Closed / Open testing or Production
6. Near the top right of the page, click Create new release. (You may need to click Manage track first)
   If the release with the violating APK is in a draft state, discard the release
7. Add the new version of app bundles or APKs
   Make sure the non-compliant version of app bundles or APKs is under the Not included section of this release
8. To save any changes you make to your release, select Save
9. When you've finished preparing your release, select Review release, and then proceed to roll out the release to 100%.
10. If the violating APK is released to multiple tracks, repeat steps 5-9 in each track

1.2.0

This build enables the native flows for buyers in Australia. All other buyers, except those in US, Canada, EU, UK and Australia, will experience web fallbacks.

The following changes are included in this release:

• Minor UI fixes.
• Internal improvements.

1.1.0

This build enables the native flows for buyers in the US, Canada, EU, and UK. All other buyers will see web fallback experiences.

The following changes are included in this release:

• Buy Now Pay Later entry points
• Improved authentication flows in SCA regions
• Minor UI fixes

1.0.0

This build enables the native flows for buyers in the US and Canada. EU buyers will see a web fallback experience.

The following changes are included in this release:

• Fixed UI bugs to ensure a consistent experience for multiple countries and languages
• Fixed an issue that caused users to continue checkout on web when an invalid currency was selected
• Ensures return of relevant billing information such as First Name, Last Name, and Email in the onApprove callback
• Added resource name qualifier to avoid name collisions
• Deprecated the following order actions
  • Patch
  • Capture
  • Authorize
  • GetDetails
  • ExecuteBillingAgreement
  • onShippingChangeAction.Patch

0.112.2

• Added a Discount field to the Cart Details UI on the checkout home page
• Addressed some issues on Vault flows
• Minor UI fixes
• Change policies link to point to user agreement screen
• Third party providers compliance work

0.112.0

Features Updates

• Introduced Pay Later PayPal offerings
• Added the ability for users to add an initial payment method to their PayPal account
• Updated the UI of the native add-card flow to include complete address input
• Added the ability to programmatically logout a PayPal user

Breaking Changes

• Order was renamed to OrderRequest
• SettingsConfig.shouldFailEligibility was renamed to SettingsConfig.showWebCheckout
• Address returned in the OnShippingChange callback was renamed to ShippingChangeAddress

Non-Breaking Changes

• Updated version to 0.112.0 to align with iOS
• Additional bugfixes

GitHub Issues Resolved
#99
#100
#104
#226
#184
#216

0.8.8

This release includes:

• Adding the ReturnUrl requirement back into the CheckoutConfig

0.8.7

This release includes:

• Upgraded the Cardinal SDK to version 2.2.7-2 which made updates to Device Data collection related to Google Play's User Data Policy

Note: If you are seeing the Play Store flag your APK after updating to this version, please try following these steps:

1. Go to your Play Console
2. Select the app
3. Go to App bundle explorer
4. Select the violating APK/app bundle's App version at the top right dropdown menu, and make a note of which releases they are under
5. Go to the track with the violation. It will be one of these 4 pages: Internal / Closed / Open testing or Production
6. Near the top right of the page, click Create new release. (You may need to click Manage track first)
   If the release with the violating APK is in a draft state, discard the release
7. Add the new version of app bundles or APKs
   Make sure the non-compliant version of app bundles or APKs is under the Not included section of this release
8. To save any changes you make to your release, select Save
9. When you've finished preparing your release, select Review release, and then proceed to roll out the release to 100%.
10. If the violating APK is released to multiple tracks, repeat steps 5-9 in each track