CODEWITHSUNDEEP
applepayemv3d-securedpan
Michał Ziobro
Michał Ziobro

Reputation: 11812

Apple Pay Payment Processing on Server Side

Is it legal and possible to: 1. Get PKPaymentToken in iOS app 2. Send this token to server side 3. Decrypt this PKPaymentToken (ex. based on many available GitHub libraries) 4. I have now: 

{
    "applicationExpirationDate": "190131",
    "applicationPrimaryAccountNumber": "370295XXXXX5435",
    "currencyCode": "840",
    "deviceManufacturerIdentifier": "XXXXXXXXXX",
    "paymentData": {
        "emvData": "nycBgJ82AgDCnyYIG2vuQydGkMafEAcGhgEDoLABXzQBAJUFgAABAACCAhzAnwMGAAAAAAAAnxoCCECaAxQQBJwBAJ83BLnvab4="
    },
    "paymentDataType": "EMV",
    "transactionAmount": 100
}

5. Use this data to make transaction in such way:

Here I have doubt! To make transaction I can use only this EMV or 3DS cryptogram in paymentData -> emvData (or 3dsecure) Or I can use applicationPrimaryAccountNumber as casual Card Number (or maybe this is different from Card Number printed on physical plastic Card?)

Why I am asking? On the server, I have integration with another external system that handles transactions. And there is a library that takes credit card information (card number, expiry date, cardholder) to make the transaction.

Will I be able to use this decrypted data to pass raw card number, exp date, cardholder to this library to make transaction payment happen. Or this library must be able to handle this EMV, 3DSecure cryptograms only?

Thanks for the clarification.

Upvotes: 0

Views: 1086

Answers (0)

Related Questions