docs(avs-for-moto): correct AVS scope, validation and result behaviour - #201
Open
flozanofdez wants to merge 2 commits into
Open
docs(avs-for-moto): correct AVS scope, validation and result behaviour#201flozanofdez wants to merge 2 commits into
flozanofdez wants to merge 2 commits into
Conversation
The page claimed AVS applies to MOTO Refund, that the merchant flag has no effect on the gateway, and that the AVS result is returned on both the SDK and Cloud API. Verified against viscus, cloudapi and hapi-android: billing is accepted on MOTO Sale and Pre-Authorization only; the gateway rejects billing with error 4070 when avsForMoto is disabled; and the result code is only exposed on the back-office /moto/sale response. Adds the field rules QA needs to write expected results — the 20/50 length limits, the control-character and long-digit-sequence guards, and the exact 400 messages — plus the result-code vocabulary and the behaviour of billing on referenced operations. Co-Authored-By: Claude Code - Claude Opus 5 <noreply@anthropic.com>
Both removed at review. The long-digit-sequence guard and the token-sale `enableAvsFields` caveat are implementation detail an integrator doesn't need to reason about; the rules that shape a request stay documented. Co-Authored-By: Claude Code - Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
QA needed confirmed AVS behaviour to close the test suite. Verifying the questions against
viscus,cloudapiandhapi-androidturned up five claims on the AVS page that don't match the code.What was wrong
operationsWithBilling = ['moToSale','moToPreAuthorization'](cloudapi); onlyMotoSaleRequest/MotoPreAuthRequestcarryBillingData(viscus);MotoRefundTransaction.isAvsSuitable = false(SDK)billingwith AVS not enabled → "no special handling"4070(MotoBaseService.applyAvsGating). A third state exists — flag never configured → billing dropped, no errorMoToBaseResponsehas noaddressVerificationfield and ignores unknown properties, andPOST /transactionsreturns the SDK's result. OnlyPOST /moto/salesurfaces itTransactionResult.avsResult(EPI agent skill)addressVerification.resultCodeenableAvsFieldsshown as a working optioncardTokensale routes toMotoSaleTransactionWithToken, which has no card-entry screenWhat was added
🤖 Generated with Claude Code