In the event CyberSource discovers that a merchant is capturing and/or transmitting personally identifying information via the merchant-defined data fields, whether or not intentionally, CyberSource WILL immediately suspend the merchant's account, which will result in a rejection of any and all transaction requests submitted by the merchant after the point of suspension. Personally identifying information includes, but is not limited to, card number, bank account number, social security number, driver's license number, state-issued identification number, passport number, card verification numbers (CVV, CVC2, CVV2, CID, CVN). Accordingly, merchants are prohibited from capturing, obtaining, and/or transmitting any personally identifying information in or via the merchant-defined data fields and any Secure Acceptance field that is not specifically designed to capture personally identifying information. From pay-on-demand to reimbursementsyou set the pace. Find Out How Money OUT TM More options for how and when you pay people. When you use the example gateway, your site doesnt receive card data capable of a transaction, but the user flow looks the same. ![]() ![]() ![]() If you want to try out the API, you can leave the code sample above as-is. Important Merchant-defined data fields are not intended to and MUST NOT be used to capture personally identifying information. MerchantE Maximize Money Your Way Money IN TM Accepting and processing credit card, debit card and ACH payments has never been easier, and getting you paid has never been quicker. Tip: example is a valid gateway name in the test environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |