testcases.authorization.acquiring.uat.valitor.com Open in urlscan Pro
54.145.55.5  Public Scan

Form analysis
0 forms found in the DOM

Text Content

Public


Documentation Settings
Environment
No Environment
Layout
Double Column
Language
cURL



VALITOR AUTHORIZATION SYSTEM

 * Introduction
 * Overview
 * Authentication
 * Error codes


Response code triggers

Stored Credentials - MIT - CIT - SCA

3D Secure

Token

Address verification

Delayed response

Single Tap
POST
Echo test
Valitor Authorization System

Welcome to the Valitor Authorization System test documentation.


OVERVIEW

Here you can find examples of payment requests for many different scenarios to
help you to intergrate the Valitor host to your payment solution. We try to give
examples of most scenarios but in the ever-changing world of payments a document
like this is never complete. If your usecase is not explained, don't hesitate to
contact our implementation specialist to request further information.


AUTHENTICATION

The Valitor Authorization Host uses Ip address whitelisting and user and
password parameters in the body of every request. To start developing against
Valitor's Authorization API you must first obtain a username (MsgSenderID) and
password (MsgSenderAP) to access the API, which is provided by a Valitor's
implementation specialist.


ERROR CODES

All requests submitted to the host should expect a response with status code
200. All abnomalities are reported in the ResponseCode parameter. See the
documentation,
https://docs.authorization.acquiring.uat.valitor.com/responsecodes/



Response code triggers

In order for partners to test how their system reacts to certain response codes
Valitor provides these response code triggers. The trigger test has no logical
validation on the context so an ecommerce autorization can be used to trigger a
card present only response code. Just use one of the given cardnumbers, one per
supported card scheme, and use the amount to request a given response code.

This does not apply to reject or error codes generated by Valitor (codes that
start with A,M or T).

The amount logic is as follows:

   
 * The amount has to be >1000. All request with amount <= 1000 will get response
   code 00.
   
 * For numeric response codes use the same value in the amount, e.g. for
   response code 05 use 1005, for 85 use 1085.
   
 * For response codes with non numeric characters use the decimal ascii value,
   e.g. for N7 use 1787, 1A use 1165 and for XD use 8868.
     
   * N = 78
     
   * P = 80
     
   * R = 82
     
   * Z = 90
     
   * Q = 81
     
   * A = 65
     
   * X = 88
     
   * D = 68
     
   


POST

Response code trigger

https://authorization.acquiring.uat.valitor.com/process

To try for different card schemes use these cardnumbers and change CardType
parameter accordingly:

For Visa: 4761340000001082

For Mastercard 5204730000003033

For Amex 341111595316301

Bodyurlencoded
MsgType
0100
MsgSenderID

Insert your credentials here

MsgSenderAP

Insert your credentials here

MsgID
123457

Remember to increment between transactions

MerchantXID
0000012ABCDEFGH
MerchantType
5999
TerminalID
35200001
CardType
V
CardNumber
4761340000001082
CardVD
001

001 for Visa and Mastercard. For Amex use 0001

CardExpDate
9912
TransType
17
TransAmount
1005
TransCurrency
352
TransTime
235959
TransDate
1231


Example Request
Response code trigger
View More

curl --location --request POST 'https://authorization.acquiring.uat.valitor.com/process' \
--data-urlencode 'MsgType=0100' \
--data-urlencode 'MsgSenderID=' \
--data-urlencode 'MsgSenderAP=' \
--data-urlencode 'MsgID=123457' \
--data-urlencode 'MerchantXID=0000012ABCDEFGH' \
--data-urlencode 'MerchantType=5999' \
--data-urlencode 'TerminalID=35200001' \
--data-urlencode 'CardType=V' \
--data-urlencode 'CardNumber=4761340000001082' \
--data-urlencode 'CardVD=001' \

Stored Credentials - MIT - CIT - SCA

See documentation here

To try for different card schemes use these cardnumbers and change CardType
parameter accordingly:

Visa: 4761340000028416

Mastercard: 5204730000009394 (exclude parameter TransXID)

Amex: 3411115992415284

Acrynoms:

MIT -> Merchant Initiated Transaction

CIT -> Cardholder Initiated Transaction

EMV3DS -> 3DS version >= 2.0

