Tokenize the card
Changed onSend card details to a PCI-DSS-compliant tokenization server without reaching Mangopay's servers.
The URL to use for this endpoint is returned in the CardRegistrationURL parameter on the POST Create a Card Registration endpoint.
The request must be made using the “application/x-www-form-urlencoded” content type. <Note icon="fa-regular fa-circle-info"> Note – Do not hardcode the URL
The CardRegistrationURL is specific to each payment. You must rely on the returned URL in full (host, path, and queries) and not hardcode any part of it. </Note>
<Warning icon="fa-regular fa-triangle-exclamation"> **Caution – Card details must never pass via your server**For security reasons, it is strictly forbidden to send the card details to your own server. You must rely on the dedicated PCI-DSS-compliant tokenization server by using the endpoint provided. </Warning>
Request
- Base URLhttps://api.sandbox.mangopay.com
- URLhttps://api.sandbox.mangopay.com/{CardRegistrationUrl}
- AuthHTTP bearer
Path parameters
The variable URL is only documented as a path parameter on this path for documentation reasons. I allows it to be rendered visiablly on the page, and because there are two dynamic server URLs in the spec (so both would be on the / path). The variable URL is the server for this request, and it has a variable host and path and query parameters. You do not need to add anything to it.
Request body
Response
The string returned by the tokenization server.
Send this string in full as the RegistrationData value on the PUT Update a Card Registration endpoint to create the Card object.
Changes
- warning
deleted the
headerrequest parameterAuthorization - info
the endpoint scheme security
oauth2was added to the API
- warning
- info
api operation id
tokenize_cardremoved and replaced withcardRegistrations_tokenize_card
- info