Notice of change - Changes to id format for Single Immediate Payments and Future Dated Payments

Issued: 19th May 2023 | TB-1069

Updated: 17th July 2023

Updated: 18th September 2023

What's changing?

Changes have been made to the id formats to improve tracking of a single immediate payment and future dated payment initiation requests.

The format for ids is changing from:

• tokenId – tt:BzFCFwVt5zrt6rdcHJK5imf2HXbGdVdyHKpWQZbgzL5s:qXTkpBAZVbXMxk9vi

• transferId – t:2UhwCZ3BMaEcAUK8bZdukor7NL4tH6TBuu6aJMp5KKfX:5zKcENpV

• transfer id - tt: 83KiRJuXmEDV5m2b8ZvLGE91ELf7PPw5BaDab98kMguu:3VMczyq7r7b6HwC

• requestId – rq:ej5ACWNwi1EcqBeuDPc4Z8C4Bgc:5zKtXEAq

to a generic prefix of pm2:

• all ids – pm2:ej5ACWNwi1EcqBeuDPc4Z8C4Bgc:5zKtXEAq

Here are some examples of the responses for the GET /token-request/result/{tokenRequestId}/results and GET /transfers calls:

GET {{BASE_URL}}/token-requests/{tokenRequestId}/result response

{
    "signature": {
        "keyId": "CqSTHPvWY_dgVh-f",
        "memberId": "m:nP4w3u5y8ddrxDJkjimgSX9e4fZ:5zKtXEAq",
        "signature": "ODRWmM0xMRM7CKmK3bNl4e2Kb2btavTbZssCsrHsu8yopoKxBzouBrD9q5-E63tgdV1DpB7i31vwNDKywA0CAE",
    },
    "status": "PROCESSED",
    "statusReasonInformation": "The Token request has been processed.",
    "tokenId": "pm2:3eYPU1BEKKunfmYgQuSKXFCeo851C5Y3XiZW3XA465TU:5zKtXEAq",
    "transferId": "pm2:3eYPU1BEKKunfmYgQuSKXFCeo851C5Y3XiZW3XA465TU:5zKtXEAq"
}

GET {{BASE_URL}}/transfers response

{
    "transfers": [
        {
        "actingAs": { ... },
        "convertedToFutureDatedPayment": false,
        "createdAtMs": "8921348754",
        "executionDate": "2023-01-28",
        "id": "pm2:4WJB2Jgm4QQMWav5tEdPXArzxxXtuZApzTHb5pFBUUMt:ZhBVAJSGzmfoR",
        "method": "INSTANT",
        "orderId": "bfeab16d-5d84-46b0-8058-343c160d0e1b",
        "payload": {
            "refId": "1683844967",
            "tokenId": "pm2:4WJB2Jgm4QQMWav5tEdPXArzxxXtuZApzTHb5pFBUUMt:ZhBVAJSGzmfoR",
            "amount": {
                "currency": "EUR",
                "value": "5.00",
            },
            "description": "D1683844967",
        },
        "payloadSignatures": { ... },
        "providerDetails": { ... },
        "refund": { ... },
        "refundDetails": { ... },
        "scaStatus": "APPLIED",
        "source": { ... },
        "status": "PROCESSING",
        "statusReasonInformation": "The Token request is processing.",
        "transactionId": "3TaeSE1GwcvsdfvafvvJUcgseh32fRhbv3g8gsdghh43jD09gvWn17ur",
        }
    ]
    "offset": "LerV6Jmex"
}

As this change is rolled out, you'll start to notice that some of your requests will have the new format ids, as will the corresponding token and transfer ids.

What problem will this solve?

This change will help you to easily identify the lifecycle of a payment initiation.

Does this change affect you?

This change applies to Token.io’s Payment Initiation Services (PIS) for Single Immediate Payments (SIP) and Future Dated Payments (FDP).

What action do I need to take?

You should check for Backward Compatibility to ensure that this change will have no impact on your requests and transfers.

When will this change be applied to all impacted customers?

Token.io will apply this change incrementally to specific memberIds in sandbox, followed by production. The dates for the commencement of the roll-out are shown in the table below. You'll be notified in advance before this change is applied to your implementation.

If you would like to delay this change to a time that suits you, please contact Token.io Support or your Implementation Manager.

Where can I get further information?

For assistance with the above and other operational aspects of the Token.io Account-to-Account Infrastructure, please contact Token.io Support.