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​

The configuration process for Apple Pay differs depending on your client's risk classification. Low-risk clients benefit from a simplified setup managed by Stitch, while high-risk clients are required to manage their own Apple Developer account and merchant configuration. This classification applies for both test and live clients.

Low-Risk Clients​

For low-risk clients, Stitch manages the Apple Pay merchant configuration internally. No Apple Developer account is required on your part.

Web​

  • Stitch will assign and configure an Apple Pay merchant ID on your behalf.
  • Provide Stitch with a list of web domains and/or subdomains that will host the Apple Pay button. The verification path must be publicly accessible, or you must whitelist Apple's IP addresses for domain verification to succeed.
  • Stitch will supply a domain verification file that must be hosted on each of the specified domains before they can be registered and whitelisted with Apple.
    • The verification file must be served at the /.well-known/apple-developer-merchantid-domain-association path on each domain (note: the file does not have a .txt extension).
  • Once Stitch has verified the domain(s), Apple Pay will be enabled for your client.

Mobile​

  • Stitch will assign and configure an Apple Pay merchant ID on your behalf.
  • No additional Apple Developer account setup is required.

High-Risk Clients​

High-risk clients are required to create and manage their own Apple Pay merchant configuration via an active Apple Developer account.

Web​

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​

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.

Domain Whitelisting

Domains must be whitelisted for both test and live environments. Provide Stitch with your full list of domains (including any staging or test domains) during onboarding to ensure Samsung Pay is functional across all environments.

Mobile​

To enable Samsung Pay as a wallet payment method on your client, you need to register for a Samsung Pay Developers account. Stitch will provide a Certificate Signing Request (CSR) to be used for configuration. Complete the following steps post-registration:

  • Create an InApp Online Payment Service.
  • Select 'Stitch Money' as the Payment Gateway (PG)
  • Upload the Stitch-provided CSR
  • Register an Android application and specify the package name that corresponds with your app.
  • Add the email address(es) linked to Samsung Wallet to 'Test accounts' to facilitate testing

Google Pay​

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

You will also need to register with the Google Pay and Wallet Console to receive a Google merchant ID. This should be used as your googlePayMerchantId value. Additionally, you will need to onboard with Google based on your integration method (detailed further here):

Test vs Production

Google Pay Console onboarding (screenshots and approval) is only required for production. Test clients can process Google Pay transactions without completing the Console onboarding steps below.

Web​

  • In your Google Console, within the 'Google Pay API' section, select 'Integrate with your website'.
  • Specify the domain of your website to be integrated with.
  • Choose 'Gateway' as your integration type.
  • Provide screenshots of your test integration within your website. Google requires the following screens to validate your integration:
    • Item selection screen — showing items or services available for purchase.
    • Pre-purchase screen — displaying the Google Pay button as a payment option.
    • Payment method screen — showing Google Pay selected as the payment method, including the total amount.
    • Post-purchase/confirmation screen — showing a successful order/payment confirmation.
  • Once Google onboarding has been submitted and approved, you will be able to process payment tokens from Google Pay (via the Stitch SDK and Stitch API).

Mobile​

  • In your Google Console, within the 'Google Pay API' section, select 'Integrate with your Android app'.
  • Select the relevant Android APK that Google Pay will be integrated into.
  • Choose 'Gateway' as your integration type.
  • Provide screenshots of your test integration within your Android APK. Google requires the following screens to validate your integration:
    • Item selection screen — showing items or services available for purchase.
    • Pre-purchase screen — displaying the Google Pay button as a payment option.
    • Payment method screen — showing Google Pay selected as the payment method, including the total amount.
    • Post-purchase/confirmation screen — showing a successful order/payment confirmation.
  • Once Google onboarding has been submitted and approved, you will be able to process payment tokens from Google Pay (via Google Pay API and Stitch API).

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
  • 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.