TRA -> Transaction Risk Analysis

LOW -> Low value


POST

First Transaction

https://authorization.acquiring.uat.valitor.com/process

When the merchant stores the payment credentials for use later with subsequent
transactions the first transaction needs to be a fully authenticated
authorization (EMV3DS).

Use TransAmount 0 when testing InitiationResaon CRE, 1000 when it's REC and 5000
when it's INS for an authorized response.

Bodyurlencoded
Mandatory variables

MsgType
0100
MsgSenderAP

Insert your credentials here

MsgSenderID

Insert your credentials here

MsgID
123456

Remember to increment between transactions

MerchantXID
0000012ABCDEFGH
MerchantType
5999
TerminalID
35200001
CardType
V
CardNumber
4761340000028416
CardExpDate
9912
TransType
15

A First transaction must be fully authenticated using EMV 3DS

TransAmount
0
TransCurrency
352
TransTime
235959

Represents the local time at the time of purchase, not when the transaction is
sent to Valitor

TransDate
1231

Represents the date at the time of purchase, not when the transaction is sent to
Valitor

CAVD
AENTRU1VUDYlLGl/eTtSLiQ8Ync=
dsTransID
dffc1e22-b02d-5af6-8000-0000000028a9

Mandatory for transacions authenticated using EMV 3DS (version 2.*)

Conditional variables

Initiator
C
InitiationReason
CRE

CRE for unscheduled credential on file. Other valid values are REC for recurring
and INS for installment.

TransXID
fcc5708b024a4d879b13484ef91ec67b00000000

Visa and Amex

CardVD
123

Not requeid in 3DS but recommended

AVSStreetAddress
26 Diswellstown WayCastleknockD

Optional

AVSPostalCode
D15 XK33

Optional

MerchantName
TestMerchant

Required for payment facilitators

MerchantCity
TestCity

Required for payment facilitators



Example Request
First Transaction
View More

curl --location --request POST 'https://authorization.acquiring.uat.valitor.com/process' \
--data-urlencode 'MsgType=0100' \
--data-urlencode 'MsgSenderAP=' \
--data-urlencode 'MsgSenderID=' \
--data-urlencode 'MsgID=123456' \
--data-urlencode 'MerchantXID=0000012ABCDEFGH' \
--data-urlencode 'MerchantType=5999' \
--data-urlencode 'TerminalID=35200001' \
--data-urlencode 'CardType=V' \
--data-urlencode 'CardNumber=4761340000028416' \
--data-urlencode 'CardExpDate=9912' \

POST

Subsequent CIT

https://authorization.acquiring.uat.valitor.com/process

All subsequent transactions must provide the TransLCID from the response of the
First Transaction.

Subsequent CIT's must either request an exemption from SCA or be fully
authenticatd (EMV3DS).

Use the following amounts to trigger test cases:

3000 -> Fully authenticatd CIT, authorized.

3300 -> CIT with exemption, authorized.

3400 -> CIT with exemption, soft declined.

Bodyurlencoded
Mandatory variables

MsgType
0100
MsgSenderAP

Insert your credentials here

MsgSenderID

Insert your credentials here

MsgID
123456

Remember to increment between transactions

MerchantXID
0000012ABCDEFGH
MerchantType
5999
TerminalID
35200001
CardType
V
CardNumber
4761340000028416
CardExpDate
9912
TransType
12
TransAmount
3000
TransCurrency
352
TransTime
235959

Represents the local time when the purchase was made

TransDate
1231

Represents the date at the time of purchase

CAVD
AENTRU1VUDYlLGl/eTtSLiQ8Ync=

If no exemptions are requested the subsequent transaction must be fully
authenticated

dsTransID
dffc1e22-b02d-5af6-8000-0000000028a9

Mandatory for transacions authenticated using EMV 3DS (version 2.*)

Conditional variables

CardVD
123

Not requeid in 3DS but recommended

TransXID
fcc5708b024a4d879b13484ef91ec67b00000000

If no exemptions are requested the subsequent transaction must be fully
authenticated

AVSStreetAddress
26 Diswellstown WayCastleknockD

Optional

AVSPostalCode
D15 XK33

Optional

Initiator
C
InitiationReason
CRE

CRE is the only valid reason for a subsequent CIT

ScaExcemtion

