What’s new in Wallet and Apple Pay

RSS for tag

Discuss the WWDC22 Session What’s new in Wallet and Apple Pay

Posts under wwdc2022-10041 tag

5 Posts
Sort by:
Post not yet marked as solved
3 Replies
1.4k Views
cannot find details about this in the docs, is order tracking only working together with an ApplePay payment ✅ nevermind, found it
Posted
by elm0cit0.
Last updated
.
Post not yet marked as solved
4 Replies
2.3k Views
I am working on Issuer Extension using which user can add debit/ credit card through wallet directly. This is Extension based (Non and UI Extension. I am nearly implemented this however have doubts about PKIssuerProvisioningExtensionHandler methods which are below open func status(completion: @escaping (PKIssuerProvisioningExtensionStatus) -> Void)  open func passEntries(completion: @escaping ([PKIssuerProvisioningExtensionPassEntry]) -> Void) open func generateAddPaymentPassRequestForPassEntryWithIdentifier(_ identifier: String, configuration: PKAddPaymentPassRequestConfiguration, certificateChain certificates: [Data], nonce: Data, nonceSignature: Data, completionHandler completion: @escaping (PKAddPaymentPassRequest?) -> Void) My query is what is the significance of configuration in last callback. Can anyone please help with this. Thanks in advance
Posted Last updated
.
Post not yet marked as solved
1 Replies
1.2k Views
Hi, I am trying to develop "Add to Apple Pay" feature in our mobile app and been following "Getting Started with Apple Pay In-App Provisioning, Verification & Security 3.0" documentation provided. The issue is after getting encryptedPassData, activationData and ephemeralPublicKey back from our provider, constructing the PKAddPaymenetPassRequest with these values and passing it to the handler is failing. Below is the source code for reference. ---------*** PKAddPaymentPassRequest *request = [[PKAddPaymentPassRequest alloc] init];      NSString* encryptedPassData = args[@"encryptedPassData"];   NSString* activationData =args[@"activationData"];   NSString* ephemeralPublicKey = args[@"ephemeralPublicKey"];      NSData* encryptedPassDataData = [[NSData alloc] initWithBase64EncodedString:encryptedPassData options:0];   NSData* activationDataData = [[NSData alloc] initWithBase64EncodedString:activationData options:0];   NSData* ephemeralPublicKeyData = [[NSData alloc] initWithBase64EncodedString:ephemeralPublicKey options:0];      request.encryptedPassData = encryptedPassDataData;   request.activationData = activationDataData;   request.ephemeralPublicKey = ephemeralPublicKeyData;   handler(request);
Posted
by sai_gen6.
Last updated
.
Post not yet marked as solved
1 Replies
558 Views
I am currently implementing Apple Pay and would like to display the terms/agreement for each recurring product in a list of many. I understand that there is support for one recurring product, but not more than one. Is this possible or are there plans to implement this? Our backend is handling the recurring payments so I just need to display multiple billing agreements. There is a very similar question posted recently here
Posted
by CB-Miller.
Last updated
.
Post not yet marked as solved
1 Replies
667 Views
Hi team! We're currently looking to support Apple Pay v14 in our application along with the automatic payments improvements it brings - specifically recurring payments. It seems that the new functionality here only supports a single recurring payment in the payment sheet, what if we want to list multiple payments which are recurring, is there a way to do this? Although you can see a breakdown of which payments you are due to pay today via the basket line items when clicking the information icon, it seems there is no way to show multiple recurring payments on the payment sheet which forces us to combine data from multiple payments into one start date and amount which gives misleading text when one recurring payment starts on a different date to one of the others. Passing the type as 'pending' and not passing an amount or recurringPaymentStartDate also gives misleading text as it then shows Starting Now and Free so we also can't hide this messaging. What is the recommended approach to support multiple recurring payments with accurate messaging on the payment? Thanks
Posted Last updated
.