topic Re: Update ARB Subscription Request - Error E00013 in Integration and Testing

Update ARB Subscription Request - Error E00013

Waterhouse — Mon, 10 Dec 2018 20:45:33 GMT

I'm trying to update arb subscriptions to point at new customer payment profiles. However, the API returns error E00013 with message "Phone is invalid. Phone can be one of following formats: 111- 111-1111 or (111) 111-1111."

I'm not even submitting the phone number with the request. Here's the code I'm using to construct the request (ruby SDK):

profile = CustomerProfileIdType.new(@info[:profile_id],@info[:payment_profile_id])
ARBUpdateSubscriptionRequest.new(
  nil,
  nil,
  @subscription_id,
  ARBSubscriptionType.new(nil,nil,nil,nil,nil,nil,nil,nil,nil,profile)
)

That code contructs a request that looks like this:

<arbupdatesubscriptionrequest>
  <subscriptionId>395823xx</subscriptionId>
  <subscription>
    <profile>
      <customerProfileId>19217479xx</customerProfileId>
      <customerPaymentProfileId>19557806xx</customerPaymentProfileId>
    </profile>
  </subscription>
</arbupdatesubscriptionrequest>

Why should I get a phone number error in this case?

Maybe the phone number on the customer profile is invalid. But if that's the case, then why am I able to submit the create customer profile request and the create subscription request without error?

Re: Update ARB Subscription Request - Error E00013

ElaineM — Tue, 11 Dec 2018 06:05:58 GMT

Hi Waterhouse,

If you are seeing this error it is likely that you would see this error when/if you attempted to process transactions using the stored profile data as well, which is why you are seeing the error at this step.

I can guess at the cause, but without specific details that may not be the best approach.

I would suggest using our Developer Support email form found at https://developer.authorize.net/support/contact_us/ to reach out to our support staff. Please provide them with full subscription, profile ID and payment profile ID information for reference when reviewing your account.

Thank you,

Elaine

Re: Update ARB Subscription Request - Error E00013

Waterhouse — Thu, 13 Dec 2018 18:55:31 GMT

Hi Elaine,

I filled out the contact form a few days ago, but they still haven't replied yet.

I can cofirm processing transactions using the "invalid" profile information works perfectly fine. We are able to charge our user's cards, and the monthly subscription payments also work fine. We're just not able to update a subscription to use a different payment profile.

As a stopgap measure, when users update their profile to use a different card, I've been cancelling their current subscription and creating a new subscription that begins on their next billing date. I don't want to have to continue doing this because we lose certain other information like how many payments they've made on their current subscription.

Re: Update ARB Subscription Request - Error E00013

Waterhouse — Tue, 18 Dec 2018 00:08:09 GMT

Still no answer from dev support. Is there any way I can get assistance on here?

Re: Update ARB Subscription Request - Error E00013

Waterhouse — Sat, 22 Dec 2018 17:24:56 GMT

Still no answer from dev support. pls respond

Re: Update ARB Subscription Request - Error E00013

kikmak42 — Wed, 26 Dec 2018 12:04:55 GMT

Hi @Waterhouse,

Can you share more information on the phone number in that CustomerPaymentProfile (not actual phone number but just the format), which would help us to investigate faster.

Thanks

Kaushik

Re: Update ARB Subscription Request - Error E00013

Waterhouse — Mon, 31 Dec 2018 19:09:46 GMT

Phone numbers are stored in E.164 format

https://support.twilio.com/hc/en-us/articles/223183008-Formatting-International-Phone-Numbers

Re: Update ARB Subscription Request - Error E00013

Waterhouse — Thu, 03 Jan 2019 01:58:05 GMT

We deal with international customers, so storing phone numbers in the USA only format of (111) 111-1111 is out of the question.

For example, it's impossible to store the number +442071838750 using the """correct""" format

Re: Update ARB Subscription Request - Error E00013

kabutotx — Thu, 03 Jan 2019 03:48:08 GMT

What country was the Profile created in? Maybe it is US and forcing US number format?

Re: Update ARB Subscription Request - Error E00013

Waterhouse — Sat, 05 Jan 2019 05:31:19 GMT

This happens to all of our customers that enter a new card regardless of what country they're from

Re: Update ARB Subscription Request - Error E00013

Waterhouse — Sat, 05 Jan 2019 05:40:44 GMT

I really don't see how this could anything other than an anet bug

createCustomerProfile: passes validation
transactions using stored profile information: passes validation
create subscription with stored profile information: passes validation
createCustomerPaymentProfile with existing profile: passes validation
update subscription to use new payment profile: fails validation

Every payment profile is submitted with a phone number in E.164 format, but validation only fails on subscription update. I'm beginning to suspect that this issue will never be solved

Re: Update ARB Subscription Request - Error E00013

RichardH — Mon, 07 Jan 2019 00:58:42 GMT

@Waterhouse

Are you including a + sign in the phone number?

Richard

Re: Update ARB Subscription Request - Error E00013

Waterhouse — Mon, 07 Jan 2019 04:49:15 GMT

Yeah. Would it work if I omitted it?

Re: Update ARB Subscription Request - Error E00013

Waterhouse — Sat, 12 Jan 2019 19:12:06 GMT

I did a little experimenting, and the update request only succeeds if both the old payment profile and the new payment profile have phone numbers in US format, which means that it's impossible to make this work for international customers.

Is there any way I can get any help with this whatsoever? It's been over a month since I messaged dev support, and they never replied.

Is there maybe a way to control API validations from the dashboard? It makes no rational sense for this validation to be present on subscription update and not on any other requests.

Is the phone number important on the customer profile? Maybe I could just put in a filler number for every customer and save their real number in our db.

I really wish you guys would just make ARB work properly instead of making me spend so much time coming up with workarounds.