TRA, LOW or AUTO.
https://docs.authorization.acquiring.uat.valitor.com/online-payments/sca-exemptions/

MerchantName
TestMerchant

Required for payment facilitators

MerchantCity
TestCity

Required for payment facilitators



Example Request
Subsequent CIT
View More

curl --location --request POST 'https://authorization.acquiring.uat.valitor.com/process' \
--data-urlencode 'MsgType=0100' \
--data-urlencode 'MsgSenderAP=' \
--data-urlencode 'MsgSenderID=' \
--data-urlencode 'MsgID=123456' \
--data-urlencode 'MerchantXID=0000012ABCDEFGH' \
--data-urlencode 'MerchantType=5999' \
--data-urlencode 'TerminalID=35200001' \
--data-urlencode 'CardType=V' \
--data-urlencode 'CardNumber=4761340000028416' \
--data-urlencode 'CardExpDate=9912' \

POST

Subsequent MIT

https://authorization.acquiring.uat.valitor.com/process

All subsequent transactions must provide the TransLCID from the response of the
First Transaction.

Subsequent MIT's are exempt from SCA.

Use the following combination of amount and InitiationReason for successful
authorization:

CRE -> 3500

REC -> 4000

INS -> 5000

Industry specific:

https://docs.authorization.acquiring.uat.valitor.com/point-of-sale/merchant-initiated-transactions/

INC -> 100

RES -> 200

DEL -> 300

REA -> 400

NOS -> 500

Bodyurlencoded
Mandatory variables

MsgType
0100
MsgSenderAP

Insert your credentials here

MsgSenderID

Insert your credentials here

MsgID
123456

Remember to increment between transactions

MerchantXID
0000012ABCDEFGH
MerchantType
5999
TerminalID
35200001
CardType
V
CardNumber
4761340000028416
CardExpDate
9912
TransType
12

A First transaction must be fully authenticated using EMV 3DS

TransAmount
4000
TransCurrency
352
TransTime
235959

Represents the local time when the purchase was made

TransDate
1231

Represents the date at the time of purchase

TransLCID
000000110743978

The TransLCID from the response of the first transaction.

Conditional variables

Initiator
M
InitiationReason
REC
MerchantName
TestMerchant

Required for payment facilitators

MerchantCity
TestCity

Required for payment facilitators



Example Request
Subsequent MIT
View More

curl --location --request POST 'https://authorization.acquiring.uat.valitor.com/process' \
--data-urlencode 'MsgType=0100' \
--data-urlencode 'MsgSenderAP=' \
--data-urlencode 'MsgSenderID=' \
--data-urlencode 'MsgID=123456' \
--data-urlencode 'MerchantXID=0000012ABCDEFGH' \
--data-urlencode 'MerchantType=5999' \
--data-urlencode 'TerminalID=35200001' \
--data-urlencode 'CardType=V' \
--data-urlencode 'CardNumber=4761340000028416' \
--data-urlencode 'CardExpDate=9912' \

3D Secure

See documentation here


FOR VISA USE THE FOLLOWING DATA:

CardNumber: 4761340000032467

CAVD:

ACIzRFVmd4iZAKq7zN3u/wAAAAA= (Fully authenticated, use TransType 15)

BwAQBUOXMAEAABYQRZcwEK7jDto= (Attempt, use TransType 16 for approval or 15 to
force a transtype downgrade)

AddddFVmd4iZAKq7zN3u/wAAAAB= (Fully authenticated, but will get declined, use
TransType 15)


FOR MASTERCARD USE THE FOLLOWING DATA:

CardNumber: 5204730000004635

CAVD:

kBMcQDw42rjEKBDCA/WQw5eBlMGf (Fully authenticated, use TransType 15)

kL23456789012345678912345675 (Attempt, use TransType 16 for approval or 15 to
force a transtype downgrade)

kL00000089012345678912345675 (Fully authenticated, but will get declined, use
TransType 15)


FOR AMEX USE THE FOLLOWING DATA:

CardNumber: 3411115992419401

CAVD:

AAABBWcSNIdjeUZThmNHAAAAAAA= (Fully authenticated, use TransType 15)

BwABB0gSNIJ4V2hIBglWAAAAAAA= (Attempt, use TransType 16)

