TMS Service Release Notes

v2.10.014

• feat: add multi-acquirer support and the new Service API (API Reference(Multi-Acquirer)). Multi-acquirer is available on request. Please contact MineSec to enable it. Once it is enabled, the legacy Service API returns error 13310 and the new Service API must be used

  	Legacy Service API	New Service API
  Base path	/api/v2	/api/openapi/v1
  Acquirers per merchant	One	Multiple
  Merchant–acquirer binding	A field on the merchant	Separate merchant payment config: payment methods, EMV and MID per acquirer
  Acquirer type	Card only	card or wallet (e.g. qr), payment methods must match the type
  Currency	Not explicit	Required on merchant, EMV and acquirer profile
  Device payment params	One set	Configured per acquirer
  Delete payment config	Removes one payment method	Removes the whole acquirer binding

  Transaction (/api/v2/order) and Settlement (/api/v2/settle) APIs are unchanged and work with both.

• feat: add incremental authorization. The authorized amount of a pre-auth can be increased via the management portal, mobile application or Service API

• feat: persist geo-fence verification results with transactions, including denied payments

• feat: add Country field for merchants

• feat: display merchant VAT number on email receipts