Skip to main content
The Blocks and Connect guides use these versions:
These packages are pre-1.0, so a minor version can include breaking changes. Review the changes below and test in test mode before deploying.

@ionicfi/sdk 0.4.1

Select a connected merchant per request

Pass { account } as the second argument to a supported method. The SDK sends Ionic-Account for that request.
PaymentIntents, SetupIntents, and customers accept the option. Requests that manage payment domains or webhook endpoints act on the platform itself and take no account. See How Connect works.

Manage API keys in the dashboard

The apiKeys resource is removed. Create, list, and rotate merchant keys in Developers → API keys and platform keys in Connect → API keys. Remove server jobs that called ionic.apiKeys. Authentication covers key permissions and storage.

Reference payments by Ionic IDs

Charge and Refund responses contain Ionic fields only. The gateway and gateway_transaction_id fields are no longer returned on Charge, and gateway_transaction_id is no longer returned on Refund. Use the Ionic Charge and Refund IDs for retrieval, refunds, and support requests.

@ionicfi/js 0.2.1

Ionic Blocks

loadIonic(publishableKey) returns a client with blocks, confirmPayment, confirmSetup, retrievePaymentIntent, and retrieveSetupIntent. Platforms pass { account: connectedMerchantId } as the second argument. Follow Build a payment page or Accept payments for connected merchants. mountPaymentFields remains available for tokenization-only integrations. See Advanced card fields.

Embedded checkout

loadIonicCheckout and IonicCheckout.mountSession are unchanged. Apple Pay on embedded checkout continues to render in your page, and its domain registration is unchanged.

@ionicfi/react 0.2.1

CheckoutEmbed and its props are unchanged. The package depends on @ionicfi/js 0.2.1, so update both together. For a custom payment form in a React app, mount a Block from @ionicfi/js in an effect and destroy it on unmount.

Before you deploy

  • Run the payment, save, and uncertain-result paths in test mode with test cards.
  • Confirm your Content Security Policy allows the Ionic script, API, and frame hosts.
  • Register live webhook endpoints and verify a signature before launch. See Going live.