Menu

User Tools

Create PDF

Site Tools


Differences

This shows you the differences between two versions of the page.

Go

Link to this comparison view

token_migration_tool [2019-07-03 11:13]
dorothea.bartel
token_migration_tool [2019-10-04 09:26] (current)
Line 1: Line 1:
 ====== Token Migration Tool ====== ====== Token Migration Tool ======
 +
  
 ===== Introduction ===== ===== Introduction =====
  
-The Token Migration Tool (ToMi) enables merchants to continue processing recurring payments after migration to the Wirecard REST API. With ToMi, you just need to provide the order number which is currently used to reference recurring transaction. ToMi uses this order number and returns the corresponding token (credit card) and transactionId (SEPA Direct Debit), which allows you to continue processing recurring transactions for that order without interruptions.+The Token Migration Tool (ToMi) enables merchants to continue processing recurring payments after migration to the Wirecard REST API. With ToMi, you just need to provide the order number which is currently used to reference recurring transaction. ToMi uses this order number and returns the ''transactionId'' and the corresponding ''tokenId'' (only for credit card), which allows you to continue processing recurring transactions for that order without interruptions.
  
 ===== Supported Payment Methods ===== ===== Supported Payment Methods =====
Line 17: Line 18:
 ^ Environment ^ URL ^ ^ Environment ^ URL ^
 | Production | %%https://checkout.wirecard.com/migration-transaction%% | | Production | %%https://checkout.wirecard.com/migration-transaction%% |
-| Test | %%https://checkout-test.wirecard.com/migration-transaction%% |+
    
 ===== Request ===== ===== Request =====
Line 69: Line 70:
   * Possible status codes: 201 | 400 | 404 | 500   * Possible status codes: 201 | 400 | 404 | 500
  
-==== JSON Schema - Success Response ====+==== JSON Schema ====
  
 +=== Success Response ===
 <code> <code>
 { {
Line 93: Line 95:
 </code> </code>
  
-==== JSON Schema - Error Response ====+=== Error Response ===
  
 <code> <code>
Line 101: Line 103:
             "type": "integer"             "type": "integer"
         },         },
-        "message": "+        "message": { 
-            "type" "string"+            "type""string"
         }         }
     }     }
Line 155: Line 157:
  
 ^ Error Message ^ Status Code ^ Description ^ Remedy ^ ^ Error Message ^ Status Code ^ Description ^ Remedy ^
-| Provided Payment Method is not valid | 400 | This happens when POST payload as payment method has a value other than creditcard or sepa | To recover from this, verify if payment method is one of those two. | +| Provided Payment Method is not valid | 400 | This happens if the ''paymentMethod'' in the request has a value other than ''creditcard'' or ''sepa''. | To recover from this, verify that the payment method is one of those two. | 
-| Entity not found | 404 | Possible reason is that merchant configuration is not valid, e.g. there are many configurations for same merchant_account | [[support.at@wirecard.com|Contact merchant support]]. | +| Entity not found | 404 | Possible reason is that merchant configuration is not valid, e.g. there are many configurations for the same ''merchant_account''. | [[support.at@wirecard.com|Contact merchant support]] for further questions. | 
-| Order with number '<x>' could not be found | 404 | This error occurs for CREDITCARD or SEPA requestwhen order does not exist in database | Provide a valid order number in request. |+| Order with number '<x>' could not be found | 404 | This error occurs for CREDITCARD or SEPA request when the order does not exist in the database| Provide a valid order number in the request. \\ **The error is most likely caused by an outdated order number. Check the order creation date. An order number is valid for 400 days.** \\ [[support.at@wirecard.com|Contact merchant support]] for further questions. |
 | Internal server error | 500 | Possible reason: HTTP method is not POST | Change HTTP method to POST. Do not use GET, PUT, ... | | Internal server error | 500 | Possible reason: HTTP method is not POST | Change HTTP method to POST. Do not use GET, PUT, ... |
  

This website uses cookies to deliver the best service to you. By continuing to browse the site, you are agreeing to our use of cookies.