{"metadata":{"image":[],"title":"","description":""},"api":{"url":"","auth":"required","settings":"","results":{"codes":[]},"params":[]},"next":{"description":"","pages":[]},"title":"Card Processing Overview","type":"basic","slug":"card-processing-overview","excerpt":"","body":"[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Expectations: Testing Vs. Production\"\n}\n[/block]\nWhen running card transactions in testwyre, you will get used to seeing successful transactions. The experience will be much different when switching over to live processing in production. There are a number of factors that come into play when processing live cards and these factors are magnified when processing crypto purchases. \n\nMany factors that determine a successful or failed charge are set by 3rd parties such as, the payment processor, card issuer or payment network. Wyre also employs a fraud engine to reduce fraudulent transactions and chargebacks. These features reduce the number of successful transactions, but ultimately they help all parties fight fraud and remain compliant.\n[block:api-header]\n{\n  \"title\": \"Limitations and Considerations\"\n}\n[/block]\nThere are certain limitations on the types of cards that can be processed. We currently process through the Visa and Mastercard networks only.\n\nWe cannot process:\n* Pre-Paid Debit or Gift Cards \n* Cards issued by a neo/virtual bank\n* Unsupported networks\n\nThere are also additional considerations for processing credit cards vs. debit cards. Many credit card issuers will consider crypto purchases the same as a cash advance. The issuing bank may charge your user additional cash advance fees for their crypto purchases through Wyre. You may want to limit processing to debit cards only, or fully disclose the possibility of additional fees levied by the credit card issuer. \n[block:api-header]\n{\n  \"title\": \"Errors\"\n}\n[/block]\nView the list of [Card Exceptions](doc:wallet-order-creation-exceptions). The [Wallet Order Details](doc:wallet-order-details) endpoint is also a source for providing error messaging related to a particular order.","updates":[],"order":0,"isReference":false,"hidden":false,"sync_unique":"","link_url":"","link_external":false,"_id":"600284336b63ed001ed667a2","createdAt":"2021-01-16T06:14:11.081Z","user":"5f7f6ea298ba660011771f74","category":{"sync":{"isSync":false,"url":""},"pages":[],"title":"Card Processing","slug":"card-processing","order":4,"from_sync":false,"reference":false,"_id":"5f2768d05702ca0011f7655e","createdAt":"2020-08-03T01:30:56.397Z","version":"550f75de61d9d30d00af9e01","project":"550f74bb6fc8130d0038aad3","__v":0},"version":{"version":"3","version_clean":"3.0.0","codename":"","is_stable":true,"is_beta":true,"is_hidden":false,"is_deprecated":false,"categories":["550f75de61d9d30d00af9e02","551027e38579861900a86698","551029e08579861900a8669a","551029e7498062190006328a","5bc633a722d682005c9ad9e4","5bc633b08c4b0b000d6a7eaa","5bc633b48f3ff600626e3e18","5bc63538e5a6ba000d22ee6d","5bc63587a18a6b000decd295","5bc635c0937fcb0056223d9c","5bc6360f42f41800319aeaa6","5be5d13ff1d319002baca9ce","5be5d2287cd14d00291fbfdb","5be8b3b09f7cb70023c56a39","5be8b3cbb910100044e20206","5c1d769a4f6aed001fe527f0","5c402942010f0d001496dded","5e8127d61c906800374eeb1c","5f2768c98622b8005106544a","5f2768d05702ca0011f7655e","5f276e5348d2b600321aef9b","5f276fd300e519001139200a","5f9a2cb79dafe500259281a7","5fd92bf362bb7301b00e48ba"],"_id":"550f75de61d9d30d00af9e01","__v":24,"releaseDate":"2015-03-23T02:09:34.221Z","project":"550f74bb6fc8130d0038aad3","createdAt":"2015-03-23T02:09:34.221Z","forked_from":"550f74bb6fc8130d0038aad6"},"project":"550f74bb6fc8130d0038aad3","__v":0,"parentDoc":null}

Card Processing Overview


[block:api-header] { "type": "basic", "title": "Expectations: Testing Vs. Production" } [/block] When running card transactions in testwyre, you will get used to seeing successful transactions. The experience will be much different when switching over to live processing in production. There are a number of factors that come into play when processing live cards and these factors are magnified when processing crypto purchases. Many factors that determine a successful or failed charge are set by 3rd parties such as, the payment processor, card issuer or payment network. Wyre also employs a fraud engine to reduce fraudulent transactions and chargebacks. These features reduce the number of successful transactions, but ultimately they help all parties fight fraud and remain compliant. [block:api-header] { "title": "Limitations and Considerations" } [/block] There are certain limitations on the types of cards that can be processed. We currently process through the Visa and Mastercard networks only. We cannot process: * Pre-Paid Debit or Gift Cards * Cards issued by a neo/virtual bank * Unsupported networks There are also additional considerations for processing credit cards vs. debit cards. Many credit card issuers will consider crypto purchases the same as a cash advance. The issuing bank may charge your user additional cash advance fees for their crypto purchases through Wyre. You may want to limit processing to debit cards only, or fully disclose the possibility of additional fees levied by the credit card issuer. [block:api-header] { "title": "Errors" } [/block] View the list of [Card Exceptions](doc:wallet-order-creation-exceptions). The [Wallet Order Details](doc:wallet-order-details) endpoint is also a source for providing error messaging related to a particular order.