Skip to content

payroc/migrations

v0.2.0MIT

Skills for migrating an existing integration from a legacy Payroc gateway to the Payroc API

from-ibx

Guides developers through porting an existing IBX gateway integration to the Payroc API. Use this skill to: migrate, port, or re-platform an integration off IBX; find the Payroc equivalent of an IBX SOAP operation or REST endpoint; understand what a TransType value maps to; work out what changes in a request when moving from transact.asmx, cardsafe.asmx, recurring.asmx or the IBX /api/v1 REST surface; translate IBX identifiers (PNRef, CustomerKey, ContractKey, CardToken) into Payroc counterparts; find out whether a capability the integration relies on still exists on Payroc; or plan the cutover for stored tokens and historical transaction references. Do NOT use this skill when building a new Payroc integration with no legacy IBX code (use a task skill such as run-a-card-sale, save-a-payment-method, or take-an-ach-payment), when migrating from a different provider, or when the user already knows the Payroc operation and only wants to implement it (go straight to that skill).

from-itransact

Guides developers through porting an existing iTransact integration to the Payroc API before Payroc retires the iTransact gateway. Use this skill when the user wants to: migrate off iTransact; find the Payroc equivalent of an xmltrans2 or xmltrans XML request, an ord.cgi or split-form post, a direct-call CGI, an api.itransact.com JSON API route, or a gateway servlet request; port an iTransact SDK, plugin, client, postback receiver or the itransact.js Checkout script; translate xid, token, customer or recipe identifiers, amounts and currency; find out whether a capability still exists on Payroc; or plan the cutover of stored cards and recurring schedules. Do NOT use this skill when the user is building a new Payroc integration with no iTransact code (use the relevant task skill such as run-a-card-sale or integrate-hosted-fields), when they are migrating from IBX (use from-ibx) or another provider, or when they already know the Payroc operation they need and only want to implement it.

from-transsafe

Guides developers through porting an existing TranSafe gateway integration to the Payroc API. Use this skill when the user wants to: migrate or port an integration off TranSafe; find the Payroc equivalent of a TranSafe REST call (/api/v2 or /api/v1) or a key/value request such as action_trans=sale sent through libMonetra or another KV transport; replace PaymentFrame, TicketRequest, cardshieldticket, hosted paypages or invoice pages; translate TranSafe identifiers such as ttid, token or profile_id; check whether a TranSafe capability (gift cards, PayPal, customers, orders, velocity rules, user admin) still exists; or plan the cutover for tokens, schedules, open authorizations and history. Do NOT use it for a new Payroc integration with no TranSafe code (use the task skill, such as run-a-card-sale or save-a-payment-method), for a migration from IBX or another provider, or when the user already knows the Payroc operation and only wants to implement it.