Skip to main content

Add, Remove, or Replace a Payment Method

Dependencies

Build a New App With Payments or Add Payments to an Existing App - the builder must know about your app specifications.

Install the Required Development Tools.

Spin Up a Test Backend or Connect to an Existing Backend - the builder will know not to make a test payment at the end if a backend is missing.

Example prompts

Generic requests: "Add an alternative payment flow", "Accept payments with GooglePay", "Remove the payment flow".

Or alternatively, if the merchant is familiar with the SDK: "Remove the SimplyConnect payment flow", "Add a second payment method with Fields".

The builder is able to add different modules on top of existing ones without disturbing the rest of your app. The modules are hosted checkout (Simply Connect), card fields, Apple Pay and Google Pay.

  • Add - writes only the new module's layer. Everything else, including your customisations, is untouched.
  • Remove - takes out a module you no longer need, and its dependencies.
  • Replace - swaps one module for another while keeping the customisations you applied.
  • Refresh - if you would rather reset it back to the original and drop the customisation.