Migrating from the Sileo API ​

When a client begins to support version 2 of the Payment Specification, the client must be able to seamlessly migrate authentication credentials if desired by the Payment Gateway. To do this, the client will make the following request and handle different responses.
POST /v2/migrate

{
	"migration_source": "payment-v1-sileo",
	"credentials": {
		"auth_token": "f2ca1bb6c7e907d06dafe4687e579fce76b37e4e93b7605022da52e6ccc26fd2",
		"payment_secret": "jr38tgh9t832gew89gt3j8y4hjgmf92r1jt38gfhrq5jtwyhsgfekart0gh9fet8y"
	}
}

As of now, migration source will always only be payment-v1-sileo on this version of the specification

Example Response:

{
	"auth_token": "a5f72a60-e0ad-42c9-a93c-ba1aa642d319",
	"payment_secret": "0f7995e3-14ae-46fc-95f9-1f92f1c33f62",
	"refresh_token": "5ad42376-2be1-405b-a1ee-4aa46330903d"
}