IOS: Payment cancelled while doing payment from UPI

[helians11]

• I have updated Purchases SDK to the latest version
• I have read the Contribution Guidelines
• I have searched the Community
• I have read docs.revenuecat.com
• I have searched for existing Github issues

Describe the bug
On IOS, while making a payment through UPI in India, the purchase is getting cancelled in background when i go to the payment app for accepting the payment.
Error Code is PURCHASE_CANCELLED in the above case as soon as i go to payment app, Payment is successful but error code is incorrect in this case.

1. Environment
   1. Platform: IOS
   2. SDK version: 9.6.15
   3. OS version:
   4. Xcode/Android Studio version:
   5. React Native version: 0.73.11
   6. SDK installation (CocoaPods + version or manual):
   7. How widespread is the issue. Percentage of devices affected.
2. Debug logs that reproduce the issue
3. Steps to reproduce, with a description of expected vs. actual behavior
4. Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.)

Additional context
Here is the code snippet

const purchasePackage = async (
  parentAuthId: string,
  parentServiceId: string,
  pkg: PurchasesPackage,
) => {
  return withInAppPurchase(parentAuthId, parentServiceId, async () => {
    try {
      const result = await Purchases.purchasePackage(pkg);

      return result;
    } catch (error) {
      logError(InAppPurchaseAnalyticsEvents.PURCHASE_PACKAGE_FAILED, {
        error,
        parentAuthId,
        parentServiceId,
      });
      throw error;
    }
  });
};


const purchase = useCallback(
    (pkg: PurchasesPackage) => {
      return purchasePackage(parentAuthId, parentServiceId, pkg);
    },
    [parentAuthId, parentServiceId],
  );


const handlePurchase = useCallback(async () => {
    if (!selectedPlan) {
      return;
    }

    setStatus('inprogress');
    trackEvent(getAnalyticsEvent('purchase', 'inprogress'), { plan_type: planType });

    try {
      await purchase(selectedPlan);

      validateCustomerInfo();
    } catch {
      setStatus('failed');
    }
  }, [selectedPlan, planType, purchase, validateCustomerInfo]);

[RCGitBot]

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

[facumenzella]

Thanks for reporting this @helians11 . I've done some investigation and have a strong hypothesis on what's happening.

Root Cause (Hypothesis)

When you switch to your UPI payment app, the iOS app goes to background and Apple's payment sheet returns an undocumented error (SKError code 907 with underlying AMSError code 6 - paymentSheetFailed).

In purchases-ios, this error is mapped to PURCHASE_CANCELLED based on RevenueCat/purchases-ios#1445, where this same error was observed during actual user cancellations. The problem is that Apple returns the same error code for both scenarios:

• User explicitly taps Cancel
• Payment sheet loses focus (e.g., app switches to UPI app)

The SDK can't currently distinguish between these two cases. Could you help confirm this?

1. Please enable debug logging and reproduce the issue:Purchases.setLogLevel(LOG_LEVEL.DEBUG);
2. share the logs when the error occurs. We're looking for something like:
   SKError(code: 907) ... AMSErrorDomain ... code: 6

This would confirm our hypothesis.

Workaround

In the meantime, I think you can verify the actual purchase status after receiving PURCHASE_CANCELLED in UPI flows with something like:

  try {                                                                                                                                
    await Purchases.purchasePackage(pkg);                                                                                              
  } catch (error) {                                                                                                                    
    if (error.code === PURCHASES_ERROR_CODE.PURCHASE_CANCELLED_ERROR) {                                                                
      // For UPI flows, check if payment actually succeeded                                                                            
      const customerInfo = await Purchases.getCustomerInfo();                                                                          
      if (customerInfo.entitlements.active['your_entitlement_id']) {                                                                   
        // Payment succeeded despite the error                                                                                         
        return handleSuccess(customerInfo);                                                                                            
      }                                                                                                                                
    }                                                                                                                                  
    throw error;                                                                                                                       
  }

[helians11]

@facumenzella Yes you are correct, that is what is happening.
To handle this correctly, we need to rely on the following error codes:

1. PURCHASES_ERROR_CODE.PURCHASE_CANCELLED_ERROR
2. PURCHASES_ERROR_CODE.PURCHASE_PENDING_ERROR

With this we also need to poll by setting a predefined timeout window for payment status.
Please update this in your docs, so that this helps others as well. Currently this behaviour is not mentioned anywhere in the document.

This approach will solve this issue.

[facumenzella]

I'll try to wrap up this tomorrow!! I'll ping once I have something @helians11 and again thanks for the report

[facumenzella]

@helians11 I think RevenueCat/purchases-ios#6207 should do the trick but I wonder if you want to test it out first?

[helians11]

@facumenzella I use react native sdk. Could you help me get that version so that i can test it from my end.
Currently i am on RN 0.73.11

[helians11]

@facumenzella Any update ?