BBBBBWcSNIdjeUZThmNHAAAAAAA= (Fully authenticated, but will get declined, use
TransType 15)


POST

3DS

https://authorization.acquiring.uat.valitor.com/process

This example can be used as a base for all types of 3DS transactions. Just
replace the data as shown above, CAVD, TransType and CardNumber (and CardType
accordingly).

HEADERS
Content-Type
application/x-www-form-urlencoded
Bodyurlencoded
Mandatory variables

MsgType
0100
MsgSenderAP

Insert your credentials here

MsgSenderID

Insert your credentials here

MsgID
123456

Remember to increment between transactions

MerchantXID
0000012ABCDEFGH
MerchantType
5999
TerminalID
35200001
CardType
M
CardNumber
5204730000004635
CardExpDate
9912
TransType
16

Fully authenticated using EMV 3DS

TransAmount
1000
TransCurrency
352
TransTime
235959

Represents the local time at the time of purchase, not when the transaction is
sent to Valitor

TransDate
1231

Represents the date at the time of purchase, not when the transaction is sent to
Valitor

CAVD
kL23456789012345678912345675
dsTransId
6518afc3-2a1d-4d17-b25e-8c00db6381ah

Required if EMV 3DS was used. Not applicable for 3DS version 1.0

Conditional variables

TransXID
fcc5708b024a4d879b13484ef91ec67b00000000

Visa and Amex only. Do not include in Mastercard transactions

CardVD
123

Not requeid in 3DS but recommended

AVSStreetAddress
26 Diswellstown WayCastleknockD

Optional

AVSPostalCode
D15 XK33

Optional

MerchantName
TestMerchant

Required for payment facilitators

MerchantCity
TestCity

Required for payment facilitators



Example Request
3DS
View More

curl --location --request POST 'https://authorization.acquiring.uat.valitor.com/process' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'MsgType=0100' \
--data-urlencode 'MsgSenderAP=' \
--data-urlencode 'MsgSenderID=' \
--data-urlencode 'MsgID=123456' \
--data-urlencode 'MerchantXID=0000012ABCDEFGH' \
--data-urlencode 'MerchantType=5999' \
--data-urlencode 'TerminalID=35200001' \
--data-urlencode 'CardType=M' \
--data-urlencode 'CardNumber=5204730000004635' \

Token


POST

Token transaction

https://authorization.acquiring.uat.valitor.com/process

Transaction using a tokenized account number.

TransType = 1B or 1C

Test 1 - CAVD passes validation: Amount: 5000 CAVD: ANdddFVmd4iZAKq7zN3u/wAAAAA=
No AdditionalData

Test 2 - CAVD does not pass validation: Amount: 7000 CAVD:
mQAAAAAAd4iZAKq7zN3u/wAAAAA= AdditionalData: 0200207

Bodyurlencoded
Mandatory variables

MsgType
0100
MsgSenderAP

Insert your credentials here

MsgSenderID

Insert your credentials here

MsgID
123456

Remember to increment between transactions

MerchantXID
0000012ABCDEFGH
MerchantType
5999
TerminalID
35200001
CardType
V
CardNumber
4761340000054693
CardExpDate
9912
TransType
1B

Optionally 1C if terminal location is on premises.

TransAmount
5000
TransCurrency
352
TransTime
235959

Represents the local time at the time of purchase, not when the transaction is
sent to Valitor

TransDate
1231

Represents the date at the time of purchase, not when the transaction is sent to
Valitor

CAVD
ANdddFVmd4iZAKq7zN3u/wAAAAA=

Here you should put the token cryptogram, TAVV or DSRP depending on card scheme.
NOTE! In the near future a new parameter will be introduced so that an
authorization can include both the token cryptogram and authentication data,
CAVV or UCAF.

Conditional variables

MerchantName
TestMerchant

Required for payment facilitators

MerchantCity
TestCity

Required for payment facilitators

AdditionalData
0200207


Example Request
Token transaction
View More

curl --location --request POST 'https://authorization.acquiring.uat.valitor.com/process' \
--data-urlencode 'MsgType=0100' \
--data-urlencode 'MsgSenderAP=' \
--data-urlencode 'MsgSenderID=' \
--data-urlencode 'MsgID=123456' \
--data-urlencode 'MerchantXID=0000012ABCDEFGH' \
--data-urlencode 'MerchantType=5999' \
--data-urlencode 'TerminalID=35200001' \
--data-urlencode 'CardType=V' \
--data-urlencode 'CardNumber=4761340000054693' \
--data-urlencode 'CardExpDate=9912' \

