Skip to main content
The migrate method allows you to enter Transactions, processed outside Subscribe, to the Subscribe database. Transactions imported to Subscribe using this method are stored in the database. Those that are entered with a status of failed will be processed by Subscribe according to your defined retry schedule. Transactions entered using this method can be searched and analyzed, both through the Subscribe Portal, and using the Transaction.fetchDeltaSince method. After migration, these Transactions will be processed and treated as if they originated with Subscribe, allowing you to use this method to import historic billing information for your customers. When you call this method to import a batch of Transactions, Vindicia queues the data, and then processes it in the order received, before adding it to the database. Lag time exists between the time you migrate a transaction, and the time it appears in the Subscribe database and UI. The lag varies according to your transaction volume, and that of other merchants currently in the queue. Vindicia recommends small batches for this call. If your migrated Transaction volume is high, call Transaction.migrate more often to reduce the amount of data sent in one call. (The optimal batch size depends on the total amount of data being sent.) To minimize timeouts, consider adjusting the timeout setting in the client library and the batch size for the call. Transaction.migrate supports the following payment processors:
  • Chase Paymentech
  • Merchant e-Solutions
  • Litle & Co.
  • PayPal
Transaction.migrate supports the following payment methods:
  • Credit Card
  • PayPal
  • Merchant Accepted Payment (MAP)

Input

srd: sparse response description, a SOAP string (which must be a JSON object), in which you specify the elements you want returned.This parameter enables the calling system to constrain a method call to return only components you specify. This gives you greater control over returned content, and improves response time within the Vindicia platform by reducing the processing needed for the call. Some fields are required, either practically or in the WSDL, and will be returned regardless of the srd. A null srd returns the complete response. migrationTransactions: an array of migrationTransaction objects to import to Subscribe. Note: While this method uses the same migrationTransaction subobject as the AutoBill.migrate method, the two methods require that different data members be populated. Do not populate the following migrationTransaction data members for the Transaction.migrate call:
  • autoBillCycle
  • billingPlanCycle
  • merchantBillingPlanId
Do not populate the following migrationTransactionItem data member for the Transaction.migrate call:
  • merchantAutoBillItemId

Output

return: an object of type Return that indicates the success or failure of the call. response: an array of TransactionValidationResponse objects.

Returns

When you migrate a batch of Transactions, a return code of 200 means that Subscribe has received your data and queued it for processing. During this process, if Subscribe discovers problems with the data that prevent it from being added to the Subscribe database, Subscribe attempts to correct the data. If the attempt fails, Subscribe will ask you to correct the errors and might request that you report the data again. The Return object also contains an attribute called soapId. For the migrate call to succeed, you must log the value of soapId. If, for some reason, the migrated Transactions do not make it into the Subscribe database, provide the soapId value to Subscribe to facilitate tracking of your batch in the Subscribe system. In addition to those listed in The Return Object, this call returns:

Example

Parent topic:Transaction Methods