Skip to main content
v2.1 → v2.2
  • customer object added
  • isVaulted field is added and if set to true then paymentMethodToken will be the multi-use token. If false, it’ll be the single-use token. Previously, paymentMethodToken was always the single-use token.
Example webhook when payment is created:
v2.0 → v2.1
v2.01 is the same as v2.0, so this migration guide applies for v2.01 as well.
  • no longer return the order object
  • paymentMethod.vaultedPaymentMethodToken is no longer returned. paymentMethodToken is now returned but this is always the single-use token (If you are keen to retrieve the multi-use token from the webhook, see the v2.2 updates).
  • Transaction objects now include date, amount and currencyCode
  • no longer return the following fields from paymentMethod object:
    • cryptogram
    • eci
    • threeDsVersion
    • domainServerTransactionId
    • networkTransactionId
    • cvvAvailable
    • transStatus
Example webhook when payment is created: