For the complete documentation index, see llms.txt. This page is also available as Markdown.

Web Transactions Processed Using Hyperswitch Decryption (Without Apple Merchant ID)

Process Apple Pay web transactions through Hyperswitch decryption without requiring an Apple Merchant ID

In this flow Hyperswitch decrypts the token internally using own certificates and then transforms the raw data for any downstream connector.

Mechanism:

  1. Frontend sends apple pay payment token to Hyperswitch.

  2. Hyperswitch unwraps the token using your private key stored in its secure vault.

  3. Hyperswitch maps the DPAN and Cryptogram to the destination PSP’s API.

Configuration :

Steps to configure Apple Pay on Hyperswitch

  • In the Processor tab, select desired connector

  • While selecting Payment Methods, click on Apple Pay in the Wallet section

  • Select the Web Domain option

  • Download the domain verification file using the button available

  • Host this file on your server at merchant_domain/.well-known/apple-developer-merchantid-domain-association

  • Enter the domain name where you have hosted the domain verification file

  • Click on verify and enable to complete your setup

You can use the following text in the email
  • Attach our PCI DSS AoC certificate and copy our Support team (support.global@juspay.io).

  • Stripe Account id: <Enter your account id: you can find it here>

  • A detailed business description: <One sentence about your business>. The business operates across xx countries and has customers across the world.

  • Feature Request: We are using Hyperswitch, a Level 1 PCI DSS 3.2.1 compliant Payments Orchestrator, to manage payments on our website. In addition to Stripe, since we are using other processors as well to process payments across multiple geographies, we wanted to use Hyperswitch’s Payment Processing certificate to decrypt Apple pay tokens and send the decrypted Apple pay tokens to Stripe. So, please enable processing decrypted Apple pay token feature on our Stripe account. We’ve attached Hyperswitch’s PCI DSS AoC for reference.

Last updated

Was this helpful?