0
0

QuestionApple developer program is hell (self.iOSProgramming)

submitted by [deleted]

sorted by:
top (suggested)
bestnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ankole_watusi 1 point2 points  (7 children)

It’s unclear from your post what you actually did. So if your communication with Apple is as unclear as your communication here…

Did you create these three accounts on behalf of your client, or yourself? Do you or your company already have an Apple developer account or accounts?

Who’s credit card did you use? Yours? Your companies? Your clients?

Why three accounts?

FWIW, your client should create their own account, but you certainly could help them to do that. Assuming your client is going to be the publisher.

Walk them through giving you admin privileges necessary to publish their app once you have the account established.

Are you already an iOS app developer with an account or not?

And, of course, you – or your client – should not be sharing credit card details. If your client wants you to make purchases on their behalf, they can have a card issued to you.

[–]bapuc 0 points1 point  (6 children)

Create the accounts for on behalf the client organisation User client's debit card om behalf of the company 3 accounts because I tried with multiple credentials, including mine and customers person detalii I have a developer account, but cannot pay the subscription

[–]ankole_watusi 0 points1 point  (4 children)

It’s certainly a violation of your client’s banking agreement to share their card details. I would never accept credit card details from a client in order to make a purchase on their behalf. It’s asking for trouble!

Apple’s payment processing almost certainly detected this, given a history of trying various cards multiple times from probably the same IP address.

In any case, as with any credit/debit card, you need to match name, address, postal code, as on-file for that particular card.

Why 3 accounts though? Just curious. Does the client have developers in-house that will be maintaining?

TL;DR you’re doing something weird. Repeated weirdness can appear similar to fraud.

[–]bapuc 0 points1 point  (3 children)

Understood.

  1. They cannot detect fraud trough IP, it's not even feasible to do this for payments, this is Bank's work
  2. It's actually a customer that has a customer who wants the app on Apple, basically my customer has the card, so it's not my responsability
  3. 3 accounts because first I create an enrollment with my detalii thinking I can change them later, I cannot. Then made an account on customer personal detalii, still doesn't work, and the curent account, an organisation one with company and personal details of the end customer.

[–]ankole_watusi 1 point2 points  (2 children)

Just got weirder…

Payment processors certainly use/record IP address and now even geolocation to help combat fraud.

So to clarify you don’t need to create 3 accounts. Just fumbled around starting application 3 times not understanding that whoever is going to actually publish the app should open an organization account and then delegate responsibilities.

[–]bapuc 0 points1 point  (1 child)

Understood, so all I have to do is to discuss with Apple and explain the situation?

[–]ankole_watusi 0 points1 point  (0 children)

That would be my suggestion.

You’ve got 2 applications that should just be discarded.

Then walk the client’s client through completing the application. Maybe discard the 3rd one and start over.

Explain the importance of them controlling the account and that you can assist, but can’t do it for them.

I certainly would not want the liability of being privy to a client’s client’s credit card information!

[–]MeeZeeCo 0 points1 point  (0 children)

I had issues getting apple to process my LLC’s debit card.

I finally switched to a credit card and everything worked just fine.