Enable Apple Pay on the Web for PSPs

Apple Pay Request

In the request for authorization from the PSP, the following is passed. For Apple Pay, the merchant should request only the fields that are required to process the transaction.

A sample request is as follows:

{
    "_v" : "1",
    "merchant_account_id" : "example-merchant-account-id",
    "session_id" : "XyY8azgOHUE47HCz6fSBn3AsepzRXE3RbbZc5E5jsWO_xEymN7DlS4ktBrJPQzBY_nBUwSavMyc0fSWNJzu0SA==",
    "order_no" : "0000001",
    "payment" : {
        "payment_id" : "089e4cd378bff63d9d7bd63f8f",
        "type" : "ApplePay",
        "amount" : 1999,
        "currency" : "USD",
        "token": "c90a1cc41f75098afee7d22437479cce29a036ba10452301af65243f57b937ecc90a1cc41f75098afee7d22437479cce29a036ba10452301af65243f57b937ecc90a1cc41f75098afee7d22437479cce29a036ba10452301af65243f57b937ecc90a1cc41f75098afee7d22437479cce29a036ba10452301af65243f57b937ecc90a1cc41f75098afee7d22437479cce29a036ba10452301af65243f57b937ecc90a1cc41f75098afee7d22437479cce29a036ba10452301af65243f57b937ecc90a1cc41f75098afee7d22437479cce29a036ba10452301af65243f57b937ec=="
    },
    "client" : {
        "ip_address" : "127.0.0.1",
        "user_agent" : "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008052912 Firefox/3.0",
        "accept_header" : "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8"
    },
    "customer_info" : {
        "customer_no" : "1234567890",
        "email" : "[email protected]",
        "customer_name" : "John Doe"
    },
    "shipping_address" : {
        "first_name" : "John",
        "last_name" : "Doe",
        "address1" : "5 Wall Street",
        "city" : "Burlington",
        "state_code" : "MA",
        "postal_code" : "12345",
        "country_code" : "US"
    },
    "billing_address" : {
        "first_name" : "John",
        "last_name" : "Doe",
        "address1" : "5 Wall Street",
        "city" : "Burlington",
        "state_code" : "MA",
        "postal_code" : "12345",
        "country_code" : "US"
    },
    "custom" : {
        "avs" : true,
        "fraud" : {
            "profile" : "strict",
            "max_score" : 72,
            "filters" : ["ml", "review"]
        }
    }
} 

Response

The response is as follows:

A sample response for authorization appears as follows:

HTTP 200
{
    "_v" : "1",
    "transaction_id" : "8989127187123781",
    "status" : "authorized"
}     

A sample response for refusal appears as follows:

HTTP 200
{
    "_v" : "1",
    "transaction_id" : "7123781898912718",
    "status" : "refused",
    "reason_code" : "declined"
}  

A sample response for an error appears as follows:

HTTP 400
{
    "_v" : "1",
    "status" : "error",
    "reason_code" : "invalid",
    "message" : "Missing required field: payment.token.payment_data"
}

A sample response that includes customization appears as follows:

{
    "_v" : "1",
    "transaction_id" : "8989127187123781",
    "status" : "authorized",
    "custom" : {
        "auth_code" : 1,
        "card_type" : "Visa",
        "masked_number" : "XXXX-XXXX-XXXX-1111",
        "fraud" : {
            "score" : 51,
            "status" : "REVIEW"
        }
    }
}    

HTTPS Statuses

The HTTPS statuses include:

Reason Codes