Skip to main content

Configuration

Before any wallet payments can be processed via Stitch, the following configuration is required with the supported providers. Payments can be processed on Visa and Mastercard card networks via a payment cryptogram generated securely on the device. PAN-only (offline) wallet payments are not currently supported.

tip

Different configuration requirements apply if your target application framework is web or native. For example, if you use the React Native framework for a mobile application, the Web configuration requirements should be adhered to.

Apple Pay​

Web​

To enable Apple Pay as a wallet payment method on your client, you need to have an active Apple Developer account and complete the following steps as an Administrator user:

  • Register a merchant ID
    • This uniquely identifies your business as a merchant that can accept Apple Pay payments.
    • Stitch recommends the same merchant identifier across wallet providers. Stitch will provide this merchant identifier for use during your onboarding journey.
  • Create a Merchant Identity and Payment Processing certificates
    • For both certificates, Stitch will provide a Certificate Signing Request (CSR) file.
    • The Payment Processing certificate is used to decrypt payment data.
    • The Merchant Identity certificate is used to authenticate payment sessions with Apple Pay servers.
    • Upload the CSRs on the Apple Developer portal to create each certificate.
    • Securely share the created certificates with Stitch. Stitch will securely store and manage these certificates to process payment data on your behalf.
  • Verify the web domain(s) that will host the Apple Pay button
    • All domains and/or sub-domains that display a payment button must be verified by Apple before payment processing can be supported.

For more information on the aforementioned steps, including certificate generation, view the Apple Pay Merchant Integration Guide.

Mobile​

To enable Apple Pay as a wallet payment method on your client, you need to have an active Apple Developer account and complete the following steps as an Administrator user:

  • Register a merchant ID
    • This uniquely identifies your business as a merchant that can accept Apple Pay payments.
    • We recommend the same merchant identifier across wallet providers. Stitch will provide this merchant identifier for use during your onboarding journey.
  • Create a Payment Processing certificate
    • Stitch will provide a Certificate Signing Request (CSR) file.
    • The Payment Processing certificate is used to decrypt payment data.
    • Upload the CSR on the Apple Developer portal to create the certificate.
    • Securely share the created certificate with Stitch. Stitch will securely store and manage these certificates to process payment data on your behalf.

For more information on the setup, view the Setting up Apple Pay Guide.

Samsung Pay​

Web​

To enable Samsung Pay as a wallet payment method on your client, no action is required on your part. Stitch handles the merchant configuration and domain verification with the provider. During onboarding, Stitch will request a list of domains and/or sub-domains that will host a Samsung Pay payment button for verification.

Mobile​

To enable Samsung Pay as a wallet payment method on your client, you need to register for a Samsung Pay Developers account. Complete the following steps post-registration:

  • Create a service. Share the Service ID with Stitch.
  • Register your Android application.

Google Pay​

The configuration requirements for a web and mobile integration are identical. To enable Google Pay™ as a wallet payment method on your client, you need to register with the Google Pay and Wallet Console to receive a Google merchant ID (googlePayMerchantId).

Stitch will seperately provision and issue you with a gateway merchant identifier (gatewayMerchantId) to facilitate payment processing. This gateway merchant identifier will be the same ID recommended for use with Apple Pay. Please contact support@stitch.money for assistance with this.

Note that you are required to adhere to the Google Pay APIs Acceptable Use Policy and accept the terms defined by the Google Pay API Terms of Service.

Limitations
  • CRYPTOGRAM_3DS is the only 3DS authorisation method supported.
  • Stitch currently does not support collection or verification of address details for wallets.

Acquirer​

If you have an existing relationship with a supported acquiring bank, you will be requested to provide the configured merchant identifier (MID) during onboarding. As an Independent Sales Organisation (ISO) business, funds will be settled directly into the account held with the acquiring bank.