Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

XML-RPC request content

 
Ravi Dhanum
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have some questions regarding the contents of the XML-RPC request to TransMaster.

1) Where is the credit card type (i.e. Mastercard, etc.) listed?
2) Does the merchant id refer to FlyByNight?
3) Is the transaction identifier created by FlyByNight? If so, is it unique only within each credit card type?

Thanks in advance for your help.

BTW, I read in another topic that the XML-RPC message is not encrypted via https. The base64 encryption is a very weak type of encryption. Is it enough to use SSL, or should the message body also be encrypted?

Thanks for reading. Please respond.

-Ravi
 
Ravi Dhanum
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

Is the transaction identifier found in the XML-RPC request created by FlyByNight? If so, is it unique only within each credit card type?

Anyone?

Thank you.

-Ravi
 
Rajah Nagur
Ranch Hand
Posts: 239
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ravi,

1) Where is the credit card type (i.e. Mastercard, etc.) listed?

The credit card type depends on the first digit of the Credit Card number
for Master card it is 5
for Visa card it is 4 .... so on
The next 6 digits identify the bank and the last digits identity the customer

2) Does the merchant id refer to FlyByNight?

Logically it should be FlyByNight, because the debit is done on the customer credit card and credit is done to merchant account i.e FlyByNight
You can state this as your understanding

3) Is the transaction identifier created by FlyByNight? If so, is it unique only within each credit card type?

Again this seems to be created by FlyByNight for each transaction. This transaction id will be useful for cancellations purposes and auditing.

one question,
do we really need to bog down to such details for creating architecture?

regarding the last part, anything over HTTPS is encrypted, because HTTPS is HTTP over SSL and uses PKI. If you keep encrypting message it will be difficult to meet the FBN SLA requirements.

rgds,
rajah
 
Ravi Dhanum
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks, Rajah! This is helpful. Although the details seem unimportant, it may make a difference in the componenent design. Thanks for the help.

-Ravi
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic