Payments & Vouchers

Terminal Tokenisations

A TerminalTokenisation represents a tokenisation request to a terminal.

post/shop/terminal-tokenisations

Create a request to tokenise a customer's card details

createCardTokenisationRequest

This endpoint sends a request to the terminal to tokenise a customer's card details.

Request body

  • terminal_idobject-idrequired

    Identifier of the physical payment terminal that should prompt for the card. The terminal captures the card and returns a tokenised reference; no PAN is stored in Trybe. Must belong to the caller's site.

  • customer_iduuidrequired

    Identifier of the customer whose card is being saved on file. The resulting payment-method token is attached to this customer and can be used for future charges (e.g. no-show fees, recurring bookings).

Responses

  • 200

    The Card Tokenisation was successfully retrieved

  • 400

    The request failed.

  • 401

    The user is unauthenticated

  • 403

    The authenticated user does not have permission.

  • 422

    The request didn't pass validation

get/shop/terminal-tokenisations/{paymentId}

Show a Card Tokenisation Request

getCardTokenisationRequest

This endpoint retrieves a Card Tokenisation Request by Payment ID.

Path parameters

  • paymentIdobject-idrequired

    The ID of the CardTokenisationRequest

Responses

  • 200

    The Card Tokenisation was successfully retrieved

  • 401

    The user is unauthenticated

  • 404

    The resource couldn't be found

post/shop/terminal-tokenisations/{paymentId}/cancel

Cancel a Card Tokenisation Request

actionCancelCardTokenisationRequest

This endpoint cancels a Card Tokenisation Request.

Path parameters

  • paymentIdobject-idrequired

    The ID of the CardTokenisationRequest

Responses

  • 200

    The Card Tokenisation was successfully retrieved

  • 401

    The user is unauthenticated

  • 403

    The authenticated user does not have permission.

  • 404

    The resource couldn't be found