CopycURL Copied Copy failed

#!/usr/bin/env bash
# Simulate processor latency
#
# Make the sandbox processor take its time, then make it answer later than your own client is
# willing to wait, so your timeout path is something you have run rather than something you have
# written.
#
# Every API call in this blueprint, in order. Each value a call returns is passed to the calls after
# it. A step that happens outside the API is a comment, and any failed call stops the script.

set -euo pipefail

BASE_URL="{{BASE_URL}}"
API_KEY="{{API_KEY}}"

# Sends one request and prints the response body. A failed call prints the API's answer and stops
# the script.
call() {
  local method="$1" path="$2" body="${3:-}" out
  local args=(-sS --fail-with-body -X "$method" "$BASE_URL$path" -H "api-key: $API_KEY")
  if [ -n "$body" ]; then
    args+=(-H "Content-Type: application/json" -d "$body")
  fi
  if ! out=$(curl "${args[@]}"); then
    printf '%s\n' "$out" >&2
    return 1
  fi
  printf '%s' "$out"
}

# Phase 1: Drive each latency profile

# Step 1: Send a sale through a degraded processor
call POST "/api/transactions" '{
  "transactionType": "Sale",
  "cardData": {
    "cardNumber": "4111111111111111",
    "nameOnCard": "Jane Doe",
    "expirationMonth": 12,
    "expirationYear": 2030,
    "cvv": 123
  },
  "customFields": [
    { "name": "loopback.latencyProfile", "value": "slow" }
  ],
  "invoiceData": {
    "amounts": { "base": 10.00, "total": 10.00 }
  }
}' > /dev/null

# Step 2: Send a sale that outlasts a typical client timeout
call POST "/api/transactions" '{
  "transactionType": "Sale",
  "cardData": {
    "cardNumber": "4111111111111111",
    "nameOnCard": "Jane Doe",
    "expirationMonth": 12,
    "expirationYear": 2030,
    "cvv": 123
  },
  "customFields": [
    { "name": "loopback.latencyProfile", "value": "timeout" }
  ],
  "invoiceData": {
    "amounts": { "base": 10.00, "total": 10.00 }
  }
}' > /dev/null

# Phase 2: Decide what your client does about it

# Step 3: Set your own timeout, then decide what happens when it fires
# A timeout is a decision about how long you are willing to wait, not a report that nothing
# happened. Pick one on purpose, log the request you abandoned, and never resend a payment blind:
# ask what became of it first. Send "loopback.latencyMs" instead of a named profile to hold the
# answer for an exact number of milliseconds, which is how you pin a run to the boundary your own
# client sits on. Both fields ride on a transaction custom field. Every profile
# "loopback.latencyProfile" accepts is listed on the testing page. One constraint applies to the
# custom-field channel. If the merchant has defined any custom fields at all, every submitted
# custom-field name has to match one of those definitions, and a name that doesn't match is rejected
# with a 400. A sandbox merchant with no custom-field definitions accepts any name, which is the
# usual case. If you get a 400 naming the control field you sent, define a custom field with that
# name on the merchant.

CopyPowerShell Copied Copy failed

# Simulate processor latency
#
# Make the sandbox processor take its time, then make it answer later than your own client is
# willing to wait, so your timeout path is something you have run rather than something you have
# written.
#
# Every API call in this blueprint, in order. Each value a call returns is passed to the calls after
# it. A step that happens outside the API is a comment, and any failed call stops the script.

$ErrorActionPreference = 'Stop'

$baseUrl = '{{BASE_URL}}'
$apiKey = '{{API_KEY}}'

# Sends one request and returns the parsed response body. A failed call stops the script.
function Invoke-BlueprintCall([string] $Method, [string] $Path, [string] $Body) {
    $arguments = @{
        Method  = $Method
        Uri     = $baseUrl + $Path
        Headers = @{ 'api-key' = $apiKey }
    }
    if ($Body) {
        $arguments.ContentType = 'application/json'
        $arguments.Body = [System.Text.Encoding]::UTF8.GetBytes($Body)
    }
    Invoke-RestMethod @arguments
}

# Phase 1: Drive each latency profile

# Step 1: Send a sale through a degraded processor
$body = @'
{
  "transactionType": "Sale",
  "cardData": {
    "cardNumber": "4111111111111111",
    "nameOnCard": "Jane Doe",
    "expirationMonth": 12,
    "expirationYear": 2030,
    "cvv": 123
  },
  "customFields": [
    { "name": "loopback.latencyProfile", "value": "slow" }
  ],
  "invoiceData": {
    "amounts": { "base": 10.00, "total": 10.00 }
  }
}
'@
$null = Invoke-BlueprintCall -Method 'POST' -Path '/api/transactions' -Body $body

# Step 2: Send a sale that outlasts a typical client timeout
$body = @'
{
  "transactionType": "Sale",
  "cardData": {
    "cardNumber": "4111111111111111",
    "nameOnCard": "Jane Doe",
    "expirationMonth": 12,
    "expirationYear": 2030,
    "cvv": 123
  },
  "customFields": [
    { "name": "loopback.latencyProfile", "value": "timeout" }
  ],
  "invoiceData": {
    "amounts": { "base": 10.00, "total": 10.00 }
  }
}
'@
$null = Invoke-BlueprintCall -Method 'POST' -Path '/api/transactions' -Body $body