Address verification

See documentation here


FOR VISA USE THE FOLLOWING DATA:

CardNumber: 4761340000091885

CardType: V AVSStreetAddress: Dalshraun
AVSPostalCode: 220 CardVD: 123

Will return an AVS match, parameter AVSR = X Anything else will return AVS
nomatch, AVSR = G


FOR MASTERCARD USE THE FOLLOWING DATA:

CardNumber: 5204730000008255

CardType: M AVSStreetAddress: Dalshraun
AVSPostalCode: 220 CardVD: 123

Will return an AVS match, parameter AVSR = X Anything else will return AVS
nomatch, AVSR = G


FOR AMEX USE THE FOLLOWING DATA:

CardNumber: 3411115992415821

CardType: A AVSStreetAddress: Dalshraun
AVSPostalCode: 220 CardVD: 1234

Will return an AVS match, parameter AVSR = Y Anything else will return AVS
nomatch, AVSR = N


POST

AVS

https://authorization.acquiring.uat.valitor.com/process

This example can be used as a base for Address Verification transactions.

HEADERS
Content-Type
application/x-www-form-urlencoded
Bodyurlencoded
Mandatory variables

MsgType
0100
MsgSenderAP

Insert your credentials here

MsgSenderID

Insert your credentials here

MsgID
123456

Remember to increment between transactions

MerchantXID
0000012ABCDEFGH
MerchantType
5999
TerminalID
35200001
CardType

CardNumber

CardExpDate
9912
TransType
17
CardVD
1234
TransAmount
1000
TransCurrency
352
TransTime
235959

Represents the local time at the time of purchase, not when the transaction is
sent to Valitor

TransDate
1231

Represents the date at the time of purchase, not when the transaction is sent to
Valitor

Conditional variables

AVSStreetAddress
Dalshraun
AVSPostalCode
220
MerchantName
TestMerchant

Required for payment facilitators

MerchantCity
TestCity

Required for payment facilitators



Example Request
AVS
View More

curl --location --request POST 'https://authorization.acquiring.uat.valitor.com/process' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'MsgType=0100' \
--data-urlencode 'MsgSenderAP=' \
--data-urlencode 'MsgSenderID=' \
--data-urlencode 'MsgID=123456' \
--data-urlencode 'MerchantXID=0000012ABCDEFGH' \
--data-urlencode 'MerchantType=5999' \
--data-urlencode 'TerminalID=35200001' \
--data-urlencode 'CardType=' \
--data-urlencode 'CardNumber=' \

Delayed response

For Visa use CardNumber: 4761340000010307

For Mastercard use CardNumber: 5204730000007505

For Amex use CardNumber: 3411115992413578

Default delay is 5 sek. but the following delays can be triggerd with the
amount, regardless of the currency:

3001 -1 sec

3002 - 2 sec

3005 - 5 sec

3010 - 10 sec

3015 - 15 sec

3030 - 30 sec

The authhost will timout at 18 sek and respond with AW.


POST

Delayed response

https://authorization.acquiring.uat.valitor.com/process
Bodyurlencoded
MsgType
0100
MsgSenderID

MsgSenderAP

MsgID
123457
MerchantXID
0000012ABCDEFGH
MerchantType
5999
TerminalID
35200001
CardType
V
CardNumber
4761340000010307
CardVD
001
CardExpDate
9912
TransType
17
TransAmount
3005
TransCurrency
352
TransTime
235959
TransDate
1231


Example Request
Delayed response
View More

curl --location --request POST 'https://authorization.acquiring.uat.valitor.com/process' \
--data-urlencode 'MsgType=0100' \
--data-urlencode 'MsgSenderID=' \
--data-urlencode 'MsgSenderAP=' \
--data-urlencode 'MsgID=123457' \
--data-urlencode 'MerchantXID=0000012ABCDEFGH' \
--data-urlencode 'MerchantType=5999' \
--data-urlencode 'TerminalID=35200001' \
--data-urlencode 'CardType=V' \
--data-urlencode 'CardNumber=4761340000010307' \
--data-urlencode 'CardVD=001' \

