Visa Developer Community

Highlighted

The Mobile Push Payment project use iso8583?

Hello,

 

I am starting the project to pay with mobile, on push mode, this is: The cardholder send the transaction. Under this scenary I found a documentation that indicate the use of iso8583 the documentation is: "Mobile Push Payments Technical Specifications". Howerver, the site page at Visa developer center, in the examples on mpush is not use the iso8583. Only is used a JSON with the field to the payments.

 

I have a doubt. there is use of 8583 under JSON?

if the spec documentation indicate 200 and 210 msg to pay, why the example at Visa Developer Center is not use the iso8583?

 

 

Regards

 

Hernando Cortes

Tags (1)
7 REPLIES 7
Visa Dev Moderator

Re: The Mobile Push Payment project use iso8583?

Hey @HernandoCortesR,

 

That's a good question. Can you please confirm what API your question relates to? Are you relating your question to Visa Direct?

 



Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.

Thanks,
Diana

Tags (1)
Highlighted

Re: The Mobile Push Payment project use iso8583?

Hi Diana, Thank by the answer.

 

Of course. The API is “mVisa API” the function is [MerchantPushPayments POST]. There is a example: on JSON format:

 

// REQUEST // URL POST

https://sandbox.api.visa.com/visadirect/mvisa/v1/merchantpushpayments

// Header Accept: application/json,application/octet-stream Authorization: {base64 encoded userid:password}

// Body

 

{

  • "senderAccountNumber": "4027290077881587",
  • "localTransactionDateTime": "2020-01-08T22:49:13",
  • "purchaseIdentifier": {
    • "type": "0",
    • "referenceNumber": "REF_123456789123456789123"

},

  • "merchantCategoryCode": "5812",
  • "feeProgramIndicator": "123",
  • "transactionCurrencyCode": "356",
  • "acquiringBin": "408972",
  • "acquirerCountryCode": "356",
  • "retrievalReferenceNumber": "412770451035",
  • "senderReference": "",
  • "secondaryId": "123TEST",
  • "cardAcceptor": {
    • "idCode": "CA-IDCode-77765",
    • "name": "Visa Inc. USA-Foster City",
    • "address": {
      • "country": "IN",
      • "city": "KOLKATA"

}

  • },
  • "recipientPrimaryAccountNumber": "4123640062698797",
  • "systemsTraceAuditNumber": "451035",
  • "businessApplicationId": "MP",
  • "amount": "124.05",
  • "senderName": "Jasper",
  • "settlementServiceIndicator": "9"

}

 

Are you relating your question to Visa Direct?  YES

On the other hand. This API is related at VISA Developer Center as DOCS/VISA DIRECT/API Reference

mVisa API

 

 
Highlighted
Visa Dev Moderator

Re: The Mobile Push Payment project use iso8583?

Hey @HernandoCortesR,

 

Thanks for confirming your question relates to Visa Direct. I'll take a look and get back to you soon on this.

 



Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.

Thanks,
Diana

Highlighted
Visa Dev Moderator

Re: The Mobile Push Payment project use iso8583?

Hey @HernandoCortesR,

 

To answer your question, Visa Direct/mVisa APIs are financial transactions and use VisaNet for processing; so the specs could include ISO mapping for APIs.

 

Visa Developer APIs do not support ISO 8583 messages. Visa Developer APIs use standard interfaces such as JSON, which is used for ease of integration.

 

Also, mVisa is only offered via APIs.

 

 



Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.

Thanks,
Diana

Highlighted

Re: The Mobile Push Payment project use iso8583?

Diana

 

if I use Visa Developer APIs to development, under sanbox. Then I need do a migration to Iso8583 on environment production?

 

Regards,

 

Hernando

Highlighted
Visa Dev Moderator

Re: The Mobile Push Payment project use iso8583?

Hey @HernandoCortesR,

 

Can you please provide us with more details about your company? Are you a developer representing an Issuer/Acquirer etc.?

 

I'd like to add to my answer that Mobile Push Payments can be implemented either using ISO connection or by using the APIs which uses JSONs. mVISA APIs have been provided to simplify the integration. If you are using mVISA APIs, you don’t need to worry about the ISO fields.

 

The Technical Implementation Guide has references to ISO8583 fields for acquirers/issuers who are already connected to VISA using ISO and can enable Mobile Push Payments by enhancing their existing connection.

We recommend doing the API based integration.

 

I hope this answers your question and I hope you're having a wonderful day.

 

Also, I'll get back to you on your questions about a migration to ISO8583 in the production environment. 

 

 



Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.

Thanks,
Diana

Highlighted
Visa Dev Moderator

Re: The Mobile Push Payment project use iso8583?

Hey @HernandoCortesR,

 

If you are using the Visa Developer Platform APIs to develop in sandbox, then you do not need to migrate to ISO in the production environment.

 



Was your question answered? Don't forget to click on "Accept as Solution" to help other devs find the answer to the same question.

Thanks,
Diana