# Phase 2: Decide what your client does about it

# Step 3: Set your own timeout, then decide what happens when it fires
# A timeout is a decision about how long you are willing to wait, not a report that nothing
# happened. Pick one on purpose, log the request you abandoned, and never resend a payment blind:
# ask what became of it first. Send "loopback.latencyMs" instead of a named profile to hold the
# answer for an exact number of milliseconds, which is how you pin a run to the boundary your own
# client sits on. Both fields ride on a transaction custom field. Every profile
# "loopback.latencyProfile" accepts is listed on the testing page. One constraint applies to the
# custom-field channel. If the merchant has defined any custom fields at all, every submitted
# custom-field name has to match one of those definitions, and a name that doesn't match is rejected
# with a 400. A sandbox merchant with no custom-field definitions accepts any name, which is the
# usual case. If you get a 400 naming the control field you sent, define a custom field with that
# name on the merchant.

CopyTypeScript Copied Copy failed

// Simulate processor latency
//
// Make the sandbox processor take its time, then make it answer later than your own client is
// willing to wait, so your timeout path is something you have run rather than something you have
// written.
//
// Every API call in this blueprint, in order. Each value a call returns is passed to the calls
// after it. A step that happens outside the API is a comment, and any failed call stops the script.

export {};

const baseUrl = '{{BASE_URL}}';
const apiKey = '{{API_KEY}}';

// Sends one request and returns the parsed response body. A failed call throws.
async function call(method: string, path: string, body?: unknown): Promise<any> {
  const headers: Record<string, string> = { 'api-key': apiKey };
  if (body !== undefined) {
    headers['Content-Type'] = 'application/json';
  }

  const response = await fetch(baseUrl + path, {
    method,
    headers,
    body: body === undefined ? undefined : JSON.stringify(body),
  });

  const text = await response.text();
  if (!response.ok) {
    throw new Error(`${method} ${path} answered ${response.status}: ${text}`);
  }

  return text ? JSON.parse(text) : null;
}

// Phase 1: Drive each latency profile

// Step 1: Send a sale through a degraded processor
await call('POST', '/api/transactions', {
  "transactionType": "Sale",
  "cardData": {
    "cardNumber": "4111111111111111",
    "nameOnCard": "Jane Doe",
    "expirationMonth": 12,
    "expirationYear": 2030,
    "cvv": 123
  },
  "customFields": [
    { "name": "loopback.latencyProfile", "value": "slow" }
  ],
  "invoiceData": {
    "amounts": { "base": 10.00, "total": 10.00 }
  }
});

// Step 2: Send a sale that outlasts a typical client timeout
await call('POST', '/api/transactions', {
  "transactionType": "Sale",
  "cardData": {
    "cardNumber": "4111111111111111",
    "nameOnCard": "Jane Doe",
    "expirationMonth": 12,
    "expirationYear": 2030,
    "cvv": 123
  },
  "customFields": [
    { "name": "loopback.latencyProfile", "value": "timeout" }
  ],
  "invoiceData": {
    "amounts": { "base": 10.00, "total": 10.00 }
  }
});

// Phase 2: Decide what your client does about it

// Step 3: Set your own timeout, then decide what happens when it fires
// A timeout is a decision about how long you are willing to wait, not a report that nothing
// happened. Pick one on purpose, log the request you abandoned, and never resend a payment blind:
// ask what became of it first. Send "loopback.latencyMs" instead of a named profile to hold the
// answer for an exact number of milliseconds, which is how you pin a run to the boundary your own
// client sits on. Both fields ride on a transaction custom field. Every profile
// "loopback.latencyProfile" accepts is listed on the testing page. One constraint applies to the
// custom-field channel. If the merchant has defined any custom fields at all, every submitted
// custom-field name has to match one of those definitions, and a name that doesn't match is
// rejected with a 400. A sandbox merchant with no custom-field definitions accepts any name, which
// is the usual case. If you get a 400 naming the control field you sent, define a custom field with
// that name on the merchant.

CopyC# Copied Copy failed

// Simulate processor latency
//
// Make the sandbox processor take its time, then make it answer later than your own client is
// willing to wait, so your timeout path is something you have run rather than something you have
// written.
//
// Every API call in this blueprint, in order. Each value a call returns is passed to the calls
// after it. A step that happens outside the API is a comment, and any failed call stops the script.

using System.Text;
using System.Text.Json;

var baseUrl = "{{BASE_URL}}";
var apiKey = "{{API_KEY}}";

using var http = new HttpClient();
http.DefaultRequestHeaders.Add("api-key", apiKey);

