Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

String length error for account numbers greater then 15 characters #271

Open
bartoszkwiatkowski opened this issue Sep 30, 2019 · 2 comments
Open

String length error for account numbers greater then 15 characters #271

bartoszkwiatkowski opened this issue Sep 30, 2019 · 2 comments
Labels
awaiting-reply Issue awaiting reply from Developer

Comments

@bartoszkwiatkowski
Copy link

bartoszkwiatkowski commented Sep 30, 2019 •
edited
Loading

Hello,

We're using sdk-dotnet-1.9.4 to call Authorize.NET API. Every time, we are trying to perform transaction request with an AccountNumber longer then 14 characters (so 15-17 in our cases), we're receiving null response with an error posted below.
It looks like SDK adds additional characters into raw call data, and in the result it's size exceeds maximum length of a field.
I would be grateful for any feedback.

Request : request.txt (XML attached as .TXT)
Error from TransactionController : E00003:The 'AnetApi/xml/v1/schema/AnetApiSchema.xsd:id' element is invalid - The value '14909-4440161689035119' is invalid according to its datatype 'String' - The actual length is greater than the MaxLength value.
Api response : NULL
@snavinch
Copy link

snavinch commented Oct 1, 2019

Thanking you for bringing this to our attention. We will communicate to the relevant team.

@gnongsie
Copy link
Contributor

Hi @bartoszkwiatkowski , apologies for the delay.

But v1.9.4 is a couple of years old and the SDK has since been updated several times.

Is it possible to ask you to shift to a newer version?

@gnongsie gnongsie added the awaiting-reply Issue awaiting reply from Developer label Dec 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
awaiting-reply Issue awaiting reply from Developer
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gnongsie @snavinch @bartoszkwiatkowski