Single Tap

Single-Tap requires two transactions to complete the scenario.

Use cardnumber 5204730000007364.

The first transaction is a contactless transaction that should include the
parameter SingleTapSupported=1. It may also include PinBlock and
PinBlockKeyIndex. The response code will be 65 if the PinBlock is omitted and 55
if it's included. All amounts except 50 will return SingleTapSupported=1 that
indicates issuer support for Single-Tap.

The second transaction should only follow if the issuer supports Single-Tap. It
must include a PinBlock and PinBlockKeyIndex and the TransLCID from the first
transaction. This will result in a response code 00. If there is something
incorrect, the response code will be 30.


POST

Contactless

https://authorization.acquiring.uat.valitor.com/process

This example can be used as a base for all Single-Tap transactions. Just replace
the data as explained above.

HEADERS
Content-Type
application/x-www-form-urlencoded
Bodyurlencoded
Mandatory variables

MsgType
0100
MsgSenderAP

Insert your credentials here

MsgSenderID

Insert your credentials here

MsgID
123456

Remember to increment between transactions.

MerchantXID
0000042ABCDEFGH
MerchantType
5999
TerminalID
35200002
CardType
M
CardNumber
5204730000007364
CardExpDate
9912
TransType
44

contactless / proximity payment

TransAmount
1000

Amount 50 will trigger that issuer does not support single-tap. All other amount
will return support for single-tap.

TransCurrency
352
TransTime
235959

Represents the local time at the time of purchase, not when the transaction is
sent to Valitor.

TransDate
1231

Represents the date at the time of purchase, not when the transaction is sent to
Valitor.

Conditional variables

SingleTapSupported
1
Track2
5204730000007364D25122010000000000
ICCData
5F2A02035282027D00950500000080009A031609159C01009F02060000000010009F03060000000000009F0902008C9F100706010A03A000029F1A0203529F260824E4C09B606699A89F2701809F3303E0B8C89F34031E03009F3501229F360200029F37046B9A9D02
TransLCID

Used in the second transaction. Use the value form the first transaction
response.

PinBlock
5CA96C6DE6BCD749

If included in the first transaction it will trigger response code 55. Mandatory
in the second transaction.

PinBlockKeyIndex
1

Always included in conjunction with PinBlock.



Contactless First Transaction
Example Request
View More

curl --location --request POST 'https://authorization.acquiring.uat.valitor.com/process' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'MsgType=0100' \
--data-urlencode 'MsgSenderAP=Insert your credentials here' \
--data-urlencode 'MsgSenderID=Insert your credentials here' \
--data-urlencode 'MsgID=123456' \
--data-urlencode 'MerchantXID=0000042ABCDEFGH' \
--data-urlencode 'MerchantType=5999' \
--data-urlencode 'TerminalID=35200002' \
--data-urlencode 'CardType=M' \
--data-urlencode 'CardNumber=5204730000007364' \

POST

Echo test

https://authorization.acquiring.uat.valitor.com/process

The simplest message avaliable. Use it to check for conncectivity and
correctness of credentials.

Bodyurlencoded
MsgType
0800
MsgCode
900
MsgSenderID
MonitorUser

To start developing against Valitor's Authorization API you must first obtain a
username (MsgSenderID) and password (MsgSenderAP) to access the API, which is
provided by a Valitor's implementation specialist.

MsgSenderAP
monitoruser

To start developing against Valitor's Authorization API you must first obtain a
username (MsgSenderID) and password (MsgSenderAP) to access the API, which is
provided by a Valitor's implementation specialist.

MsgID
{{MsgID}}

The Pre-request script generates a random MsgID value



Example Request
Echo test response

curl --location --request POST 'https://authorization.acquiring.uat.valitor.com/process' \
--data-urlencode 'MsgType=0800' \
--data-urlencode 'MsgCode=900' \
--data-urlencode 'MsgSenderID=MonitorUser' \
--data-urlencode 'MsgSenderAP=monitoruser' \
--data-urlencode 'MsgID={{MsgID}}'

Example Response
200 OK
Body
Header(7)

MsgType=0810&MsgID=175070&ResponseCode=00&ResponseSource=A