// Sends one request and returns the parsed response body. A failed call throws.
async Task<JsonElement> CallAsync(string method, string path, string? body = null)
{
    using var request = new HttpRequestMessage(new HttpMethod(method), baseUrl + path);
    if (body is not null)
    {
        request.Content = new StringContent(body, Encoding.UTF8, "application/json");
    }

    using var response = await http.SendAsync(request);
    var json = await response.Content.ReadAsStringAsync();
    if (!response.IsSuccessStatusCode)
    {
        throw new HttpRequestException($"{method} {path} answered {(int)response.StatusCode}: {json}");
    }

    return json.Length == 0 ? default : JsonSerializer.Deserialize<JsonElement>(json);
}

// Phase 1: Drive each latency profile

// Step 1: Send a sale through a degraded processor
await CallAsync("POST", "/api/transactions", """
    {
      "transactionType": "Sale",
      "cardData": {
        "cardNumber": "4111111111111111",
        "nameOnCard": "Jane Doe",
        "expirationMonth": 12,
        "expirationYear": 2030,
        "cvv": 123
      },
      "customFields": [
        { "name": "loopback.latencyProfile", "value": "slow" }
      ],
      "invoiceData": {
        "amounts": { "base": 10.00, "total": 10.00 }
      }
    }
    """);

// Step 2: Send a sale that outlasts a typical client timeout
await CallAsync("POST", "/api/transactions", """
    {
      "transactionType": "Sale",
      "cardData": {
        "cardNumber": "4111111111111111",
        "nameOnCard": "Jane Doe",
        "expirationMonth": 12,
        "expirationYear": 2030,
        "cvv": 123
      },
      "customFields": [
        { "name": "loopback.latencyProfile", "value": "timeout" }
      ],
      "invoiceData": {
        "amounts": { "base": 10.00, "total": 10.00 }
      }
    }
    """);

// Phase 2: Decide what your client does about it

// Step 3: Set your own timeout, then decide what happens when it fires
// A timeout is a decision about how long you are willing to wait, not a report that nothing
// happened. Pick one on purpose, log the request you abandoned, and never resend a payment blind:
// ask what became of it first. Send "loopback.latencyMs" instead of a named profile to hold the
// answer for an exact number of milliseconds, which is how you pin a run to the boundary your own
// client sits on. Both fields ride on a transaction custom field. Every profile
// "loopback.latencyProfile" accepts is listed on the testing page. One constraint applies to the
// custom-field channel. If the merchant has defined any custom fields at all, every submitted
// custom-field name has to match one of those definitions, and a name that doesn't match is
// rejected with a 400. A sandbox merchant with no custom-field definitions accepts any name, which
// is the usual case. If you get a 400 naming the control field you sent, define a custom field with
// that name on the merchant.

CopyPython Copied Copy failed

# Simulate processor latency
#
# Make the sandbox processor take its time, then make it answer later than your own client is
# willing to wait, so your timeout path is something you have run rather than something you have
# written.
#
# Every API call in this blueprint, in order. Each value a call returns is passed to the calls after
# it. A step that happens outside the API is a comment, and any failed call stops the script.

import requests

BASE_URL = "{{BASE_URL}}"
API_KEY = "{{API_KEY}}"


# Sends one request and returns the parsed response body. A failed call raises.
def call(method, path, body=None):
    response = requests.request(
        method,
        BASE_URL + path,
        headers={"api-key": API_KEY},
        json=body,
    )
    response.raise_for_status()
    return response.json() if response.content else None


# Phase 1: Drive each latency profile

# Step 1: Send a sale through a degraded processor
call("POST", "/api/transactions", {
  "transactionType": "Sale",
  "cardData": {
    "cardNumber": "4111111111111111",
    "nameOnCard": "Jane Doe",
    "expirationMonth": 12,
    "expirationYear": 2030,
    "cvv": 123
  },
  "customFields": [
    { "name": "loopback.latencyProfile", "value": "slow" }
  ],
  "invoiceData": {
    "amounts": { "base": 10.00, "total": 10.00 }
  }
})

# Step 2: Send a sale that outlasts a typical client timeout
call("POST", "/api/transactions", {
  "transactionType": "Sale",
  "cardData": {
    "cardNumber": "4111111111111111",
    "nameOnCard": "Jane Doe",
    "expirationMonth": 12,
    "expirationYear": 2030,
    "cvv": 123
  },
  "customFields": [
    { "name": "loopback.latencyProfile", "value": "timeout" }
  ],
  "invoiceData": {
    "amounts": { "base": 10.00, "total": 10.00 }
  }
})

# Phase 2: Decide what your client does about it

# Step 3: Set your own timeout, then decide what happens when it fires
# A timeout is a decision about how long you are willing to wait, not a report that nothing
# happened. Pick one on purpose, log the request you abandoned, and never resend a payment blind:
# ask what became of it first. Send "loopback.latencyMs" instead of a named profile to hold the
# answer for an exact number of milliseconds, which is how you pin a run to the boundary your own
# client sits on. Both fields ride on a transaction custom field. Every profile
# "loopback.latencyProfile" accepts is listed on the testing page. One constraint applies to the
# custom-field channel. If the merchant has defined any custom fields at all, every submitted
# custom-field name has to match one of those definitions, and a name that doesn't match is rejected
# with a 400. A sandbox merchant with no custom-field definitions accepts any name, which is the
# usual case. If you get a 400 naming the control field you sent, define a custom field with that
# name on the merchant.