Website logo
Create AccountSign In
⌘K
Moyasar Documentation
Payments
Credit Card
Apple Pay
STC Pay
Tokenization
Payment Errors
Form Configuration
Payouts
Invoices
Creating invoices
Mobile SDKs
iOS SDK
Android SDK
Flutter SDK
Hosted Checkout
E-Commerce Plugins
WooCommerce
PrestaShop
NopCommerce
OpenCart
Magento2
Testing
Testing Cards
Apple Pay Testing
Custom Payments
Credit Cards
STC Pay
Apple Pay on Websites
Apple Pay on Apps
Tokenized Cards
Dashboard
Apple Pay Using Developer Account
Apple Pay Using Web Registration
Get Your API Keys
Setting up your IP whitelist
Setting up Webhooks
API
Introduction
Authentication
Pagination
Metadata
Payments
Payouts
Invoices
Tokens
Apple Pay
Webhooks
Errors
Support
Help Desk
Docs powered by Archbee
API
Payments

3D Secure

1min

In the world of e-Payment, fear of online fraud holds many credit card holders back from all sorts of online activities (shopping, transactions, subscriptions, etc). One of the main goals of introducing 3-D secure industry standard solutions by Visa and MasterCard is to increase security during e-Payment transactions and prevent fraud.

All create payment API calls default to 3-D secure. This is configurable using the creditcard source[3ds] parameter in the payment object.

Upon creation, the returned payment object will include transaction_url and the credit card user should be redirected to continue the transaction at the issuing bank gateway.

After successful authorization, the user will be charged, and redirected by API to the customer’s site as specified in the callback_url parameter.

The payment’s id, status, and message will be appended to callback_url original query parameters during redirection.

Updated 23 Nov 2023
Did this page help you?
PREVIOUS
Manual Payments
NEXT
Create Account
Docs powered by Archbee
Docs powered by Archbee